Jul 29 04:08:21 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8369" x-info="http://www.rsyslog.com"] start
Jul 29 04:08:21 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 29 04:08:21 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 29 04:08:21 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 29 04:08:21 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 29 04:08:21 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 29 04:08:21 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 29 04:08:21 node-4 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 29 04:08:21 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=2412558c-77ba-4a40-8577-74ac4cd89780 nomdmonddf nomdmonisw
Jul 29 04:08:21 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 29 04:08:21 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 29 04:08:21 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 29 04:08:21 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 29 04:08:21 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 29 04:08:21 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 29 04:08:21 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 29 04:08:21 node-4 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 29 04:08:21 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 29 04:08:21 node-4 kernel: [    0.000000] No AGP bridge found
Jul 29 04:08:21 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 29 04:08:21 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 29 04:08:21 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 29 04:08:21 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 29 04:08:21 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 29 04:08:21 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 29 04:08:21 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 29 04:08:21 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 29 04:08:21 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 29 04:08:21 node-4 kernel: [    0.000000]   2 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000]   3 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000]   4 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000]   5 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000]   6 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000]   7 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000]   8 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000]   9 disabled
Jul 29 04:08:21 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 29 04:08:21 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 29 04:08:21 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 29 04:08:21 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 29 04:08:21 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 29 04:08:21 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 29 04:08:21 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 29 04:08:21 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 29 04:08:21 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 29 04:08:21 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 29 04:08:21 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 29 04:08:21 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 29 04:08:21 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 29 04:08:21 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 29 04:08:21 node-4 kernel: [    0.000000] Zone ranges:
Jul 29 04:08:21 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 29 04:08:21 node-4 kernel: [    0.000000] Early memory node ranges
Jul 29 04:08:21 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 29 04:08:21 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 29 04:08:21 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 29 04:08:21 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 29 04:08:21 node-4 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 29 04:08:21 node-4 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 29 04:08:21 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 29 04:08:21 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 29 04:08:21 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 29 04:08:21 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 29 04:08:21 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 29 04:08:21 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 29 04:08:21 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 29 04:08:21 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 29 04:08:21 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 29 04:08:21 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 29 04:08:21 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 29 04:08:21 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 29 04:08:21 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 29 04:08:21 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 29 04:08:21 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 29 04:08:21 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 29 04:08:21 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 29 04:08:21 node-4 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 29 04:08:21 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 29 04:08:21 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 29 04:08:21 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=2412558c-77ba-4a40-8577-74ac4cd89780 nomdmonddf nomdmonisw
Jul 29 04:08:21 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 29 04:08:21 node-4 kernel: [    0.000000] Checking aperture...
Jul 29 04:08:21 node-4 kernel: [    0.000000] No AGP bridge found
Jul 29 04:08:21 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 29 04:08:21 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 29 04:08:21 node-4 kernel: [    0.000000] Memory: 32653456K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 29 04:08:21 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 29 04:08:21 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 29 04:08:21 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 29 04:08:21 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 29 04:08:21 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 29 04:08:21 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 29 04:08:21 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 29 04:08:21 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 29 04:08:21 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 29 04:08:21 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 29 04:08:21 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 29 04:08:21 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 29 04:08:21 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 29 04:08:21 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 29 04:08:21 node-4 kernel: [    0.004000] tsc: Detected 3491.927 MHz processor
Jul 29 04:08:21 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.85 BogoMIPS (lpj=13967708)
Jul 29 04:08:21 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 29 04:08:21 node-4 kernel: [    0.000043] Security Framework initialized
Jul 29 04:08:21 node-4 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 29 04:08:21 node-4 kernel: [    0.000063] Yama: becoming mindful.
Jul 29 04:08:21 node-4 kernel: [    0.001453] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.006398] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.008324] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.008351] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.008645] Initializing cgroup subsys memory
Jul 29 04:08:21 node-4 kernel: [    0.008653] Initializing cgroup subsys devices
Jul 29 04:08:21 node-4 kernel: [    0.008655] Initializing cgroup subsys freezer
Jul 29 04:08:21 node-4 kernel: [    0.008657] Initializing cgroup subsys blkio
Jul 29 04:08:21 node-4 kernel: [    0.008659] Initializing cgroup subsys perf_event
Jul 29 04:08:21 node-4 kernel: [    0.008661] Initializing cgroup subsys hugetlb
Jul 29 04:08:21 node-4 kernel: [    0.008681] CPU: Physical Processor ID: 0
Jul 29 04:08:21 node-4 kernel: [    0.008682] CPU: Processor Core ID: 0
Jul 29 04:08:21 node-4 kernel: [    0.008685] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 29 04:08:21 node-4 kernel: [    0.008685] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 29 04:08:21 node-4 kernel: [    0.009379] mce: CPU supports 22 MCE banks
Jul 29 04:08:21 node-4 kernel: [    0.009406] CPU0: Thermal monitoring enabled (TM1)
Jul 29 04:08:21 node-4 kernel: [    0.009427] process: using mwait in idle threads
Jul 29 04:08:21 node-4 kernel: [    0.009430] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 29 04:08:21 node-4 kernel: [    0.009430] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 29 04:08:21 node-4 kernel: [    0.009430] tlb_flushall_shift: 6
Jul 29 04:08:21 node-4 kernel: [    0.009518] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 29 04:08:21 node-4 kernel: [    0.010243] ACPI: Core revision 20131115
Jul 29 04:08:21 node-4 kernel: [    0.022910] ACPI: All ACPI Tables successfully acquired
Jul 29 04:08:21 node-4 kernel: [    0.023060] ftrace: allocating 28617 entries in 112 pages
Jul 29 04:08:21 node-4 kernel: [    0.031869] dmar: Host address width 46
Jul 29 04:08:21 node-4 kernel: [    0.031871] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 29 04:08:21 node-4 kernel: [    0.031877] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 04:08:21 node-4 kernel: [    0.031879] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 29 04:08:21 node-4 kernel: [    0.031883] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 04:08:21 node-4 kernel: [    0.031885] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 29 04:08:21 node-4 kernel: [    0.031886] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 29 04:08:21 node-4 kernel: [    0.031887] dmar: ATSR flags: 0x0
Jul 29 04:08:21 node-4 kernel: [    0.031888] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 29 04:08:21 node-4 kernel: [    0.031889] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 29 04:08:21 node-4 kernel: [    0.032005] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 29 04:08:21 node-4 kernel: [    0.032006] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 04:08:21 node-4 kernel: [    0.032007] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 04:08:21 node-4 kernel: [    0.032008] HPET id 0 under DRHD base 0xc7ffc000
Jul 29 04:08:21 node-4 kernel: [    0.032009] Your BIOS is broken and requested that x2apic be disabled.
Jul 29 04:08:21 node-4 kernel: [    0.032009] This will slightly decrease performance.
Jul 29 04:08:21 node-4 kernel: [    0.032009] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 29 04:08:21 node-4 kernel: [    0.032439] Enabled IRQ remapping in xapic mode
Jul 29 04:08:21 node-4 kernel: [    0.032440] x2apic not enabled, IRQ remapping is in xapic mode
Jul 29 04:08:21 node-4 kernel: [    0.032444] Switched APIC routing to physical flat.
Jul 29 04:08:21 node-4 kernel: [    0.033014] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 29 04:08:21 node-4 kernel: [    0.072664] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 29 04:08:21 node-4 kernel: [    0.072670] TSC deadline timer enabled
Jul 29 04:08:21 node-4 kernel: [    0.072677] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 29 04:08:21 node-4 kernel: [    0.072683] ... version:                3
Jul 29 04:08:21 node-4 kernel: [    0.072684] ... bit width:              48
Jul 29 04:08:21 node-4 kernel: [    0.072685] ... generic registers:      4
Jul 29 04:08:21 node-4 kernel: [    0.072686] ... value mask:             0000ffffffffffff
Jul 29 04:08:21 node-4 kernel: [    0.072687] ... max period:             0000ffffffffffff
Jul 29 04:08:21 node-4 kernel: [    0.072688] ... fixed-purpose events:   3
Jul 29 04:08:21 node-4 kernel: [    0.072689] ... event mask:             000000070000000f
Jul 29 04:08:21 node-4 kernel: [    0.074114] x86: Booting SMP configuration:
Jul 29 04:08:21 node-4 kernel: [    0.088239] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 29 04:08:21 node-4 kernel: [    0.074116] .... node  #0, CPUs:        #1  #2  #3
Jul 29 04:08:21 node-4 kernel: [    0.116156] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 29 04:08:21 node-4 kernel: [    0.270313] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 29 04:08:21 node-4 kernel: [    0.325934] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 29 04:08:21 node-4 kernel: [    0.382991] x86: Booted up 2 nodes, 16 CPUs
Jul 29 04:08:21 node-4 kernel: [    0.382995] smpboot: Total of 16 processors activated (111754.26 BogoMIPS)
Jul 29 04:08:21 node-4 kernel: [    0.407961] devtmpfs: initialized
Jul 29 04:08:21 node-4 kernel: [    0.411345] EVM: security.selinux
Jul 29 04:08:21 node-4 kernel: [    0.411347] EVM: security.SMACK64
Jul 29 04:08:21 node-4 kernel: [    0.411348] EVM: security.ima
Jul 29 04:08:21 node-4 kernel: [    0.411349] EVM: security.capability
Jul 29 04:08:21 node-4 kernel: [    0.411399] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.412059] pinctrl core: initialized pinctrl subsystem
Jul 29 04:08:21 node-4 kernel: [    0.412123] regulator-dummy: no parameters
Jul 29 04:08:21 node-4 kernel: [    0.412154] RTC time:  4:07:45, date: 07/29/16
Jul 29 04:08:21 node-4 kernel: [    0.412190] NET: Registered protocol family 16
Jul 29 04:08:21 node-4 kernel: [    0.412274] cpuidle: using governor ladder
Jul 29 04:08:21 node-4 kernel: [    0.412276] cpuidle: using governor menu
Jul 29 04:08:21 node-4 kernel: [    0.412310] ACPI: bus type PCI registered
Jul 29 04:08:21 node-4 kernel: [    0.412312] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 29 04:08:21 node-4 kernel: [    0.412360] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 29 04:08:21 node-4 kernel: [    0.412362] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 29 04:08:21 node-4 kernel: [    0.426096] PCI: Using configuration type 1 for base access
Jul 29 04:08:21 node-4 kernel: [    0.427098] bio: create slab <bio-0> at 0
Jul 29 04:08:21 node-4 kernel: [    0.427372] ACPI: Added _OSI(Module Device)
Jul 29 04:08:21 node-4 kernel: [    0.427374] ACPI: Added _OSI(Processor Device)
Jul 29 04:08:21 node-4 kernel: [    0.427375] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 29 04:08:21 node-4 kernel: [    0.427376] ACPI: Added _OSI(Processor Aggregator Device)
Jul 29 04:08:21 node-4 kernel: [    0.440021] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 29 04:08:21 node-4 kernel: [    0.450613] ACPI: Interpreter enabled
Jul 29 04:08:21 node-4 kernel: [    0.450618] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 29 04:08:21 node-4 kernel: [    0.450622] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 29 04:08:21 node-4 kernel: [    0.450625] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 29 04:08:21 node-4 kernel: [    0.450632] ACPI: (supports S0 S4 S5)
Jul 29 04:08:21 node-4 kernel: [    0.450633] ACPI: Using IOAPIC for interrupt routing
Jul 29 04:08:21 node-4 kernel: [    0.450673] HEST: Table parsing has been initialized.
Jul 29 04:08:21 node-4 kernel: [    0.450676] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 29 04:08:21 node-4 kernel: [    0.451226] ACPI: No dock devices found.
Jul 29 04:08:21 node-4 kernel: [    0.462800] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 29 04:08:21 node-4 kernel: [    0.462805] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:21 node-4 kernel: [    0.462808] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 04:08:21 node-4 kernel: [    0.462835] PCI host bridge to bus 0000:ff
Jul 29 04:08:21 node-4 kernel: [    0.462837] pci_bus 0000:ff: root bus resource [bus ff]
Jul 29 04:08:21 node-4 kernel: [    0.462845] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 04:08:21 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 29 04:08:21 node-4 kernel: [    0.462883] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.462914] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.462950] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.462980] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.463010] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.463041] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463071] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463102] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463131] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463158] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463185] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463214] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463240] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463267] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463293] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463322] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463349] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463377] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.463406] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463433] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.463460] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463487] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463517] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.463552] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463583] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463613] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463644] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463675] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463706] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463736] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463767] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463797] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463828] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463859] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463890] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463922] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463952] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.463980] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464012] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464045] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464082] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464117] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464150] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464178] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464207] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464239] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464269] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464299] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464330] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464361] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464390] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464421] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464450] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464479] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464510] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464542] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464598] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 29 04:08:21 node-4 kernel: [    0.464601] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:21 node-4 kernel: [    0.464604] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 04:08:21 node-4 kernel: [    0.464622] PCI host bridge to bus 0000:7f
Jul 29 04:08:21 node-4 kernel: [    0.464623] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 29 04:08:21 node-4 kernel: [    0.464628] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464655] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.464683] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464712] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464733] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.464757] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.464783] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464813] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464837] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464861] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464885] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464907] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464930] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464952] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.464976] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465001] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465023] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465045] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465068] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.465091] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465113] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.465135] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465157] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465183] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 04:08:21 node-4 kernel: [    0.465215] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465241] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465268] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465294] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465319] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465345] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465370] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465397] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465423] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465451] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465478] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465506] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465534] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465558] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465583] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465610] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465635] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465661] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465691] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465718] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465744] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465769] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465794] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465820] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465846] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465872] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465900] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465925] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465947] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465971] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.465996] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.466024] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.466050] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.467294] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 29 04:08:21 node-4 kernel: [    0.467297] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:21 node-4 kernel: [    0.468424] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 04:08:21 node-4 kernel: [    0.468935] PCI host bridge to bus 0000:00
Jul 29 04:08:21 node-4 kernel: [    0.468937] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 29 04:08:21 node-4 kernel: [    0.468939] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 29 04:08:21 node-4 kernel: [    0.468940] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 29 04:08:21 node-4 kernel: [    0.468941] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 29 04:08:21 node-4 kernel: [    0.468943] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 29 04:08:21 node-4 kernel: [    0.468944] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 29 04:08:21 node-4 kernel: [    0.468946] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 29 04:08:21 node-4 kernel: [    0.468951] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 29 04:08:21 node-4 kernel: [    0.469036] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.469066] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.469108] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 29 04:08:21 node-4 kernel: [    0.469128] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.469157] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.469197] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 29 04:08:21 node-4 kernel: [    0.469216] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.469245] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.469289] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 29 04:08:21 node-4 kernel: [    0.469306] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.469377] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.469454] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.469528] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 04:08:21 node-4 kernel: [    0.469533] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 29 04:08:21 node-4 kernel: [    0.469617] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 29 04:08:21 node-4 kernel: [    0.469765] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 29 04:08:21 node-4 kernel: [    0.469782] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 29 04:08:21 node-4 kernel: [    0.469860] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.469913] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 29 04:08:21 node-4 kernel: [    0.469934] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.469989] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.470032] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 29 04:08:21 node-4 kernel: [    0.470059] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.470114] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.470157] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 29 04:08:21 node-4 kernel: [    0.470181] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 29 04:08:21 node-4 kernel: [    0.470198] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 29 04:08:21 node-4 kernel: [    0.470276] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.470325] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 29 04:08:21 node-4 kernel: [    0.470351] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 29 04:08:21 node-4 kernel: [    0.470596] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 29 04:08:21 node-4 kernel: [    0.470602] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 29 04:08:21 node-4 kernel: [    0.470608] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.470614] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.470621] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 29 04:08:21 node-4 kernel: [    0.470651] pci 0000:01:00.0: supports D1 D2
Jul 29 04:08:21 node-4 kernel: [    0.476816] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 04:08:21 node-4 kernel: [    0.476832] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 04:08:21 node-4 kernel: [    0.476834] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:21 node-4 kernel: [    0.476940] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.476973] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 29 04:08:21 node-4 kernel: [    0.484813] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 04:08:21 node-4 kernel: [    0.484819] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.484823] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:21 node-4 kernel: [    0.484907] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.484984] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.485083] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.485127] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 04:08:21 node-4 kernel: [    0.485130] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.485132] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:21 node-4 kernel: [    0.485199] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.485323] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.485375] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 04:08:21 node-4 kernel: [    0.485378] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.485380] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.485429] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.485551] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.485589] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.485708] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.485746] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.485865] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.485901] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:21 node-4 kernel: [    0.486022] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:21 node-4 kernel: [    0.486062] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 04:08:21 node-4 kernel: [    0.486064] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.486066] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.486126] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:21 node-4 kernel: [    0.486189] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.486266] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.486306] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 29 04:08:21 node-4 kernel: [    0.486385] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 29 04:08:21 node-4 kernel: [    0.486493] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 04:08:21 node-4 kernel: [    0.486496] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.486498] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.486553] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:21 node-4 kernel: [    0.486608] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.486656] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.486866] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 04:08:21 node-4 kernel: [    0.486870] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:21 node-4 kernel: [    0.486935] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:21 node-4 kernel: [    0.486988] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.487038] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.487269] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 04:08:21 node-4 kernel: [    0.487273] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:21 node-4 kernel: [    0.487332] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:21 node-4 kernel: [    0.487395] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.487447] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 29 04:08:21 node-4 kernel: [    0.487673] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 04:08:21 node-4 kernel: [    0.487676] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:21 node-4 kernel: [    0.487850] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 04:08:21 node-4 kernel: [    0.487888] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 04:08:21 node-4 kernel: [    0.487963] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 29 04:08:21 node-4 kernel: [    0.487982] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 29 04:08:21 node-4 kernel: [    0.487995] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 29 04:08:21 node-4 kernel: [    0.488008] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 29 04:08:21 node-4 kernel: [    0.488058] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 29 04:08:21 node-4 kernel: [    0.492819] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 04:08:21 node-4 kernel: [    0.492828] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:21 node-4 kernel: [    0.492880] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 29 04:08:21 node-4 kernel: [    0.493640] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 29 04:08:21 node-4 kernel: [    0.493643] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:21 node-4 kernel: [    0.493767] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 04:08:21 node-4 kernel: [    0.493874] PCI host bridge to bus 0000:80
Jul 29 04:08:21 node-4 kernel: [    0.493876] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 29 04:08:21 node-4 kernel: [    0.493878] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 29 04:08:21 node-4 kernel: [    0.493879] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 29 04:08:21 node-4 kernel: [    0.493887] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.493950] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.494018] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 04:08:21 node-4 kernel: [    0.494080] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 04:08:21 node-4 kernel: [    0.494086] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 29 04:08:21 node-4 kernel: [    0.494159] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 29 04:08:21 node-4 kernel: [    0.494475] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 29 04:08:21 node-4 kernel: [    0.494506] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 29 04:08:21 node-4 kernel: [    0.494536] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 29 04:08:21 node-4 kernel: [    0.494564] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 29 04:08:21 node-4 kernel: [    0.494593] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:21 node-4 kernel: [    0.494623] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:21 node-4 kernel: [    0.494653] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:21 node-4 kernel: [    0.494682] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:21 node-4 kernel: [    0.494768] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 29 04:08:21 node-4 kernel: [    0.494773] ACPI: \_SB_.UNC1: notify handler is installed
Jul 29 04:08:21 node-4 kernel: [    0.494774] ACPI: \_SB_.UNC0: notify handler is installed
Jul 29 04:08:21 node-4 kernel: [    0.494788] ACPI: \_SB_.PCI0: notify handler is installed
Jul 29 04:08:21 node-4 kernel: [    0.494842] ACPI: \_SB_.PCI1: notify handler is installed
Jul 29 04:08:21 node-4 kernel: [    0.494921] Found 4 acpi root devices
Jul 29 04:08:21 node-4 kernel: [    0.495032] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 29 04:08:21 node-4 kernel: [    0.495034] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 29 04:08:21 node-4 kernel: [    0.495036] vgaarb: loaded
Jul 29 04:08:21 node-4 kernel: [    0.495037] vgaarb: bridge control possible 0000:0c:00.0
Jul 29 04:08:21 node-4 kernel: [    0.495159] SCSI subsystem initialized
Jul 29 04:08:21 node-4 kernel: [    0.495224] libata version 3.00 loaded.
Jul 29 04:08:21 node-4 kernel: [    0.495239] ACPI: bus type USB registered
Jul 29 04:08:21 node-4 kernel: [    0.495249] usbcore: registered new interface driver usbfs
Jul 29 04:08:21 node-4 kernel: [    0.495255] usbcore: registered new interface driver hub
Jul 29 04:08:21 node-4 kernel: [    0.495278] usbcore: registered new device driver usb
Jul 29 04:08:21 node-4 kernel: [    0.495448] PCI: Using ACPI for IRQ routing
Jul 29 04:08:21 node-4 kernel: [    0.499032] PCI: pci_cache_line_size set to 64 bytes
Jul 29 04:08:21 node-4 kernel: [    0.499242] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 29 04:08:21 node-4 kernel: [    0.499243] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 29 04:08:21 node-4 kernel: [    0.499244] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 29 04:08:21 node-4 kernel: [    0.499310] NetLabel: Initializing
Jul 29 04:08:21 node-4 kernel: [    0.499312] NetLabel:  domain hash size = 128
Jul 29 04:08:21 node-4 kernel: [    0.499313] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 29 04:08:21 node-4 kernel: [    0.499323] NetLabel:  unlabeled traffic allowed by default
Jul 29 04:08:21 node-4 kernel: [    0.499379] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 29 04:08:21 node-4 kernel: [    0.499384] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 29 04:08:21 node-4 kernel: [    0.501453] Switched to clocksource hpet
Jul 29 04:08:21 node-4 kernel: [    0.505986] AppArmor: AppArmor Filesystem Enabled
Jul 29 04:08:21 node-4 kernel: [    0.506025] pnp: PnP ACPI init
Jul 29 04:08:21 node-4 kernel: [    0.506037] ACPI: bus type PNP registered
Jul 29 04:08:21 node-4 kernel: [    0.506218] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506229] pnp 00:01: [dma 4]
Jul 29 04:08:21 node-4 kernel: [    0.506247] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506281] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506306] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506326] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506374] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506486] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506488] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 29 04:08:21 node-4 kernel: [    0.506490] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506491] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506493] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506494] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506498] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 29 04:08:21 node-4 kernel: [    0.506500] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506501] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506503] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506504] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506506] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506507] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 29 04:08:21 node-4 kernel: [    0.506510] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506610] pnp 00:07: [dma 0 disabled]
Jul 29 04:08:21 node-4 kernel: [    0.506643] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506723] pnp 00:08: [dma 0 disabled]
Jul 29 04:08:21 node-4 kernel: [    0.506759] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 04:08:21 node-4 kernel: [    0.506816] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 29 04:08:21 node-4 kernel: [    0.507258] pnp: PnP ACPI: found 10 devices
Jul 29 04:08:21 node-4 kernel: [    0.507260] ACPI: bus type PNP unregistered
Jul 29 04:08:21 node-4 kernel: [    0.513280] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 04:08:21 node-4 kernel: [    0.513284] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 04:08:21 node-4 kernel: [    0.513287] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:21 node-4 kernel: [    0.513293] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 04:08:21 node-4 kernel: [    0.513295] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513309] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513338] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 04:08:21 node-4 kernel: [    0.513353] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513382] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 04:08:21 node-4 kernel: [    0.513396] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:21 node-4 kernel: [    0.513430] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 04:08:21 node-4 kernel: [    0.513444] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:21 node-4 kernel: [    0.513474] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 04:08:21 node-4 kernel: [    0.513476] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513494] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513523] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 04:08:21 node-4 kernel: [    0.513525] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513539] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513568] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 04:08:21 node-4 kernel: [    0.513570] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513573] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513578] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 04:08:21 node-4 kernel: [    0.513580] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513583] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513587] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 04:08:21 node-4 kernel: [    0.513593] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 04:08:21 node-4 kernel: [    0.513602] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 04:08:21 node-4 kernel: [    0.513605] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:21 node-4 kernel: [    0.513612] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 29 04:08:21 node-4 kernel: [    0.513613] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 29 04:08:21 node-4 kernel: [    0.513614] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 29 04:08:21 node-4 kernel: [    0.513615] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 29 04:08:21 node-4 kernel: [    0.513616] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 29 04:08:21 node-4 kernel: [    0.513617] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 29 04:08:21 node-4 kernel: [    0.513618] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 29 04:08:21 node-4 kernel: [    0.513619] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:21 node-4 kernel: [    0.513620] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513621] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513622] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513623] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513624] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513625] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513626] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513627] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513628] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:21 node-4 kernel: [    0.513629] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513630] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:21 node-4 kernel: [    0.513631] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:21 node-4 kernel: [    0.513632] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:21 node-4 kernel: [    0.513633] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:21 node-4 kernel: [    0.513636] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 29 04:08:21 node-4 kernel: [    0.513637] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 29 04:08:21 node-4 kernel: [    0.513677] NET: Registered protocol family 2
Jul 29 04:08:21 node-4 kernel: [    0.513979] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.514362] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.514530] TCP: Hash tables configured (established 262144 bind 65536)
Jul 29 04:08:21 node-4 kernel: [    0.514576] TCP: reno registered
Jul 29 04:08:21 node-4 kernel: [    0.514609] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.514715] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.514877] NET: Registered protocol family 1
Jul 29 04:08:21 node-4 kernel: [    0.553474] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 29 04:08:21 node-4 kernel: [    0.553482] PCI: CLS 64 bytes, default 64
Jul 29 04:08:21 node-4 kernel: [    0.553525] Trying to unpack rootfs image as initramfs...
Jul 29 04:08:21 node-4 kernel: [    0.775131] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 29 04:08:21 node-4 kernel: [    0.775181] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 29 04:08:21 node-4 kernel: [    0.775183] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 29 04:08:21 node-4 kernel: [    0.775614] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775623] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775631] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775639] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775647] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775653] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775659] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775665] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775673] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775680] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775691] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775698] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775704] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775712] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775718] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775723] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:21 node-4 kernel: [    0.775781] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 29 04:08:21 node-4 kernel: [    0.775784] Scanning for low memory corruption every 60 seconds
Jul 29 04:08:21 node-4 kernel: [    0.776370] Initialise system trusted keyring
Jul 29 04:08:21 node-4 kernel: [    0.776417] audit: initializing netlink socket (disabled)
Jul 29 04:08:21 node-4 kernel: [    0.776428] type=2000 audit(1469765264.728:1): initialized
Jul 29 04:08:21 node-4 kernel: [    0.794404] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 29 04:08:21 node-4 kernel: [    0.795909] zbud: loaded
Jul 29 04:08:21 node-4 kernel: [    0.796047] VFS: Disk quotas dquot_6.5.2
Jul 29 04:08:21 node-4 kernel: [    0.796095] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 29 04:08:21 node-4 kernel: [    0.796456] fuse init (API version 7.22)
Jul 29 04:08:21 node-4 kernel: [    0.796512] msgmni has been set to 32768
Jul 29 04:08:21 node-4 kernel: [    0.796557] Key type big_key registered
Jul 29 04:08:21 node-4 kernel: [    0.797066] Key type asymmetric registered
Jul 29 04:08:21 node-4 kernel: [    0.797068] Asymmetric key parser 'x509' registered
Jul 29 04:08:21 node-4 kernel: [    0.797091] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 29 04:08:21 node-4 kernel: [    0.797158] io scheduler noop registered
Jul 29 04:08:21 node-4 kernel: [    0.797160] io scheduler deadline registered (default)
Jul 29 04:08:21 node-4 kernel: [    0.797177] io scheduler cfq registered
Jul 29 04:08:21 node-4 kernel: [    0.797682] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    0.797869] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    0.797981] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    0.798101] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    0.798218] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    0.798338] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    0.798732] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 29 04:08:21 node-4 kernel: [    0.798758] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 29 04:08:21 node-4 kernel: [    0.798774] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 29 04:08:21 node-4 kernel: [    0.798787] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798789] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798791] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:21 node-4 kernel: [    0.798797] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798798] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798799] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798801] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798802] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798804] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798805] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798807] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798808] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798809] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798811] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798812] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798815] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:21 node-4 kernel: [    0.798828] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798830] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:21 node-4 kernel: [    0.798847] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798851] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:21 node-4 kernel: [    0.798861] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798863] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:21 node-4 kernel: [    0.798866] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 29 04:08:21 node-4 kernel: [    0.798906] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 29 04:08:21 node-4 kernel: [    0.798912] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 29 04:08:21 node-4 kernel: [    0.798916] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 29 04:08:21 node-4 kernel: [    0.798924] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 29 04:08:21 node-4 kernel: [    0.798961] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 29 04:08:21 node-4 kernel: [    0.798963] vesafb: scrolling: redraw
Jul 29 04:08:21 node-4 kernel: [    0.798964] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 29 04:08:21 node-4 kernel: [    0.819381] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 29 04:08:21 node-4 kernel: [    0.827857] Console: switching to colour frame buffer device 80x30
Jul 29 04:08:21 node-4 kernel: [    0.836527] fb0: VESA VGA frame buffer device
Jul 29 04:08:21 node-4 kernel: [    0.836726] intel_idle: MWAIT substates: 0x2120
Jul 29 04:08:21 node-4 kernel: [    0.836727] intel_idle: v0.4 model 0x3F
Jul 29 04:08:21 node-4 kernel: [    0.836728] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 29 04:08:21 node-4 kernel: [    0.836942] ipmi message handler version 39.2
Jul 29 04:08:21 node-4 kernel: [    0.837219] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 29 04:08:21 node-4 kernel: [    0.837649] ACPI: AC Adapter [P111] (on-line)
Jul 29 04:08:21 node-4 kernel: [    0.842887] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 29 04:08:21 node-4 kernel: [    0.853889] ACPI: Power Button [PWRB]
Jul 29 04:08:21 node-4 kernel: [    0.859643] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 29 04:08:21 node-4 kernel: [    0.871276] ACPI: Power Button [PWRF]
Jul 29 04:08:21 node-4 kernel: [    0.886931] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 29 04:08:21 node-4 kernel: [    0.898670] pstore: Registered erst as persistent store backend
Jul 29 04:08:21 node-4 kernel: [    0.904901] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 29 04:08:21 node-4 kernel: [    0.916896] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 29 04:08:21 node-4 kernel: [    0.943681] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 29 04:08:21 node-4 kernel: [    0.977158] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 29 04:08:21 node-4 kernel: [    0.991224] Linux agpgart interface v0.103
Jul 29 04:08:21 node-4 kernel: [    0.998846] brd: module loaded
Jul 29 04:08:21 node-4 kernel: [    1.005922] loop: module loaded
Jul 29 04:08:21 node-4 kernel: [    1.012635] libphy: Fixed MDIO Bus: probed
Jul 29 04:08:21 node-4 kernel: [    1.019112] tun: Universal TUN/TAP device driver, 1.6
Jul 29 04:08:21 node-4 kernel: [    1.025602] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 29 04:08:21 node-4 kernel: [    1.032135] PPP generic driver version 2.4.2
Jul 29 04:08:21 node-4 kernel: [    1.038533] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 29 04:08:21 node-4 kernel: [    1.045018] ehci-pci: EHCI PCI platform driver
Jul 29 04:08:21 node-4 kernel: [    1.051631] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 29 04:08:21 node-4 kernel: [    1.058052] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 29 04:08:21 node-4 kernel: [    1.070607] ehci-pci 0000:00:1a.0: debug port 2
Jul 29 04:08:21 node-4 kernel: [    1.080813] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 29 04:08:21 node-4 kernel: [    1.080832] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 29 04:08:21 node-4 kernel: [    1.096940] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 29 04:08:21 node-4 kernel: [    1.103014] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 04:08:21 node-4 kernel: [    1.109230] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 04:08:21 node-4 kernel: [    1.121155] usb usb1: Product: EHCI Host Controller
Jul 29 04:08:21 node-4 kernel: [    1.127201] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 04:08:21 node-4 kernel: [    1.133268] usb usb1: SerialNumber: 0000:00:1a.0
Jul 29 04:08:21 node-4 kernel: [    1.139251] hub 1-0:1.0: USB hub found
Jul 29 04:08:21 node-4 kernel: [    1.145023] hub 1-0:1.0: 2 ports detected
Jul 29 04:08:21 node-4 kernel: [    1.150822] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 29 04:08:21 node-4 kernel: [    1.156398] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 29 04:08:21 node-4 kernel: [    1.167294] ehci-pci 0000:00:1d.0: debug port 2
Jul 29 04:08:21 node-4 kernel: [    1.176587] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 29 04:08:21 node-4 kernel: [    1.176590] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 29 04:08:21 node-4 kernel: [    1.192858] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 29 04:08:21 node-4 kernel: [    1.198061] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 04:08:21 node-4 kernel: [    1.203359] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 04:08:21 node-4 kernel: [    1.213945] usb usb2: Product: EHCI Host Controller
Jul 29 04:08:21 node-4 kernel: [    1.219420] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 04:08:21 node-4 kernel: [    1.224966] usb usb2: SerialNumber: 0000:00:1d.0
Jul 29 04:08:21 node-4 kernel: [    1.230509] hub 2-0:1.0: USB hub found
Jul 29 04:08:21 node-4 kernel: [    1.235856] hub 2-0:1.0: 2 ports detected
Jul 29 04:08:21 node-4 kernel: [    1.241167] ehci-platform: EHCI generic platform driver
Jul 29 04:08:21 node-4 kernel: [    1.246398] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 29 04:08:21 node-4 kernel: [    1.251717] ohci-pci: OHCI PCI platform driver
Jul 29 04:08:21 node-4 kernel: [    1.257021] ohci-platform: OHCI generic platform driver
Jul 29 04:08:21 node-4 kernel: [    1.262230] uhci_hcd: USB Universal Host Controller Interface driver
Jul 29 04:08:21 node-4 kernel: [    1.267577] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 29 04:08:21 node-4 kernel: [    1.460637] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 29 04:08:21 node-4 kernel: [    1.772390] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 29 04:08:21 node-4 kernel: [    1.788740] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 29 04:08:21 node-4 kernel: [    1.794340] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 04:08:21 node-4 kernel: [    1.800009] hub 1-1:1.0: USB hub found
Jul 29 04:08:21 node-4 kernel: [    1.805600] hub 1-1:1.0: 6 ports detected
Jul 29 04:08:21 node-4 kernel: [    1.920272] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 29 04:08:21 node-4 kernel: [    2.306332] i8042: No controller found
Jul 29 04:08:21 node-4 kernel: [    2.311866] mousedev: PS/2 mouse device common for all mice
Jul 29 04:08:21 node-4 kernel: [    2.317585] rtc_cmos 00:02: RTC can wake from S4
Jul 29 04:08:21 node-4 kernel: [    2.320734] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 29 04:08:21 node-4 kernel: [    2.320735] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 04:08:21 node-4 kernel: [    2.321495] hub 2-1:1.0: USB hub found
Jul 29 04:08:21 node-4 kernel: [    2.321737] hub 2-1:1.0: 8 ports detected
Jul 29 04:08:21 node-4 kernel: [    2.346028] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 29 04:08:21 node-4 kernel: [    2.351786] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 29 04:08:21 node-4 kernel: [    2.363088] device-mapper: uevent: version 1.0.3
Jul 29 04:08:21 node-4 kernel: [    2.368792] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 29 04:08:21 node-4 kernel: [    2.380146] ledtrig-cpu: registered to indicate activity on CPUs
Jul 29 04:08:21 node-4 kernel: [    2.386116] TCP: cubic registered
Jul 29 04:08:21 node-4 kernel: [    2.391964] NET: Registered protocol family 10
Jul 29 04:08:21 node-4 kernel: [    2.398014] NET: Registered protocol family 17
Jul 29 04:08:21 node-4 kernel: [    2.403771] Key type dns_resolver registered
Jul 29 04:08:21 node-4 kernel: [    2.409829] Loading compiled-in X.509 certificates
Jul 29 04:08:21 node-4 kernel: [    2.416034] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 29 04:08:21 node-4 kernel: [    2.427644] registered taskstats version 1
Jul 29 04:08:21 node-4 kernel: [    2.435670] Key type trusted registered
Jul 29 04:08:21 node-4 kernel: [    2.443280] Key type encrypted registered
Jul 29 04:08:21 node-4 kernel: [    2.448758] AppArmor: AppArmor sha1 policy hashing enabled
Jul 29 04:08:21 node-4 kernel: [    2.454249] IMA: No TPM chip found, activating TPM-bypass!
Jul 29 04:08:21 node-4 kernel: [    2.460344] regulator-dummy: disabling
Jul 29 04:08:21 node-4 kernel: [    2.465827]   Magic number: 8:671:111
Jul 29 04:08:21 node-4 kernel: [    2.471559] rtc_cmos 00:02: setting system clock to 2016-07-29 04:07:47 UTC (1469765267)
Jul 29 04:08:21 node-4 kernel: [    2.484038] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 29 04:08:21 node-4 kernel: [    2.489708] EDD information not available.
Jul 29 04:08:21 node-4 kernel: [    2.495343] PM: Hibernation image not present or could not be loaded.
Jul 29 04:08:21 node-4 kernel: [    2.496226] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 29 04:08:21 node-4 kernel: [    2.507545] Write protecting the kernel read-only data: 12288k
Jul 29 04:08:21 node-4 kernel: [    2.513832] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 29 04:08:21 node-4 kernel: [    2.526756] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 29 04:08:21 node-4 kernel: [    2.558922] device-mapper: multipath: version 1.6.0 loaded
Jul 29 04:08:21 node-4 kernel: [    2.566855] systemd-udevd[216]: starting version 204
Jul 29 04:08:21 node-4 kernel: [    2.587518] md: linear personality registered for level -1
Jul 29 04:08:21 node-4 kernel: [    2.595886] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 29 04:08:21 node-4 kernel: [    2.607916] md: multipath personality registered for level -4
Jul 29 04:08:21 node-4 kernel: [    2.615911] md: raid0 personality registered for level 0
Jul 29 04:08:21 node-4 kernel: [    2.624604] md: raid1 personality registered for level 1
Jul 29 04:08:21 node-4 kernel: [    2.631030] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 29 04:08:21 node-4 kernel: [    2.637397] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 29 04:08:21 node-4 kernel: [    2.643746] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 29 04:08:21 node-4 kernel: [    2.644109] megasas: FW now in Ready state
Jul 29 04:08:21 node-4 kernel: [    2.644206] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644250] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644294] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644353] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644396] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644436] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644472] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644510] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644549] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644585] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644622] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644665] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644703] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644713] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644750] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644794] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.644980] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 29 04:08:21 node-4 kernel: [    2.676531] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 29 04:08:21 node-4 kernel: [    2.689945] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 04:08:21 node-4 kernel: [    2.703762] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:21 node-4 kernel: [    2.710746] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.710752] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.710757] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.710762] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.710807] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:21 node-4 kernel: [    2.734401] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 29 04:08:21 node-4 kernel: [    2.739560] raid6: sse2x1    9889 MB/s
Jul 29 04:08:21 node-4 kernel: [    2.754481] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 04:08:21 node-4 kernel: [    2.767878] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:21 node-4 kernel: [    2.807495] raid6: sse2x2   11586 MB/s
Jul 29 04:08:21 node-4 kernel: [    2.879440] raid6: sse2x4   10116 MB/s
Jul 29 04:08:21 node-4 kernel: [    2.951380] raid6: avx2x1   14942 MB/s
Jul 29 04:08:21 node-4 kernel: [    3.023315] raid6: avx2x2   18863 MB/s
Jul 29 04:08:21 node-4 kernel: [    3.095258] raid6: avx2x4   21399 MB/s
Jul 29 04:08:21 node-4 kernel: [    3.101220] raid6: using algorithm avx2x4 (21399 MB/s)
Jul 29 04:08:21 node-4 kernel: [    3.107139] raid6: using avx2x2 recovery algorithm
Jul 29 04:08:21 node-4 kernel: [    3.112962] Switched to clocksource tsc
Jul 29 04:08:21 node-4 kernel: [    3.112966] megasas:IOC Init cmd success
Jul 29 04:08:21 node-4 kernel: [    3.113007] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.113048] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.113088] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.113122] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.113217] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.114774] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 29 04:08:21 node-4 kernel: [    3.114775] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 04:08:21 node-4 kernel: [    3.114775] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 29 04:08:21 node-4 kernel: [    3.114776] usb 2-1.4: Manufacturer: Avocent
Jul 29 04:08:21 node-4 kernel: [    3.114777] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 29 04:08:21 node-4 kernel: [    3.121475] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 29 04:08:21 node-4 kernel: [    3.121476] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 04:08:21 node-4 kernel: [    3.121477] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:21 node-4 kernel: [    3.121539] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.121569] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.121607] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.121647] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.121727] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.132469] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 29 04:08:21 node-4 kernel: [    3.132470] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 04:08:21 node-4 kernel: [    3.132471] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:21 node-4 kernel: [    3.132532] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.132570] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.132603] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.132639] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.132711] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:21 node-4 kernel: [    3.135246] megasas: INIT adapter done
Jul 29 04:08:21 node-4 kernel: [    3.207162] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 29 04:08:21 node-4 kernel: [    3.207490] scsi0 : LSI SAS based MegaRAID driver
Jul 29 04:08:21 node-4 kernel: [    3.211220] xor: automatically using best checksumming function:
Jul 29 04:08:21 node-4 kernel: [    3.214566] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 04:08:21 node-4 kernel: [    3.222505] hidraw: raw HID events driver (C) Jiri Kosina
Jul 29 04:08:21 node-4 kernel: [    3.225281] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 04:08:21 node-4 kernel: [    3.229195] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 29 04:08:21 node-4 kernel: [    3.229274] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 29 04:08:21 node-4 kernel: [    3.229505] sd 0:2:0:0: [sda] Write Protect is off
Jul 29 04:08:21 node-4 kernel: [    3.229507] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 29 04:08:21 node-4 kernel: [    3.229576] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 29 04:08:21 node-4 kernel: [    3.251259]    avx       : 36357.000 MB/sec
Jul 29 04:08:21 node-4 kernel: [    3.258801]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 29 04:08:21 node-4 kernel: [    3.260354] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 29 04:08:21 node-4 kernel: [    3.309929] usbcore: registered new interface driver usbhid
Jul 29 04:08:21 node-4 kernel: [    3.309929] usbhid: USB HID core driver
Jul 29 04:08:21 node-4 kernel: [    3.365420] async_tx: api initialized (async)
Jul 29 04:08:21 node-4 kernel: [    3.384331] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 29 04:08:21 node-4 kernel: [    3.397237] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 29 04:08:21 node-4 kernel: [    3.410072] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 29 04:08:21 node-4 kernel: [    3.422880] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 29 04:08:21 node-4 kernel: [    3.436296] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 29 04:08:21 node-4 kernel: [    3.442969] random: lvm urandom read with 31 bits of entropy available
Jul 29 04:08:21 node-4 kernel: [    3.457054] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 29 04:08:21 node-4 kernel: [    3.457303] md: raid6 personality registered for level 6
Jul 29 04:08:21 node-4 kernel: [    3.457304] md: raid5 personality registered for level 5
Jul 29 04:08:21 node-4 kernel: [    3.457304] md: raid4 personality registered for level 4
Jul 29 04:08:21 node-4 kernel: [    3.495319] md: raid10 personality registered for level 10
Jul 29 04:08:21 node-4 kernel: [    3.550586] multipathd (372): /proc/372/oom_adj is deprecated, please use /proc/372/oom_score_adj instead.
Jul 29 04:08:21 node-4 kernel: [    3.624290] bio: create slab <bio-1> at 1
Jul 29 04:08:21 node-4 kernel: [    4.359904] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:21 node-4 kernel: [    5.045629] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 29 04:08:21 node-4 kernel: [    5.103104] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 29 04:08:21 node-4 kernel: [    5.216457] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:21 node-4 kernel: [    5.264374] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:21 node-4 kernel: [    5.307737] random: nonblocking pool is initialized
Jul 29 04:08:21 node-4 kernel: [    5.339681] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:21 node-4 kernel: [    5.541588] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 29 04:08:21 node-4 kernel: [    5.600333] XFS (dm-0): Mounting Filesystem
Jul 29 04:08:21 node-4 kernel: [    6.008496] XFS (dm-0): Ending clean mount
Jul 29 04:08:21 node-4 kernel: [    6.073968] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:21 node-4 kernel: [    6.108889] XFS (dm-1): Mounting Filesystem
Jul 29 04:08:21 node-4 kernel: [    6.192182] XFS (dm-1): Ending clean mount
Jul 29 04:08:21 node-4 kernel: [    8.320323] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:21 node-4 kernel: [    8.348609] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:21 node-4 kernel: [    8.526990] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 29 04:08:21 node-4 kernel: [    8.526995] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 29 04:08:21 node-4 kernel: [    8.526999] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 29 04:08:21 node-4 kernel: [    8.527002] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 29 04:08:21 node-4 kernel: [    8.564969] systemd-udevd[778]: starting version 204
Jul 29 04:08:21 node-4 kernel: [    8.760876] power_meter ACPI000D:00: Found ACPI power meter.
Jul 29 04:08:21 node-4 kernel: [    8.760885] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 29 04:08:21 node-4 kernel: [    8.800073] wmi: Mapper loaded
Jul 29 04:08:21 node-4 kernel: [    8.821380] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 29 04:08:21 node-4 kernel: [    8.821387] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 04:08:21 node-4 kernel: [    8.821391] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 29 04:08:21 node-4 kernel: [    8.821393] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 04:08:21 node-4 kernel: [    8.821416] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 29 04:08:21 node-4 kernel: [    8.825577] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 29 04:08:21 node-4 kernel: [    8.827469] IPMI System Interface driver.
Jul 29 04:08:21 node-4 kernel: [    8.827498] ipmi_si: probing via ACPI
Jul 29 04:08:21 node-4 kernel: [    8.827519] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 29 04:08:21 node-4 kernel: [    8.827520] ipmi_si: Adding ACPI-specified kcs state machine
Jul 29 04:08:21 node-4 kernel: [    8.827527] ipmi_si: probing via SMBIOS
Jul 29 04:08:21 node-4 kernel: [    8.827528] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 04:08:21 node-4 kernel: [    8.827529] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 29 04:08:21 node-4 kernel: [    8.827530] ipmi_si: probing via SPMI
Jul 29 04:08:21 node-4 kernel: [    8.827531] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 04:08:21 node-4 kernel: [    8.827532] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 29 04:08:21 node-4 kernel: [    8.827533] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 29 04:08:21 node-4 kernel: [    8.886930] systemd-udevd[808]: renamed network interface eth2 to enp8s0
Jul 29 04:08:21 node-4 kernel: [    8.914731] systemd-udevd[797]: renamed network interface eth0 to enp6s0
Jul 29 04:08:21 node-4 kernel: [    8.934695] systemd-udevd[818]: renamed network interface eth3 to enp9s0
Jul 29 04:08:21 node-4 kernel: [    8.957033] systemd-udevd[807]: renamed network interface eth1 to enp7s0
Jul 29 04:08:21 node-4 kernel: [    8.976084] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 29 04:08:21 node-4 kernel: [    8.976089] ipmi_si 00:09: IPMI kcs interface initialized
Jul 29 04:08:21 node-4 kernel: [    9.283362] type=1400 audit(1469765274.315:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.283514] type=1400 audit(1469765274.315:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.283641] type=1400 audit(1469765274.315:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.285486] type=1400 audit(1469765274.315:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1071 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.285631] type=1400 audit(1469765274.315:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1071 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.285754] type=1400 audit(1469765274.315:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1071 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.291254] type=1400 audit(1469765274.323:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.291405] type=1400 audit(1469765274.323:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1069 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.291524] type=1400 audit(1469765274.323:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1069 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.298933] type=1400 audit(1469765274.331:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1068 comm="apparmor_parser"
Jul 29 04:08:21 node-4 kernel: [    9.863874] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:21 node-4 kernel: [    9.898162] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:21 node-4 kernel: [   10.060932] enic 0000:06:00.0 enp6s0: Link UP
Jul 29 04:08:21 node-4 kernel: [   10.061444] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 29 04:08:21 node-4 kernel: [   10.061453] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 29 04:08:21 node-4 kernel: [   19.371092] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 04:08:22 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 29 04:08:22 node-4 kernel: [   38.074793] init: failsafe main process (8396) killed by TERM signal
Jul 29 04:08:23 node-4 dbus[8448]: [system] AppArmor D-Bus mediation is enabled
Jul 29 04:08:23 node-4 kernel: [   38.273393] audit_printk_skb: 30 callbacks suppressed
Jul 29 04:08:23 node-4 kernel: [   38.273395] type=1400 audit(1469765303.124:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8523 comm="apparmor_parser"
Jul 29 04:08:23 node-4 kernel: [   38.273399] type=1400 audit(1469765303.124:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8523 comm="apparmor_parser"
Jul 29 04:08:23 node-4 kernel: [   38.273402] type=1400 audit(1469765303.124:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8523 comm="apparmor_parser"
Jul 29 04:08:23 node-4 kernel: [   38.273620] type=1400 audit(1469765303.124:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8523 comm="apparmor_parser"
Jul 29 04:08:23 node-4 kernel: [   38.273622] type=1400 audit(1469765303.124:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8523 comm="apparmor_parser"
Jul 29 04:08:23 node-4 kernel: [   38.273735] type=1400 audit(1469765303.124:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8523 comm="apparmor_parser"
Jul 29 04:08:23 node-4 kernel: [   38.278377] type=1400 audit(1469765303.132:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8524 comm="apparmor_parser"
Jul 29 04:08:23 node-4 kernel: [   38.350837] type=1400 audit(1469765303.204:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8526 comm="apparmor_parser"
Jul 29 04:08:23 node-4 anacron[8589]: Anacron 2.3 started on 2016-07-29
Jul 29 04:08:23 node-4 cron[8554]: (CRON) INFO (pidfile fd = 3)
Jul 29 04:08:23 node-4 anacron[8589]: Will run job `cron.daily' in 5 min.
Jul 29 04:08:23 node-4 anacron[8589]: Will run job `cron.weekly' in 10 min.
Jul 29 04:08:23 node-4 anacron[8589]: Will run job `cron.monthly' in 15 min.
Jul 29 04:08:23 node-4 anacron[8589]: Jobs will be executed sequentially
Jul 29 04:08:23 node-4 cron[8597]: (CRON) STARTUP (fork ok)
Jul 29 04:08:23 node-4 multipathd: path checkers start up
Jul 29 04:08:23 node-4 cron[8597]: (CRON) INFO (Running @reboot jobs)
Jul 29 04:08:23 node-4 postfix/master[8733]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 29 04:08:26 node-4 puppet-agent[8918]: Reopening log files
Jul 29 04:08:27 node-4 puppet-agent[8918]: Could not request certificate: Connection refused - connect(2)
Jul 29 04:08:42 node-4 puppet-user[8997]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 29 04:08:42 node-4 puppet-user[8997]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 29 04:08:42 node-4 puppet-user[8997]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 29 04:08:42 node-4 puppet-user[8997]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 29 04:08:42 node-4 puppet-user[8997]: Finished catalog run in 0.47 seconds
Jul 29 04:08:43 node-4 multipathd: uevent trigger error
Jul 29 04:08:44 node-4 puppet-user[9470]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 04:08:44 node-4 puppet-user[9470]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 29 04:08:44 node-4 puppet-user[9470]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 29 04:08:44 node-4 puppet-user[9470]: Finished catalog run in 0.06 seconds
Jul 29 04:08:45 node-4 puppet-user[10016]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 29 04:08:45 node-4 puppet-user[10016]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 29 04:08:45 node-4 puppet-user[10016]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 29 04:08:45 node-4 puppet-user[10016]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 29 04:08:45 node-4 puppet-user[10016]: Finished catalog run in 0.03 seconds
Jul 29 04:08:47 node-4 puppet-user[10473]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 29 04:08:47 node-4 puppet-user[10473]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 29 04:08:47 node-4 puppet-user[10473]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 29 04:08:47 node-4 puppet-user[10473]: Finished catalog run in 0.04 seconds
Jul 29 04:08:48 node-4 puppet-user[10919]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 29 04:08:48 node-4 puppet-user[10919]: Compiled catalog for node-4.domain.tld in environment production in 0.18 seconds
Jul 29 04:08:48 node-4 puppet-user[10919]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 29 04:08:49 node-4 puppet-user[10919]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 29 04:08:49 node-4 puppet-user[10919]: Finished catalog run in 0.47 seconds
Jul 29 04:08:50 node-4 puppet-user[11397]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 29 04:08:50 node-4 puppet-user[11397]: Compiled catalog for node-4.domain.tld in environment production in 0.21 seconds
Jul 29 04:08:50 node-4 puppet-user[11397]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 29 04:08:50 node-4 puppet-user[11397]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 29 04:08:50 node-4 puppet-user[11397]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 29 04:08:50 node-4 puppet-user[11397]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 29 04:08:50 node-4 puppet-user[11397]: Finished catalog run in 0.22 seconds
Jul 29 04:08:52 node-4 puppet-user[11874]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 29 04:08:52 node-4 puppet-user[11874]: Compiled catalog for node-4.domain.tld in environment production in 0.14 seconds
Jul 29 04:08:52 node-4 puppet-user[11874]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 29 04:08:52 node-4 kernel: [   67.607853] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 29 04:08:52 node-4 kernel: [   67.607907] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 29 04:08:52 node-4 puppet-user[11874]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 29 04:08:52 node-4 puppet-user[11874]: Finished catalog run in 0.06 seconds
Jul 29 04:08:54 node-4 puppet-user[12345]: (Scope(Class[main])) MODULAR: sync_time
Jul 29 04:08:54 node-4 puppet-user[12345]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 29 04:08:54 node-4 ntpdate[12760]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 29 04:09:00 node-4 ntpdate[12760]: adjust time server 10.20.0.2 offset 0.101999 sec
Jul 29 04:09:00 node-4 puppet-user[12345]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 29 04:09:00 node-4 puppet-user[12345]: Finished catalog run in 6.16 seconds
Jul 29 04:09:01 node-4 CRON[13096]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 04:09:07 node-4 puppet-user[13153]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 04:09:07 node-4 puppet-user[13153]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Jul 29 04:09:07 node-4 puppet-user[13153]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 29 04:09:07 node-4 puppet-user[13153]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 29 04:09:07 node-4 puppet-user[13153]: Finished catalog run in 0.08 seconds
Jul 29 04:09:08 node-4 kernel: [   83.152239] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 04:09:08 node-4 puppet-agent[8918]: Could not run: SIGTERM
Jul 29 04:09:08 node-4 kernel: [   83.410659] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 04:09:08 node-4 ec2: 
Jul 29 04:09:08 node-4 ec2: #############################################################
Jul 29 04:09:08 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 29 04:09:08 node-4 ec2: 1024 e9:7d:f4:96:55:ee:2d:63:e3:60:9a:d4:19:fa:9d:f0  root@node-4.domain.tld (DSA)
Jul 29 04:09:08 node-4 ec2: 256 d7:43:d0:bc:09:21:42:6c:14:38:6e:e4:d0:df:f2:77  root@node-4.domain.tld (ECDSA)
Jul 29 04:09:08 node-4 ec2: 256 19:cf:a9:09:7a:2d:a3:71:31:d9:bd:60:ab:5d:8f:cf  root@node-4.domain.tld (ED25519)
Jul 29 04:09:08 node-4 ec2: 2048 f7:52:fc:f6:97:53:6c:5d:67:af:25:eb:2c:95:d5:00  root@node-4.domain.tld (RSA)
Jul 29 04:09:08 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 29 04:09:08 node-4 ec2: #############################################################
Jul 29 04:09:09 node-4 puppet-user[13741]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 29 04:09:10 node-4 puppet-user[13741]: Compiled catalog for node-4.domain.tld in environment production in 1.22 seconds
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 29 04:09:10 node-4 puppet-user[13741]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 29 04:09:28 node-4 puppet-user[13741]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 29 04:09:28 node-4 puppet-user[13741]: Finished catalog run in 18.25 seconds
Jul 29 04:09:30 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:09:30 node-4 nailgun-agent: D, [2016-07-29T04:09:01.593161 #13099] DEBUG -- : Sleep for 29 seconds before sending request
Jul 29 04:09:30 node-4 nailgun-agent: I, [2016-07-29T04:09:30.616212 #13099]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 04:09:31 node-4 nailgun-agent: D, [2016-07-29T04:09:31.293754 #13099] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 29 04:09:31 node-4 puppet-user[14890]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 29 04:09:31 node-4 puppet-user[14890]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Jul 29 04:09:35 node-4 puppet-user[14890]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.554091 #13099] DEBUG -- : Trying to find block devices
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.554337 #13099] DEBUG -- : Found block device: sda
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.554446 #13099] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.554514 #13099] DEBUG -- : Trying to get list of physical devices
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.554941 #13099] DEBUG -- : Getting udev properties for device: sda
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.558593 #13099] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc788
Jul 29 04:09:43 node-4 nailgun-agent: 6005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16921", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.558665 #13099] DEBUG -- : Trying to find out if device sda is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.558778 #13099] DEBUG -- : Device sda removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.558871 #13099] DEBUG -- : Device sda seems to be appropriate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.560009 #13099] DEBUG -- : Getting udev properties for device: dm-0
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.563280 #13099] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-h3z4k0T2K3xkb2ErCpPesSXR1rOZuUDur0mIMRFUnin1VoyvmeMUQic4FmwxZxgm /dev/disk/by-uuid/85c2ada7-946f-42eb-a863-b30dafdee299 /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-h3z4k0T2K3xkb2ErCpPesSXR1rOZuUDur0mIMRFUnin1VoyvmeMUQic4FmwxZxgm", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"85c2ada7-946f-42eb-a863-b30dafdee299", "ID_FS_UUID_ENC"=>"85c2ada7-946f-42eb-a863-b30dafdee299", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81386", "nomdmonddf"=>"1", "nom
Jul 29 04:09:43 node-4 nailgun-agent: dmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.563354 #13099] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.563444 #13099] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.563484 #13099] DEBUG -- : Device dm-0 seems to be appropriate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.563527 #13099] DEBUG -- : Getting udev properties for device: dm-1
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.566917 #13099] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-QW5I7ZOF1Z1es73sufpVXnPTWntNrwK8JKcG6LqxYMZFrZvm3TBRkGnrP3ZFgdQ2 /dev/disk/by-uuid/90725ce0-fd37-483f-a059-338cd8d5cec8 /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-QW5I7ZOF1Z1es73sufpVXnPTWntNrwK8JKcG6LqxYMZFrZvm3TBRkGnrP3ZFgdQ2", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"90725ce0-fd37-483f-a059-338cd8d5cec8", "ID_FS_UUID_ENC"=>"90725ce0-fd37-483f-a059-338cd8d5cec8", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9
Jul 29 04:09:43 node-4 nailgun-agent: 524", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.566991 #13099] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.567195 #13099] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.567235 #13099] DEBUG -- : Device dm-1 seems to be appropriate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.567278 #13099] DEBUG -- : Getting udev properties for device: dm-2
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.570676 #13099] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-NaGRIYhZcFFCRFsfD26XYiG15FzBccth6eGGm1RslpF0svyOQpFNsyj9j8gnizda /dev/disk/by-uuid/08de8acb-feaa-42fc-8906-25815685159f /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-NaGRIYhZcFFCRFsfD26XYiG15FzBccth6eGGm1RslpF0svyOQpFNsyj9j8gnizda", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"08de8acb-feaa-42fc-8906-25815685159f", "ID_FS_UUID_ENC"=>"08de8acb-feaa-42fc-8906-25815685159f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17490", "nomdmon
Jul 29 04:09:43 node-4 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.570753 #13099] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.570839 #13099] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.570879 #13099] DEBUG -- : Device dm-2 seems to be appropriate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.570975 #13099] DEBUG -- : Getting udev properties for device: dm-3
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.574587 #13099] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-PIgrriq68bZHxA66x47yFThfELJ6BtbeNXSBWnasY64BmUP6by7k7TtYBggNpBgk /dev/disk/by-uuid/313b96b3-3262-418a-a467-1cddfdccd650 /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-PIgrriq68bZHxA66x47yFThfELJ6BtbeNXSBWnasY64BmUP6by7k7TtYBggNpBgk", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"313b96b3-3262-418a-a467-1cddfdccd650", "ID_FS_UUID_ENC"=>"313b96b3-3262-418a-a467-1cddfdccd650", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14053", "nomdmonddf"=>"1",
Jul 29 04:09:43 node-4 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.574661 #13099] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.574748 #13099] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.574790 #13099] DEBUG -- : Device dm-3 seems to be appropriate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.574836 #13099] DEBUG -- : Getting udev properties for device: dm-4
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.578333 #13099] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-YxOyPPRkeniAbe8791IAefUBCvUaHEPnZbezqiY9JtUflLOGSui3sFPfuR04h54z /dev/disk/by-uuid/2412558c-77ba-4a40-8577-74ac4cd89780 /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-YxOyPPRkeniAbe8791IAefUBCvUaHEPnZbezqiY9JtUflLOGSui3sFPfuR04h54z", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2412558c-77ba-4a40-8577-74ac4cd89780", "ID_FS_UUID_ENC"=>"2412558c-77ba-4a40-8577-74ac4cd89780", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15054", "nomdmonddf"=>"1", "nom
Jul 29 04:09:43 node-4 nailgun-agent: dmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.578408 #13099] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.578493 #13099] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.578532 #13099] DEBUG -- : Device dm-4 seems to be appropriate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.578577 #13099] DEBUG -- : Getting udev properties for device: dm-5
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.582214 #13099] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-YxOyPPRkeniAbe8791IAefUBCvUaHEPncmnOUN7aZELjqW99YbXdRil4hJqrNbxV /dev/disk/by-uuid/90e0175a-988c-43fd-b3f4-a521d46a8805 /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-YxOyPPRkeniAbe8791IAefUBCvUaHEPncmnOUN7aZELjqW99YbXdRil4hJqrNbxV", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"90e0175a-988c-43fd-b3f4-a521d46a8805", "ID_FS_UUID_ENC"=>"90e0175a-988c-43fd-b3f4-a521d46a8805", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15397", "nomdmonddf"=>"1", "nomdmonisw
Jul 29 04:09:43 node-4 nailgun-agent: "=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.582289 #13099] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.582378 #13099] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.582416 #13099] DEBUG -- : Device dm-5 seems to be appropriate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.582463 #13099] DEBUG -- : Getting udev properties for device: ram0
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.585554 #13099] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62506", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.585627 #13099] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.585741 #13099] DEBUG -- : Device ram0 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.585791 #13099] DEBUG -- : Getting udev properties for device: ram1
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.588646 #13099] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62876", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.588771 #13099] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.588860 #13099] DEBUG -- : Device ram1 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.588909 #13099] DEBUG -- : Getting udev properties for device: ram2
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.591878 #13099] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64953", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.591930 #13099] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.592083 #13099] DEBUG -- : Device ram2 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.592125 #13099] DEBUG -- : Getting udev properties for device: ram3
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.595149 #13099] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65033", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.595204 #13099] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.595268 #13099] DEBUG -- : Device ram3 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.595346 #13099] DEBUG -- : Getting udev properties for device: ram4
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.598262 #13099] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65106", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.598314 #13099] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.598380 #13099] DEBUG -- : Device ram4 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.598421 #13099] DEBUG -- : Getting udev properties for device: ram5
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.602419 #13099] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65188", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.602474 #13099] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.602541 #13099] DEBUG -- : Device ram5 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.602583 #13099] DEBUG -- : Getting udev properties for device: ram6
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.606681 #13099] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65267", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.606733 #13099] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.606800 #13099] DEBUG -- : Device ram6 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.606840 #13099] DEBUG -- : Getting udev properties for device: ram7
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.609527 #13099] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65327", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.609604 #13099] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.609703 #13099] DEBUG -- : Device ram7 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.609760 #13099] DEBUG -- : Getting udev properties for device: ram8
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.612757 #13099] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65398", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.612832 #13099] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.612925 #13099] DEBUG -- : Device ram8 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.612980 #13099] DEBUG -- : Getting udev properties for device: ram9
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.615901 #13099] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65466", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.615972 #13099] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.616082 #13099] DEBUG -- : Device ram9 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.616137 #13099] DEBUG -- : Getting udev properties for device: loop0
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.619310 #13099] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59190", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.619381 #13099] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.619468 #13099] DEBUG -- : Device loop0 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.619522 #13099] DEBUG -- : Getting udev properties for device: loop1
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.622636 #13099] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59503", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.622709 #13099] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.622801 #13099] DEBUG -- : Device loop1 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.622855 #13099] DEBUG -- : Getting udev properties for device: loop2
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.626071 #13099] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60197", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.626144 #13099] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.626245 #13099] DEBUG -- : Device loop2 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.626345 #13099] DEBUG -- : Getting udev properties for device: loop3
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.629441 #13099] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60532", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.629518 #13099] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.629593 #13099] DEBUG -- : Device loop3 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.629629 #13099] DEBUG -- : Getting udev properties for device: loop4
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.632563 #13099] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60719", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.632613 #13099] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.632671 #13099] DEBUG -- : Device loop4 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.632708 #13099] DEBUG -- : Getting udev properties for device: loop5
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.635807 #13099] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61158", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.635881 #13099] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.636021 #13099] DEBUG -- : Device loop5 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.636058 #13099] DEBUG -- : Getting udev properties for device: loop6
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.638845 #13099] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61629", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.638894 #13099] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.638957 #13099] DEBUG -- : Device loop6 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.638995 #13099] DEBUG -- : Getting udev properties for device: loop7
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.642180 #13099] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62136", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.642230 #13099] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.642304 #13099] DEBUG -- : Device loop7 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.642341 #13099] DEBUG -- : Getting udev properties for device: ram10
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.644987 #13099] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64371", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.645035 #13099] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.645104 #13099] DEBUG -- : Device ram10 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.645142 #13099] DEBUG -- : Getting udev properties for device: ram11
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.648220 #13099] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64491", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.648281 #13099] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.648341 #13099] DEBUG -- : Device ram11 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.648375 #13099] DEBUG -- : Getting udev properties for device: ram12
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.651413 #13099] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64577", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.651458 #13099] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.651517 #13099] DEBUG -- : Device ram12 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.651552 #13099] DEBUG -- : Getting udev properties for device: ram13
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.654447 #13099] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64674", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.654492 #13099] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.654557 #13099] DEBUG -- : Device ram13 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.654592 #13099] DEBUG -- : Getting udev properties for device: ram14
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.657415 #13099] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64769", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.669392 #13099] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.670143 #13099] DEBUG -- : Device ram14 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.670183 #13099] DEBUG -- : Getting udev properties for device: ram15
Jul 29 04:09:43 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674316 #13099] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64871", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674353 #13099] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674398 #13099] DEBUG -- : Device ram15 removable parameter: "0"
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674446 #13099] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674468 #13099] DEBUG -- : Block device seems to be physical data storage: sda
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674524 #13099] DEBUG -- : Found block device: dm-0
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674545 #13099] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674563 #13099] DEBUG -- : Found block device: dm-1
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674577 #13099] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674588 #13099] DEBUG -- : Found block device: dm-2
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674604 #13099] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674619 #13099] DEBUG -- : Found block device: dm-3
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674633 #13099] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674642 #13099] DEBUG -- : Found block device: dm-4
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674654 #13099] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674665 #13099] DEBUG -- : Found block device: dm-5
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674677 #13099] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674687 #13099] DEBUG -- : Found block device: ram0
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674698 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674709 #13099] DEBUG -- : Found block device: ram1
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674724 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674735 #13099] DEBUG -- : Found block device: ram2
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674749 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674760 #13099] DEBUG -- : Found block device: ram3
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674774 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674786 #13099] DEBUG -- : Found block device: ram4
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674799 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674811 #13099] DEBUG -- : Found block device: ram5
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674826 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674839 #13099] DEBUG -- : Found block device: ram6
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674852 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674865 #13099] DEBUG -- : Found block device: ram7
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674881 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674897 #13099] DEBUG -- : Found block device: ram8
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674911 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674924 #13099] DEBUG -- : Found block device: ram9
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674938 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674949 #13099] DEBUG -- : Found block device: loop0
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674964 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674977 #13099] DEBUG -- : Found block device: loop1
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.674990 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675002 #13099] DEBUG -- : Found block device: loop2
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675015 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675025 #13099] DEBUG -- : Found block device: loop3
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675037 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675047 #13099] DEBUG -- : Found block device: loop4
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675061 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675072 #13099] DEBUG -- : Found block device: loop5
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675082 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675091 #13099] DEBUG -- : Found block device: loop6
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675103 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675113 #13099] DEBUG -- : Found block device: loop7
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675124 #13099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675138 #13099] DEBUG -- : Found block device: ram10
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675157 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675169 #13099] DEBUG -- : Found block device: ram11
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675182 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675192 #13099] DEBUG -- : Found block device: ram12
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675202 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675212 #13099] DEBUG -- : Found block device: ram13
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675224 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675235 #13099] DEBUG -- : Found block device: ram14
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675247 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675260 #13099] DEBUG -- : Found block device: ram15
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675276 #13099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.675312 #13099] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 29 04:09:43 node-4 nailgun-agent: D, [2016-07-29T04:09:43.890670 #13099] DEBUG -- : Response: status: 200 body: {"id": 4}
Jul 29 04:09:43 node-4 nailgun-agent: I, [2016-07-29T04:09:43.891107 #13099]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 29 04:10:01 node-4 CRON[17386]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 04:10:06 node-4 puppet-user[14890]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 29 04:10:06 node-4 puppet-user[14890]: Finished catalog run in 35.11 seconds
Jul 29 04:10:08 node-4 puppet-user[17658]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 29 04:10:08 node-4 puppet-user[17658]: Compiled catalog for node-4.domain.tld in environment production in 0.57 seconds
Jul 29 04:10:09 node-4 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 29 04:10:09 node-4 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 29 04:10:09 node-4 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 29 04:10:09 node-4 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 29 04:10:09 node-4 puppet-user[17658]: Finished catalog run in 0.09 seconds
Jul 29 04:10:10 node-4 puppet-user[18124]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 29 04:10:11 node-4 puppet-user[18124]: Compiled catalog for node-4.domain.tld in environment production in 0.88 seconds
Jul 29 04:10:12 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 29 04:10:12 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 29 04:10:12 node-4 crontab[18569]: (root) LIST (root)
Jul 29 04:10:12 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 29 04:10:12 node-4 crontab[18570]: (root) REPLACE (root)
Jul 29 04:10:14 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:15 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 29 04:10:16 node-4 puppet-user[18124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 29 04:10:16 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8369" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 29 04:10:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:17 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 29 04:10:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:44 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:44 node-4 multipathd: uevent trigger error
<27>Jul 29 04:10:44 node-4 multipathd: uevent trigger error
<27>Jul 29 04:11:44 node-4 ntpdate[30170]: no servers can be used, exiting
<27>Jul 29 04:11:44 node-4 ntpdate[30447]: no servers can be used, exiting
<27>Jul 29 04:11:44 node-4 ntpdate[30608]: no servers can be used, exiting
<27>Jul 29 04:12:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:12:40 node-4 multipathd: uevent trigger error
<43>Jul 29 04:12:57 node-4 apache2_error [Fri Jul 29 04:12:53.054825 2016] [mpm_event:notice] [pid 7428:tid 140273812125568] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:12:57 node-4 apache2_error [Fri Jul 29 04:12:53.054910 2016] [core:notice] [pid 7428:tid 140273812125568] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 04:12:57 node-4 apache2_error [Fri Jul 29 04:12:56.037685 2016] [mpm_event:notice] [pid 7428:tid 140273812125568] AH00491: caught SIGTERM, shutting down
<43>Jul 29 04:12:57 node-4 apache2_error [Fri Jul 29 04:12:57.140748 2016] [mpm_worker:notice] [pid 7788:tid 140607830755200] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:12:57 node-4 apache2_error [Fri Jul 29 04:12:57.140806 2016] [core:notice] [pid 7788:tid 140607830755200] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:13:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:01 node-4 multipathd: uevent trigger error
<43>Jul 29 04:13:37 node-4 apache2_error [Fri Jul 29 04:13:34.547582 2016] [mpm_worker:notice] [pid 7788:tid 140607830755200] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:13:37 node-4 apache2_error [Fri Jul 29 04:13:34.551741 2016] [mpm_worker:warn] [pid 7788:tid 140607830755200] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:13:37 node-4 apache2_error [Fri Jul 29 04:13:34.552173 2016] [mpm_worker:notice] [pid 7788:tid 140607830755200] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:13:37 node-4 apache2_error [Fri Jul 29 04:13:34.552180 2016] [core:notice] [pid 7788:tid 140607830755200] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:13:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:13:56 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:33 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 29 04:14:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:37 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:14:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:01 node-4 haproxy[25494]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:01 node-4 haproxy[25494]: proxy odl-jetty has no server available!
<27>Jul 29 04:15:01 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:03 node-4 haproxy[25494]: 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>Jul 29 04:15:03 node-4 haproxy[25494]: proxy odl-neutron-endpoint has no server available!
<129>Jul 29 04:15:03 node-4 haproxy[26694]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:06 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:06 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:06 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:06 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:06 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:06 node-4 haproxy[26706]: 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>Jul 29 04:15:06 node-4 haproxy[26706]: proxy odl-jetty has no server available!
<27>Jul 29 04:15:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:09 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:11 node-4 haproxy[26706]: 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>Jul 29 04:15:11 node-4 haproxy[26706]: proxy odl-neutron-endpoint has no server available!
<129>Jul 29 04:15:12 node-4 haproxy[28964]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:13 node-4 haproxy[28978]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:15 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:15 node-4 haproxy[28978]: 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>Jul 29 04:15:15 node-4 haproxy[28978]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:17 node-4 haproxy[30162]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:18 node-4 haproxy[30176]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:18 node-4 haproxy[30176]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:21 node-4 haproxy[30176]: 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>Jul 29 04:15:21 node-4 haproxy[30176]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:22 node-4 haproxy[31532]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:23 node-4 haproxy[31546]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:23 node-4 haproxy[31546]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:23 node-4 haproxy[31546]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:24 node-4 haproxy[31546]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:25 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:25 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:25 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:25 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:25 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:26 node-4 haproxy[31546]: 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>Jul 29 04:15:26 node-4 haproxy[31546]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:27 node-4 haproxy[32739]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:28 node-4 haproxy[32751]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:28 node-4 haproxy[32751]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:28 node-4 haproxy[32751]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:29 node-4 haproxy[32751]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:29 node-4 haproxy[32751]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:31 node-4 haproxy[32751]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:31 node-4 haproxy[32751]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:31 node-4 haproxy[32751]: proxy aodh has no server available!
<129>Jul 29 04:15:31 node-4 haproxy[32751]: 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>Jul 29 04:15:31 node-4 haproxy[32751]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:33 node-4 haproxy[1682]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:33 node-4 haproxy[1682]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:33 node-4 haproxy[1682]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:34 node-4 haproxy[1691]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:34 node-4 haproxy[1691]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:34 node-4 haproxy[1691]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:34 node-4 haproxy[1691]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:36 node-4 haproxy[1691]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:36 node-4 haproxy[1691]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:36 node-4 haproxy[1691]: proxy aodh has no server available!
<129>Jul 29 04:15:36 node-4 haproxy[1691]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:37 node-4 haproxy[1691]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:37 node-4 haproxy[1691]: proxy ceilometer has no server available!
<129>Jul 29 04:15:37 node-4 haproxy[1691]: 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>Jul 29 04:15:37 node-4 haproxy[1691]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:38 node-4 haproxy[2869]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:38 node-4 haproxy[2869]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:39 node-4 haproxy[2878]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:39 node-4 haproxy[2878]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:39 node-4 haproxy[2878]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:40 node-4 haproxy[2878]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:40 node-4 haproxy[2878]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:41 node-4 haproxy[2878]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:42 node-4 haproxy[2878]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:42 node-4 haproxy[2878]: proxy aodh has no server available!
<129>Jul 29 04:15:42 node-4 haproxy[2878]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:42 node-4 haproxy[2878]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:42 node-4 haproxy[2878]: proxy ceilometer has no server available!
<129>Jul 29 04:15:42 node-4 haproxy[2878]: 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>Jul 29 04:15:42 node-4 haproxy[2878]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:44 node-4 haproxy[4096]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:44 node-4 haproxy[4096]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:44 node-4 haproxy[4096]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:44 node-4 haproxy[4096]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:45 node-4 haproxy[4096]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:45 node-4 haproxy[4096]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:45 node-4 haproxy[4096]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:45 node-4 haproxy[4096]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:46 node-4 haproxy[4096]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:47 node-4 haproxy[4096]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:47 node-4 haproxy[4096]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:47 node-4 haproxy[4096]: proxy aodh has no server available!
<129>Jul 29 04:15:47 node-4 haproxy[4096]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:47 node-4 haproxy[4096]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:47 node-4 haproxy[4096]: proxy ceilometer has no server available!
<129>Jul 29 04:15:47 node-4 haproxy[4096]: 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>Jul 29 04:15:47 node-4 haproxy[4096]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:50 node-4 haproxy[5371]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:50 node-4 haproxy[5371]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:50 node-4 haproxy[5371]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:50 node-4 haproxy[5371]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:50 node-4 haproxy[5371]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:50 node-4 haproxy[5371]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:51 node-4 haproxy[5371]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:51 node-4 haproxy[5371]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:51 node-4 haproxy[5371]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:51 node-4 haproxy[5371]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:51 node-4 haproxy[5371]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:51 node-4 haproxy[5371]: 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.
<129>Jul 29 04:15:52 node-4 haproxy[5371]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:52 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:52 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:52 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:52 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:53 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:53 node-4 haproxy[5371]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:53 node-4 haproxy[5371]: proxy glance-registry has no server available!
<129>Jul 29 04:15:53 node-4 haproxy[5371]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:53 node-4 haproxy[5371]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:53 node-4 haproxy[5371]: proxy aodh has no server available!
<129>Jul 29 04:15:53 node-4 haproxy[5371]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:53 node-4 haproxy[5371]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:53 node-4 haproxy[5371]: proxy ceilometer has no server available!
<129>Jul 29 04:15:53 node-4 haproxy[5371]: 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>Jul 29 04:15:53 node-4 haproxy[5371]: proxy odl-jetty has no server available!
<129>Jul 29 04:15:56 node-4 haproxy[6646]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:56 node-4 haproxy[6646]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:56 node-4 haproxy[6646]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:56 node-4 haproxy[6646]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:56 node-4 haproxy[6646]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:56 node-4 haproxy[6646]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:56 node-4 haproxy[6646]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:57 node-4 haproxy[6646]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:15:58 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:58 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:58 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:58 node-4 multipathd: uevent trigger error
<27>Jul 29 04:15:58 node-4 multipathd: uevent trigger error
<129>Jul 29 04:15:58 node-4 haproxy[6646]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:59 node-4 haproxy[6646]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:59 node-4 haproxy[6646]: proxy glance-registry has no server available!
<129>Jul 29 04:15:59 node-4 haproxy[6646]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:59 node-4 haproxy[6646]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:59 node-4 haproxy[6646]: proxy aodh has no server available!
<129>Jul 29 04:15:59 node-4 haproxy[6646]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:59 node-4 haproxy[6646]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:59 node-4 haproxy[6646]: proxy ceilometer has no server available!
<129>Jul 29 04:15:59 node-4 haproxy[6646]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:59 node-4 haproxy[6646]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:59 node-4 haproxy[6646]: proxy nova-novncproxy has no server available!
<129>Jul 29 04:15:59 node-4 haproxy[6646]: 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>Jul 29 04:15:59 node-4 haproxy[6646]: proxy odl-jetty has no server available!
<129>Jul 29 04:16:01 node-4 haproxy[7837]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:01 node-4 haproxy[7837]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:01 node-4 haproxy[7837]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:01 node-4 haproxy[7837]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:01 node-4 haproxy[7837]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:01 node-4 haproxy[7837]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-4 haproxy[7853]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-4 haproxy[7853]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-4 haproxy[7853]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-4 haproxy[7853]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-4 haproxy[7853]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-4 haproxy[7853]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-4 haproxy[7853]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:03 node-4 haproxy[7853]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:03 node-4 haproxy[7853]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:03 node-4 haproxy[7853]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:16:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:04 node-4 multipathd: uevent trigger error
<129>Jul 29 04:16:04 node-4 haproxy[7853]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:04 node-4 haproxy[7853]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:04 node-4 haproxy[7853]: proxy glance-registry has no server available!
<129>Jul 29 04:16:04 node-4 haproxy[7853]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:04 node-4 haproxy[7853]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:04 node-4 haproxy[7853]: proxy aodh has no server available!
<27>Jul 29 04:16:04 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 29 04:16:04 node-4 haproxy[7853]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:04 node-4 haproxy[7853]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:04 node-4 haproxy[7853]: proxy ceilometer has no server available!
<129>Jul 29 04:16:04 node-4 haproxy[7853]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:05 node-4 haproxy[7853]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:05 node-4 haproxy[7853]: proxy nova-novncproxy has no server available!
<129>Jul 29 04:16:05 node-4 haproxy[7853]: 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>Jul 29 04:16:05 node-4 haproxy[7853]: proxy odl-jetty has no server available!
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:07 node-4 haproxy[9163]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-4 haproxy[9163]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:09 node-4 haproxy[9163]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:16:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-4 multipathd: uevent trigger error
<129>Jul 29 04:16:09 node-4 haproxy[9163]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:09 node-4 haproxy[9163]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:09 node-4 haproxy[9163]: proxy glance-registry has no server available!
<129>Jul 29 04:16:10 node-4 haproxy[9163]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:10 node-4 haproxy[9163]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:10 node-4 haproxy[9163]: proxy aodh has no server available!
<129>Jul 29 04:16:10 node-4 haproxy[9163]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:10 node-4 haproxy[9163]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:10 node-4 haproxy[9163]: proxy ceilometer has no server available!
<129>Jul 29 04:16:10 node-4 haproxy[9163]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:10 node-4 haproxy[9163]: 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>Jul 29 04:16:10 node-4 haproxy[9163]: proxy nova-novncproxy has no server available!
<129>Jul 29 04:16:10 node-4 haproxy[9163]: 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>Jul 29 04:16:10 node-4 haproxy[9163]: proxy odl-jetty has no server available!
<27>Jul 29 04:16:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:16 node-4 multipathd: uevent trigger error
<129>Jul 29 04:16:16 node-4 haproxy[9163]: 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>Jul 29 04:16:16 node-4 haproxy[9163]: proxy odl-neutron-endpoint has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server keystone-1/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:17 node-4 haproxy[9163]: proxy keystone-1 has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server keystone-2/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:17 node-4 haproxy[9163]: proxy keystone-2 has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server nova-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:17 node-4 haproxy[9163]: proxy nova-api has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:17 node-4 haproxy[9163]: proxy nova-metadata-api has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:17 node-4 haproxy[9163]: proxy cinder-api has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server glance-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:17 node-4 haproxy[9163]: proxy glance-api has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server glance-glare/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:17 node-4 haproxy[9163]: proxy glance-glare has no server available!
<129>Jul 29 04:16:17 node-4 haproxy[9163]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:17 node-4 haproxy[9163]: 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>Jul 29 04:16:17 node-4 haproxy[9163]: proxy neutron has no server available!
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:18 node-4 haproxy[9163]: proxy mysqld has no server available!
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server object-storage/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:18 node-4 haproxy[9163]: proxy object-storage has no server available!
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server heat-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:18 node-4 haproxy[9163]: proxy heat-api has no server available!
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:18 node-4 haproxy[9163]: proxy heat-api-cfn has no server available!
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:18 node-4 haproxy[9163]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:18 node-4 haproxy[9163]: proxy heat-api-cloudwatch has no server available!
<27>Jul 29 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 29 04:16:25 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 29 04:17:02 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 04:17:04 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 04:17:04 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 04:17:04 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 29 04:17:41 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 04:18:07 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 29 04:18:09 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 29 04:19:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:19:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:19:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:19:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:19:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-4 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-4 multipathd: uevent trigger error
<43>Jul 29 04:24:28 node-4 apache2_error [Fri Jul 29 04:24:24.737213 2016] [mpm_worker:notice] [pid 7788:tid 140607830755200] AH00295: caught SIGTERM, shutting down
<43>Jul 29 04:24:28 node-4 apache2_error [Fri Jul 29 04:24:25.488315 2016] [mpm_worker:notice] [pid 11376:tid 140069632141184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:24:28 node-4 apache2_error [Fri Jul 29 04:24:25.488342 2016] [core:notice] [pid 11376:tid 140069632141184] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 29 04:24:29 node-4 epmd: epmd: node name already occupied rabbitmq-cli-61
<11>Jul 29 04:24:32 node-4 epmd: epmd: node name already occupied rabbitmq-cli-61
<43>Jul 29 04:24:58 node-4 apache2_error [Fri Jul 29 04:24:57.399187 2016] [mpm_worker:notice] [pid 11376:tid 140069632141184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:24:58 node-4 apache2_error [Fri Jul 29 04:24:57.416333 2016] [mpm_worker:warn] [pid 11376:tid 140069632141184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:24:58 node-4 apache2_error [Fri Jul 29 04:24:57.421143 2016] [mpm_worker:notice] [pid 11376:tid 140069632141184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:24:58 node-4 apache2_error [Fri Jul 29 04:24:57.421169 2016] [core:notice] [pid 11376:tid 140069632141184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:25:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:25:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:25:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:25:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:25:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:25:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:25:03 node-4 multipathd: uevent trigger error
<11>Jul 29 04:25:09 node-4 epmd: epmd: node name already occupied rabbitmq-cli-61
<11>Jul 29 04:25:17 node-4 epmd: epmd: node name already occupied rabbitmq-cli-61
<27>Jul 29 04:26:02 node-4 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-4 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-4 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-4 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-4 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-4 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-4 multipathd: uevent trigger error
<11>Jul 29 04:26:25 node-4 epmd: epmd: node name already occupied rabbitmq-cli-61
<27>Jul 29 04:27:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:27:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:27:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:27:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:27:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:27:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-4 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-4 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-4 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-4 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-4 multipathd: uevent trigger error
<11>Jul 29 04:33:10 node-4 epmd: epmd: node name already occupied rabbitmq-cli-61
<27>Jul 29 04:34:29 node-4 multipathd: uevent trigger error
<27>Jul 29 04:34:29 node-4 multipathd: uevent trigger error
<27>Jul 29 04:34:29 node-4 multipathd: uevent trigger error
<27>Jul 29 04:34:29 node-4 multipathd: uevent trigger error
<27>Jul 29 04:34:29 node-4 multipathd: uevent trigger error
<27>Jul 29 04:34:29 node-4 multipathd: uevent trigger error
<27>Jul 29 04:34:29 node-4 multipathd: uevent trigger error
<27>Jul 29 04:35:38 node-4 multipathd: uevent trigger error
<27>Jul 29 04:35:38 node-4 multipathd: uevent trigger error
<27>Jul 29 04:35:38 node-4 multipathd: uevent trigger error
<27>Jul 29 04:35:38 node-4 multipathd: uevent trigger error
<27>Jul 29 04:35:38 node-4 multipathd: uevent trigger error
<27>Jul 29 04:35:38 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:15 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:25 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:25 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:26 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:26 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:26 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:26 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:26 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:31 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:36 node-4 multipathd: uevent trigger error
<27>Jul 29 04:36:36 node-4 multipathd: uevent trigger error
<43>Jul 29 04:37:28 node-4 apache2_error [Fri Jul 29 04:37:23.151044 2016] [mpm_worker:notice] [pid 11376:tid 140069632141184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:37:28 node-4 apache2_error [Fri Jul 29 04:37:23.532862 2016] [mpm_worker:warn] [pid 11376:tid 140069632141184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:37:28 node-4 apache2_error [Fri Jul 29 04:37:23.536759 2016] [mpm_worker:notice] [pid 11376:tid 140069632141184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:37:28 node-4 apache2_error [Fri Jul 29 04:37:23.536777 2016] [core:notice] [pid 11376:tid 140069632141184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:38:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:04 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:04 node-4 multipathd: uevent trigger error
<43>Jul 29 04:38:08 node-4 apache2_error [Fri Jul 29 04:38:00.360289 2016] [mpm_worker:notice] [pid 11376:tid 140069632141184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:38:08 node-4 apache2_error [Fri Jul 29 04:38:00.746475 2016] [mpm_worker:warn] [pid 11376:tid 140069632141184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:38:08 node-4 apache2_error [Fri Jul 29 04:38:00.755919 2016] [mpm_worker:notice] [pid 11376:tid 140069632141184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:38:08 node-4 apache2_error [Fri Jul 29 04:38:00.755952 2016] [core:notice] [pid 11376:tid 140069632141184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:38:21 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:21 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:21 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-4 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 29 04:39:23 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:23 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:23 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:23 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:23 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:27 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:27 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:27 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:27 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:39:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:16 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:16 node-4 multipathd: uevent trigger error
<11>Jul 29 04:41:25 node-4 liberasurecode[76142]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-4 liberasurecode[76142]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-4 liberasurecode[76142]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-4 liberasurecode[76142]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-4 liberasurecode[76169]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-4 liberasurecode[76169]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-4 liberasurecode[76169]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-4 liberasurecode[76169]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-4 liberasurecode[76606]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-4 liberasurecode[76606]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-4 liberasurecode[76606]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-4 liberasurecode[76606]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78894]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78894]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78942]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78942]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78942]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[78942]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79029]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79029]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79029]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79029]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79086]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79086]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79086]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79086]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79100]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79100]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79100]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79100]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79112]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79112]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79112]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-4 liberasurecode[79112]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:34 node-4 liberasurecode[79160]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:34 node-4 liberasurecode[79160]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:34 node-4 liberasurecode[79160]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:34 node-4 liberasurecode[79160]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 04:41:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:40 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:45 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:45 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:45 node-4 multipathd: uevent trigger error
<27>Jul 29 04:41:45 node-4 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-4 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-4 multipathd: uevent trigger error
<11>Jul 29 04:45:01 node-4 liberasurecode[109446]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-4 liberasurecode[109446]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-4 liberasurecode[109446]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-4 liberasurecode[109446]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 04:45:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:09 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:14 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:28 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:28 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:28 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:28 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:28 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:28 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:34 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:44 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:48 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:53 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:53 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:53 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:53 node-4 multipathd: uevent trigger error
<27>Jul 29 04:45:53 node-4 multipathd: uevent trigger error
