Oct  4 22:32:21 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8402" x-info="http://www.rsyslog.com"] start
Oct  4 22:32:21 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  4 22:32:21 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct  4 22:32:21 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct  4 22:32:21 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  4 22:32:21 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  4 22:32:21 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  4 22:32:21 node-1 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Oct  4 22:32:21 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=ac438202-8ef3-48c5-aa27-c9eceb43ff95 nomdmonddf nomdmonisw
Oct  4 22:32:21 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct  4 22:32:21 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct  4 22:32:21 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct  4 22:32:21 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct  4 22:32:21 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  4 22:32:21 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  4 22:32:21 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  4 22:32:21 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct  4 22:32:21 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  4 22:32:21 node-1 kernel: [    0.000000] No AGP bridge found
Oct  4 22:32:21 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  4 22:32:21 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct  4 22:32:21 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  4 22:32:21 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct  4 22:32:21 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  4 22:32:21 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  4 22:32:21 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  4 22:32:21 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  4 22:32:21 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  4 22:32:21 node-1 kernel: [    0.000000]   2 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000]   3 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000]   4 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000]   5 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000]   6 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000]   7 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000]   8 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000]   9 disabled
Oct  4 22:32:21 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  4 22:32:21 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  4 22:32:21 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  4 22:32:21 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  4 22:32:21 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  4 22:32:21 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  4 22:32:21 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  4 22:32:21 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  4 22:32:21 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  4 22:32:21 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  4 22:32:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  4 22:32:21 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  4 22:32:21 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  4 22:32:21 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  4 22:32:21 node-1 kernel: [    0.000000] Zone ranges:
Oct  4 22:32:21 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] Movable zone start for each node
Oct  4 22:32:21 node-1 kernel: [    0.000000] Early memory node ranges
Oct  4 22:32:21 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct  4 22:32:21 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  4 22:32:21 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  4 22:32:21 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  4 22:32:21 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct  4 22:32:21 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct  4 22:32:21 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  4 22:32:21 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  4 22:32:21 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  4 22:32:21 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  4 22:32:21 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  4 22:32:21 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  4 22:32:21 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  4 22:32:21 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  4 22:32:21 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  4 22:32:21 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  4 22:32:21 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  4 22:32:21 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  4 22:32:21 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  4 22:32:21 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  4 22:32:21 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  4 22:32:21 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  4 22:32:21 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  4 22:32:21 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct  4 22:32:21 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct  4 22:32:21 node-1 kernel: [    0.000000] Policy zone: Normal
Oct  4 22:32:21 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=ac438202-8ef3-48c5-aa27-c9eceb43ff95 nomdmonddf nomdmonisw
Oct  4 22:32:21 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  4 22:32:21 node-1 kernel: [    0.000000] Checking aperture...
Oct  4 22:32:21 node-1 kernel: [    0.000000] No AGP bridge found
Oct  4 22:32:21 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  4 22:32:21 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  4 22:32:21 node-1 kernel: [    0.000000] Memory: 32653452K/33280636K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct  4 22:32:21 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  4 22:32:21 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  4 22:32:21 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  4 22:32:21 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  4 22:32:21 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  4 22:32:21 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  4 22:32:21 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  4 22:32:21 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  4 22:32:21 node-1 kernel: [    0.000000] console [tty0] enabled
Oct  4 22:32:21 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  4 22:32:21 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  4 22:32:21 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  4 22:32:21 node-1 kernel: [    0.000000] hpet clockevent registered
Oct  4 22:32:21 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  4 22:32:21 node-1 kernel: [    0.004000] tsc: Detected 3491.848 MHz processor
Oct  4 22:32:21 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.69 BogoMIPS (lpj=13967392)
Oct  4 22:32:21 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  4 22:32:21 node-1 kernel: [    0.000042] Security Framework initialized
Oct  4 22:32:21 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Oct  4 22:32:21 node-1 kernel: [    0.000061] Yama: becoming mindful.
Oct  4 22:32:21 node-1 kernel: [    0.001452] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.006398] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.008329] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.008356] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.008650] Initializing cgroup subsys memory
Oct  4 22:32:21 node-1 kernel: [    0.008659] Initializing cgroup subsys devices
Oct  4 22:32:21 node-1 kernel: [    0.008661] Initializing cgroup subsys freezer
Oct  4 22:32:21 node-1 kernel: [    0.008662] Initializing cgroup subsys blkio
Oct  4 22:32:21 node-1 kernel: [    0.008664] Initializing cgroup subsys perf_event
Oct  4 22:32:21 node-1 kernel: [    0.008666] Initializing cgroup subsys hugetlb
Oct  4 22:32:21 node-1 kernel: [    0.008686] CPU: Physical Processor ID: 0
Oct  4 22:32:21 node-1 kernel: [    0.008687] CPU: Processor Core ID: 0
Oct  4 22:32:21 node-1 kernel: [    0.008691] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  4 22:32:21 node-1 kernel: [    0.008691] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  4 22:32:21 node-1 kernel: [    0.009385] mce: CPU supports 22 MCE banks
Oct  4 22:32:21 node-1 kernel: [    0.009413] CPU0: Thermal monitoring enabled (TM1)
Oct  4 22:32:21 node-1 kernel: [    0.009434] process: using mwait in idle threads
Oct  4 22:32:21 node-1 kernel: [    0.009437] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  4 22:32:21 node-1 kernel: [    0.009437] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  4 22:32:21 node-1 kernel: [    0.009437] tlb_flushall_shift: 6
Oct  4 22:32:21 node-1 kernel: [    0.009525] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  4 22:32:21 node-1 kernel: [    0.010250] ACPI: Core revision 20131115
Oct  4 22:32:21 node-1 kernel: [    0.022915] ACPI: All ACPI Tables successfully acquired
Oct  4 22:32:21 node-1 kernel: [    0.023077] ftrace: allocating 28614 entries in 112 pages
Oct  4 22:32:21 node-1 kernel: [    0.031795] dmar: Host address width 46
Oct  4 22:32:21 node-1 kernel: [    0.031797] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  4 22:32:21 node-1 kernel: [    0.031803] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  4 22:32:21 node-1 kernel: [    0.031805] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  4 22:32:21 node-1 kernel: [    0.031809] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  4 22:32:21 node-1 kernel: [    0.031810] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  4 22:32:21 node-1 kernel: [    0.031812] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  4 22:32:21 node-1 kernel: [    0.031813] dmar: ATSR flags: 0x0
Oct  4 22:32:21 node-1 kernel: [    0.031814] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  4 22:32:21 node-1 kernel: [    0.031815] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  4 22:32:21 node-1 kernel: [    0.031930] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  4 22:32:21 node-1 kernel: [    0.031932] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  4 22:32:21 node-1 kernel: [    0.031933] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  4 22:32:21 node-1 kernel: [    0.031934] HPET id 0 under DRHD base 0xc7ffc000
Oct  4 22:32:21 node-1 kernel: [    0.031935] Your BIOS is broken and requested that x2apic be disabled.
Oct  4 22:32:21 node-1 kernel: [    0.031935] This will slightly decrease performance.
Oct  4 22:32:21 node-1 kernel: [    0.031935] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  4 22:32:21 node-1 kernel: [    0.032365] Enabled IRQ remapping in xapic mode
Oct  4 22:32:21 node-1 kernel: [    0.032366] x2apic not enabled, IRQ remapping is in xapic mode
Oct  4 22:32:21 node-1 kernel: [    0.032370] Switched APIC routing to physical flat.
Oct  4 22:32:21 node-1 kernel: [    0.032944] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  4 22:32:21 node-1 kernel: [    0.072593] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  4 22:32:21 node-1 kernel: [    0.072599] TSC deadline timer enabled
Oct  4 22:32:21 node-1 kernel: [    0.072606] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  4 22:32:21 node-1 kernel: [    0.072612] ... version:                3
Oct  4 22:32:21 node-1 kernel: [    0.072613] ... bit width:              48
Oct  4 22:32:21 node-1 kernel: [    0.072614] ... generic registers:      4
Oct  4 22:32:21 node-1 kernel: [    0.072615] ... value mask:             0000ffffffffffff
Oct  4 22:32:21 node-1 kernel: [    0.072616] ... max period:             0000ffffffffffff
Oct  4 22:32:21 node-1 kernel: [    0.072617] ... fixed-purpose events:   3
Oct  4 22:32:21 node-1 kernel: [    0.072617] ... event mask:             000000070000000f
Oct  4 22:32:21 node-1 kernel: [    0.074005] x86: Booting SMP configuration:
Oct  4 22:32:21 node-1 kernel: [    0.088109] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  4 22:32:21 node-1 kernel: [    0.074007] .... node  #0, CPUs:        #1  #2  #3
Oct  4 22:32:21 node-1 kernel: [    0.116020] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  4 22:32:21 node-1 kernel: [    0.270169] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  4 22:32:21 node-1 kernel: [    0.325786] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  4 22:32:21 node-1 kernel: [    0.382851] x86: Booted up 2 nodes, 16 CPUs
Oct  4 22:32:21 node-1 kernel: [    0.382855] smpboot: Total of 16 processors activated (111751.57 BogoMIPS)
Oct  4 22:32:21 node-1 kernel: [    0.407294] devtmpfs: initialized
Oct  4 22:32:21 node-1 kernel: [    0.409830] EVM: security.selinux
Oct  4 22:32:21 node-1 kernel: [    0.409832] EVM: security.SMACK64
Oct  4 22:32:21 node-1 kernel: [    0.409833] EVM: security.ima
Oct  4 22:32:21 node-1 kernel: [    0.409833] EVM: security.capability
Oct  4 22:32:21 node-1 kernel: [    0.409884] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.410567] pinctrl core: initialized pinctrl subsystem
Oct  4 22:32:21 node-1 kernel: [    0.410632] regulator-dummy: no parameters
Oct  4 22:32:21 node-1 kernel: [    0.410664] RTC time: 22:31:45, date: 10/04/16
Oct  4 22:32:21 node-1 kernel: [    0.410699] NET: Registered protocol family 16
Oct  4 22:32:21 node-1 kernel: [    0.410785] cpuidle: using governor ladder
Oct  4 22:32:21 node-1 kernel: [    0.410786] cpuidle: using governor menu
Oct  4 22:32:21 node-1 kernel: [    0.410835] ACPI: bus type PCI registered
Oct  4 22:32:21 node-1 kernel: [    0.410837] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  4 22:32:21 node-1 kernel: [    0.410884] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  4 22:32:21 node-1 kernel: [    0.410887] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  4 22:32:21 node-1 kernel: [    0.424624] PCI: Using configuration type 1 for base access
Oct  4 22:32:21 node-1 kernel: [    0.425626] bio: create slab <bio-0> at 0
Oct  4 22:32:21 node-1 kernel: [    0.425903] ACPI: Added _OSI(Module Device)
Oct  4 22:32:21 node-1 kernel: [    0.425905] ACPI: Added _OSI(Processor Device)
Oct  4 22:32:21 node-1 kernel: [    0.425906] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  4 22:32:21 node-1 kernel: [    0.425907] ACPI: Added _OSI(Processor Aggregator Device)
Oct  4 22:32:21 node-1 kernel: [    0.438680] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  4 22:32:21 node-1 kernel: [    0.449137] ACPI: Interpreter enabled
Oct  4 22:32:21 node-1 kernel: [    0.449143] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  4 22:32:21 node-1 kernel: [    0.449147] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  4 22:32:21 node-1 kernel: [    0.449149] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  4 22:32:21 node-1 kernel: [    0.449156] ACPI: (supports S0 S4 S5)
Oct  4 22:32:21 node-1 kernel: [    0.449158] ACPI: Using IOAPIC for interrupt routing
Oct  4 22:32:21 node-1 kernel: [    0.449202] HEST: Table parsing has been initialized.
Oct  4 22:32:21 node-1 kernel: [    0.449205] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  4 22:32:21 node-1 kernel: [    0.449766] ACPI: No dock devices found.
Oct  4 22:32:21 node-1 kernel: [    0.461473] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  4 22:32:21 node-1 kernel: [    0.461477] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:21 node-1 kernel: [    0.461481] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  4 22:32:21 node-1 kernel: [    0.461509] PCI host bridge to bus 0000:ff
Oct  4 22:32:21 node-1 kernel: [    0.461511] pci_bus 0000:ff: root bus resource [bus ff]
Oct  4 22:32:21 node-1 kernel: [    0.461519] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461557] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.461588] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461624] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461654] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.461684] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.461715] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461744] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461775] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461804] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461831] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461857] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461886] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461912] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461939] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461966] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.461995] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462022] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462049] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.462077] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462103] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.462129] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462155] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462185] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.462219] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462250] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462280] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462311] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462341] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462372] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462403] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462434] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462465] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462496] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462526] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462557] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462589] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462617] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462645] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462676] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462708] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462744] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462777] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462809] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462839] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462870] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462899] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462928] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462958] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.462987] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463018] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463049] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463077] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463105] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463134] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463165] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463196] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463252] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  4 22:32:21 node-1 kernel: [    0.463255] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:21 node-1 kernel: [    0.463258] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  4 22:32:21 node-1 kernel: [    0.463275] PCI host bridge to bus 0000:7f
Oct  4 22:32:21 node-1 kernel: [    0.463277] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  4 22:32:21 node-1 kernel: [    0.463282] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463309] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.463337] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463367] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463388] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.463413] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.463438] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463468] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463492] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463516] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463541] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463565] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463590] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463613] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463636] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463662] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463683] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463706] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463729] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.463752] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463774] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.463796] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463818] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463844] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  4 22:32:21 node-1 kernel: [    0.463877] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463904] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463930] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463956] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.463982] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464007] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464033] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464060] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464085] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464111] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464137] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464163] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464192] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464217] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464243] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464273] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464298] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464324] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464352] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464379] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464403] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464429] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464456] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464482] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464507] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464533] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464562] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464587] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464610] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464633] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464658] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464687] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.464713] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.465958] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  4 22:32:21 node-1 kernel: [    0.465961] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:21 node-1 kernel: [    0.467094] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  4 22:32:21 node-1 kernel: [    0.467608] PCI host bridge to bus 0000:00
Oct  4 22:32:21 node-1 kernel: [    0.467611] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  4 22:32:21 node-1 kernel: [    0.467612] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  4 22:32:21 node-1 kernel: [    0.467614] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  4 22:32:21 node-1 kernel: [    0.467615] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  4 22:32:21 node-1 kernel: [    0.467616] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  4 22:32:21 node-1 kernel: [    0.467618] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  4 22:32:21 node-1 kernel: [    0.467619] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  4 22:32:21 node-1 kernel: [    0.467625] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  4 22:32:21 node-1 kernel: [    0.467707] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.467738] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.467780] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  4 22:32:21 node-1 kernel: [    0.467799] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.467828] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.467869] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  4 22:32:21 node-1 kernel: [    0.467887] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.467917] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.467957] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  4 22:32:21 node-1 kernel: [    0.467973] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.468042] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.468120] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.468195] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  4 22:32:21 node-1 kernel: [    0.468200] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  4 22:32:21 node-1 kernel: [    0.468285] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  4 22:32:21 node-1 kernel: [    0.468433] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  4 22:32:21 node-1 kernel: [    0.468450] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  4 22:32:21 node-1 kernel: [    0.468528] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.468583] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  4 22:32:21 node-1 kernel: [    0.468604] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.468659] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.468703] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  4 22:32:21 node-1 kernel: [    0.468730] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.468785] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.468828] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  4 22:32:21 node-1 kernel: [    0.468852] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  4 22:32:21 node-1 kernel: [    0.468870] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  4 22:32:21 node-1 kernel: [    0.468947] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.468997] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  4 22:32:21 node-1 kernel: [    0.469023] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  4 22:32:21 node-1 kernel: [    0.469270] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  4 22:32:21 node-1 kernel: [    0.469276] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  4 22:32:21 node-1 kernel: [    0.469282] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.469288] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.469295] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  4 22:32:21 node-1 kernel: [    0.469325] pci 0000:01:00.0: supports D1 D2
Oct  4 22:32:21 node-1 kernel: [    0.479467] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  4 22:32:21 node-1 kernel: [    0.479470] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  4 22:32:21 node-1 kernel: [    0.479471] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  4 22:32:21 node-1 kernel: [    0.479579] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.479612] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  4 22:32:21 node-1 kernel: [    0.491471] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  4 22:32:21 node-1 kernel: [    0.491477] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.491481] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:21 node-1 kernel: [    0.491566] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.491639] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.491734] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.491816] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  4 22:32:21 node-1 kernel: [    0.491823] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.491827] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:21 node-1 kernel: [    0.491911] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.492052] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.492107] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  4 22:32:21 node-1 kernel: [    0.492109] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.492111] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.492160] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.492279] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.492319] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.492438] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.492477] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.492596] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.492634] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:21 node-1 kernel: [    0.492752] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:21 node-1 kernel: [    0.492795] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  4 22:32:21 node-1 kernel: [    0.492798] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.492800] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.492871] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:21 node-1 kernel: [    0.492935] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.492990] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.493032] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  4 22:32:21 node-1 kernel: [    0.493114] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  4 22:32:21 node-1 kernel: [    0.493219] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  4 22:32:21 node-1 kernel: [    0.493222] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.493224] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.493280] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:21 node-1 kernel: [    0.493334] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.493382] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.493596] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  4 22:32:21 node-1 kernel: [    0.493600] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  4 22:32:21 node-1 kernel: [    0.493661] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:21 node-1 kernel: [    0.493714] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.493763] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.493999] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  4 22:32:21 node-1 kernel: [    0.494003] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  4 22:32:21 node-1 kernel: [    0.494061] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:21 node-1 kernel: [    0.494122] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.494174] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  4 22:32:21 node-1 kernel: [    0.494396] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  4 22:32:21 node-1 kernel: [    0.494399] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  4 22:32:21 node-1 kernel: [    0.494573] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  4 22:32:21 node-1 kernel: [    0.494611] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  4 22:32:21 node-1 kernel: [    0.494688] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  4 22:32:21 node-1 kernel: [    0.494707] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  4 22:32:21 node-1 kernel: [    0.494720] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  4 22:32:21 node-1 kernel: [    0.494733] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  4 22:32:21 node-1 kernel: [    0.494783] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  4 22:32:21 node-1 kernel: [    0.503477] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  4 22:32:21 node-1 kernel: [    0.503501] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  4 22:32:21 node-1 kernel: [    0.503533] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  4 22:32:21 node-1 kernel: [    0.504028] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  4 22:32:21 node-1 kernel: [    0.504031] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:21 node-1 kernel: [    0.504151] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  4 22:32:21 node-1 kernel: [    0.504259] PCI host bridge to bus 0000:80
Oct  4 22:32:21 node-1 kernel: [    0.504261] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  4 22:32:21 node-1 kernel: [    0.504263] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  4 22:32:21 node-1 kernel: [    0.504264] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  4 22:32:21 node-1 kernel: [    0.504273] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.504336] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.504404] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  4 22:32:21 node-1 kernel: [    0.504466] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  4 22:32:21 node-1 kernel: [    0.504472] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  4 22:32:21 node-1 kernel: [    0.504545] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  4 22:32:21 node-1 kernel: [    0.504844] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  4 22:32:21 node-1 kernel: [    0.504876] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  4 22:32:21 node-1 kernel: [    0.504905] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  4 22:32:21 node-1 kernel: [    0.504935] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  4 22:32:21 node-1 kernel: [    0.504964] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:21 node-1 kernel: [    0.504994] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:21 node-1 kernel: [    0.505024] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:21 node-1 kernel: [    0.505054] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:21 node-1 kernel: [    0.505140] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  4 22:32:21 node-1 kernel: [    0.505145] ACPI: \_SB_.UNC1: notify handler is installed
Oct  4 22:32:21 node-1 kernel: [    0.505146] ACPI: \_SB_.UNC0: notify handler is installed
Oct  4 22:32:21 node-1 kernel: [    0.505161] ACPI: \_SB_.PCI0: notify handler is installed
Oct  4 22:32:21 node-1 kernel: [    0.505215] ACPI: \_SB_.PCI1: notify handler is installed
Oct  4 22:32:21 node-1 kernel: [    0.505295] Found 4 acpi root devices
Oct  4 22:32:21 node-1 kernel: [    0.505405] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  4 22:32:21 node-1 kernel: [    0.505407] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  4 22:32:21 node-1 kernel: [    0.505409] vgaarb: loaded
Oct  4 22:32:21 node-1 kernel: [    0.505410] vgaarb: bridge control possible 0000:0c:00.0
Oct  4 22:32:21 node-1 kernel: [    0.505528] SCSI subsystem initialized
Oct  4 22:32:21 node-1 kernel: [    0.505593] libata version 3.00 loaded.
Oct  4 22:32:21 node-1 kernel: [    0.505615] ACPI: bus type USB registered
Oct  4 22:32:21 node-1 kernel: [    0.505625] usbcore: registered new interface driver usbfs
Oct  4 22:32:21 node-1 kernel: [    0.505630] usbcore: registered new interface driver hub
Oct  4 22:32:21 node-1 kernel: [    0.505651] usbcore: registered new device driver usb
Oct  4 22:32:21 node-1 kernel: [    0.505811] PCI: Using ACPI for IRQ routing
Oct  4 22:32:21 node-1 kernel: [    0.509418] PCI: pci_cache_line_size set to 64 bytes
Oct  4 22:32:21 node-1 kernel: [    0.509621] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  4 22:32:21 node-1 kernel: [    0.509623] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct  4 22:32:21 node-1 kernel: [    0.509624] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  4 22:32:21 node-1 kernel: [    0.509689] NetLabel: Initializing
Oct  4 22:32:21 node-1 kernel: [    0.509691] NetLabel:  domain hash size = 128
Oct  4 22:32:21 node-1 kernel: [    0.509691] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  4 22:32:21 node-1 kernel: [    0.509701] NetLabel:  unlabeled traffic allowed by default
Oct  4 22:32:21 node-1 kernel: [    0.509756] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  4 22:32:21 node-1 kernel: [    0.509761] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  4 22:32:21 node-1 kernel: [    0.511817] Switched to clocksource hpet
Oct  4 22:32:21 node-1 kernel: [    0.515806] AppArmor: AppArmor Filesystem Enabled
Oct  4 22:32:21 node-1 kernel: [    0.515825] pnp: PnP ACPI init
Oct  4 22:32:21 node-1 kernel: [    0.515832] ACPI: bus type PNP registered
Oct  4 22:32:21 node-1 kernel: [    0.515943] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  4 22:32:21 node-1 kernel: [    0.515951] pnp 00:01: [dma 4]
Oct  4 22:32:21 node-1 kernel: [    0.515963] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  4 22:32:21 node-1 kernel: [    0.515988] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516008] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516026] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516059] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516111] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516113] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  4 22:32:21 node-1 kernel: [    0.516115] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516116] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516117] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516122] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516124] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  4 22:32:21 node-1 kernel: [    0.516125] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516127] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516128] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516130] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516131] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516133] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  4 22:32:21 node-1 kernel: [    0.516135] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516218] pnp 00:07: [dma 0 disabled]
Oct  4 22:32:21 node-1 kernel: [    0.516247] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516321] pnp 00:08: [dma 0 disabled]
Oct  4 22:32:21 node-1 kernel: [    0.516353] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516403] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  4 22:32:21 node-1 kernel: [    0.516753] pnp: PnP ACPI: found 10 devices
Oct  4 22:32:21 node-1 kernel: [    0.516755] ACPI: bus type PNP unregistered
Oct  4 22:32:21 node-1 kernel: [    0.523063] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  4 22:32:21 node-1 kernel: [    0.523066] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  4 22:32:21 node-1 kernel: [    0.523069] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  4 22:32:21 node-1 kernel: [    0.523073] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  4 22:32:21 node-1 kernel: [    0.523075] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523090] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523122] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  4 22:32:21 node-1 kernel: [    0.523137] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523165] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  4 22:32:21 node-1 kernel: [    0.523180] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  4 22:32:21 node-1 kernel: [    0.523209] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  4 22:32:21 node-1 kernel: [    0.523223] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  4 22:32:21 node-1 kernel: [    0.523252] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  4 22:32:21 node-1 kernel: [    0.523254] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523268] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523297] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  4 22:32:21 node-1 kernel: [    0.523299] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523314] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523342] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  4 22:32:21 node-1 kernel: [    0.523344] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523347] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523351] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  4 22:32:21 node-1 kernel: [    0.523353] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523355] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523359] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  4 22:32:21 node-1 kernel: [    0.523364] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  4 22:32:21 node-1 kernel: [    0.523372] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  4 22:32:21 node-1 kernel: [    0.523375] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  4 22:32:21 node-1 kernel: [    0.523381] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  4 22:32:21 node-1 kernel: [    0.523382] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  4 22:32:21 node-1 kernel: [    0.523383] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  4 22:32:21 node-1 kernel: [    0.523384] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  4 22:32:21 node-1 kernel: [    0.523385] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  4 22:32:21 node-1 kernel: [    0.523386] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  4 22:32:21 node-1 kernel: [    0.523387] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  4 22:32:21 node-1 kernel: [    0.523388] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  4 22:32:21 node-1 kernel: [    0.523389] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523390] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523390] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523391] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523392] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523393] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523394] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523395] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523396] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:21 node-1 kernel: [    0.523397] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523398] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  4 22:32:21 node-1 kernel: [    0.523399] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  4 22:32:21 node-1 kernel: [    0.523400] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  4 22:32:21 node-1 kernel: [    0.523401] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  4 22:32:21 node-1 kernel: [    0.523403] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  4 22:32:21 node-1 kernel: [    0.523404] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  4 22:32:21 node-1 kernel: [    0.523440] NET: Registered protocol family 2
Oct  4 22:32:21 node-1 kernel: [    0.523701] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.524042] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.524191] TCP: Hash tables configured (established 262144 bind 65536)
Oct  4 22:32:21 node-1 kernel: [    0.524229] TCP: reno registered
Oct  4 22:32:21 node-1 kernel: [    0.524257] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.524356] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.524503] NET: Registered protocol family 1
Oct  4 22:32:21 node-1 kernel: [    0.559924] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  4 22:32:21 node-1 kernel: [    0.559939] PCI: CLS 64 bytes, default 64
Oct  4 22:32:21 node-1 kernel: [    0.560001] Trying to unpack rootfs image as initramfs...
Oct  4 22:32:21 node-1 kernel: [    0.778862] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct  4 22:32:21 node-1 kernel: [    0.778896] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  4 22:32:21 node-1 kernel: [    0.778899] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct  4 22:32:21 node-1 kernel: [    0.779322] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779328] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779333] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779338] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779364] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779374] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779383] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779392] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779400] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779409] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779416] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779422] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779429] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779436] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779444] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779451] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:21 node-1 kernel: [    0.779527] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  4 22:32:21 node-1 kernel: [    0.779530] Scanning for low memory corruption every 60 seconds
Oct  4 22:32:21 node-1 kernel: [    0.779933] Initialise system trusted keyring
Oct  4 22:32:21 node-1 kernel: [    0.779989] audit: initializing netlink socket (disabled)
Oct  4 22:32:21 node-1 kernel: [    0.780006] type=2000 audit(1475620304.732:1): initialized
Oct  4 22:32:21 node-1 kernel: [    0.797762] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  4 22:32:21 node-1 kernel: [    0.799332] zbud: loaded
Oct  4 22:32:21 node-1 kernel: [    0.799466] VFS: Disk quotas dquot_6.5.2
Oct  4 22:32:21 node-1 kernel: [    0.799503] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  4 22:32:21 node-1 kernel: [    0.799874] fuse init (API version 7.22)
Oct  4 22:32:21 node-1 kernel: [    0.799934] msgmni has been set to 32768
Oct  4 22:32:21 node-1 kernel: [    0.799983] Key type big_key registered
Oct  4 22:32:21 node-1 kernel: [    0.800468] Key type asymmetric registered
Oct  4 22:32:21 node-1 kernel: [    0.800470] Asymmetric key parser 'x509' registered
Oct  4 22:32:21 node-1 kernel: [    0.800492] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  4 22:32:21 node-1 kernel: [    0.800564] io scheduler noop registered
Oct  4 22:32:21 node-1 kernel: [    0.800566] io scheduler deadline registered (default)
Oct  4 22:32:21 node-1 kernel: [    0.800584] io scheduler cfq registered
Oct  4 22:32:21 node-1 kernel: [    0.800983] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    0.801130] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    0.801244] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    0.801351] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    0.801461] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    0.801577] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    0.801942] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  4 22:32:21 node-1 kernel: [    0.801968] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  4 22:32:21 node-1 kernel: [    0.801984] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  4 22:32:21 node-1 kernel: [    0.801994] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.801996] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.801999] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:21 node-1 kernel: [    0.802004] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802005] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802007] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802008] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802009] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802011] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802012] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802014] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802015] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802017] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802018] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802020] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802022] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:21 node-1 kernel: [    0.802033] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802036] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:21 node-1 kernel: [    0.802050] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802054] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:21 node-1 kernel: [    0.802064] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802066] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:21 node-1 kernel: [    0.802069] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  4 22:32:21 node-1 kernel: [    0.802105] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  4 22:32:21 node-1 kernel: [    0.802112] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  4 22:32:21 node-1 kernel: [    0.802116] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  4 22:32:21 node-1 kernel: [    0.802126] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  4 22:32:21 node-1 kernel: [    0.802168] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  4 22:32:21 node-1 kernel: [    0.802170] vesafb: scrolling: redraw
Oct  4 22:32:21 node-1 kernel: [    0.802171] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  4 22:32:21 node-1 kernel: [    0.822783] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  4 22:32:21 node-1 kernel: [    0.831302] Console: switching to colour frame buffer device 80x30
Oct  4 22:32:21 node-1 kernel: [    0.839979] fb0: VESA VGA frame buffer device
Oct  4 22:32:21 node-1 kernel: [    0.840176] intel_idle: MWAIT substates: 0x2120
Oct  4 22:32:21 node-1 kernel: [    0.840178] intel_idle: v0.4 model 0x3F
Oct  4 22:32:21 node-1 kernel: [    0.840178] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  4 22:32:21 node-1 kernel: [    0.840405] ipmi message handler version 39.2
Oct  4 22:32:21 node-1 kernel: [    0.840679] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  4 22:32:21 node-1 kernel: [    0.841112] ACPI: AC Adapter [P111] (on-line)
Oct  4 22:32:21 node-1 kernel: [    0.846362] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  4 22:32:21 node-1 kernel: [    0.857370] ACPI: Power Button [PWRB]
Oct  4 22:32:21 node-1 kernel: [    0.863122] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  4 22:32:21 node-1 kernel: [    0.874741] ACPI: Power Button [PWRF]
Oct  4 22:32:21 node-1 kernel: [    0.893350] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  4 22:32:21 node-1 kernel: [    0.904999] pstore: Registered erst as persistent store backend
Oct  4 22:32:21 node-1 kernel: [    0.911194] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  4 22:32:21 node-1 kernel: [    0.923119] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  4 22:32:21 node-1 kernel: [    0.949864] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  4 22:32:21 node-1 kernel: [    0.983148] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  4 22:32:21 node-1 kernel: [    0.997314] Linux agpgart interface v0.103
Oct  4 22:32:21 node-1 kernel: [    1.004950] brd: module loaded
Oct  4 22:32:21 node-1 kernel: [    1.011984] loop: module loaded
Oct  4 22:32:21 node-1 kernel: [    1.018690] libphy: Fixed MDIO Bus: probed
Oct  4 22:32:21 node-1 kernel: [    1.025152] tun: Universal TUN/TAP device driver, 1.6
Oct  4 22:32:21 node-1 kernel: [    1.031625] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  4 22:32:21 node-1 kernel: [    1.038153] PPP generic driver version 2.4.2
Oct  4 22:32:21 node-1 kernel: [    1.044545] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  4 22:32:21 node-1 kernel: [    1.050991] ehci-pci: EHCI PCI platform driver
Oct  4 22:32:21 node-1 kernel: [    1.057514] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  4 22:32:21 node-1 kernel: [    1.063922] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  4 22:32:21 node-1 kernel: [    1.076449] ehci-pci 0000:00:1a.0: debug port 2
Oct  4 22:32:21 node-1 kernel: [    1.086642] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  4 22:32:21 node-1 kernel: [    1.086662] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  4 22:32:21 node-1 kernel: [    1.103319] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  4 22:32:21 node-1 kernel: [    1.109400] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  4 22:32:21 node-1 kernel: [    1.115580] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  4 22:32:21 node-1 kernel: [    1.127493] usb usb1: Product: EHCI Host Controller
Oct  4 22:32:21 node-1 kernel: [    1.133524] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  4 22:32:21 node-1 kernel: [    1.139578] usb usb1: SerialNumber: 0000:00:1a.0
Oct  4 22:32:21 node-1 kernel: [    1.145532] hub 1-0:1.0: USB hub found
Oct  4 22:32:21 node-1 kernel: [    1.151303] hub 1-0:1.0: 2 ports detected
Oct  4 22:32:21 node-1 kernel: [    1.157087] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  4 22:32:21 node-1 kernel: [    1.162671] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  4 22:32:21 node-1 kernel: [    1.173592] ehci-pci 0000:00:1d.0: debug port 2
Oct  4 22:32:21 node-1 kernel: [    1.182902] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  4 22:32:21 node-1 kernel: [    1.182909] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  4 22:32:21 node-1 kernel: [    1.199238] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  4 22:32:21 node-1 kernel: [    1.204449] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  4 22:32:21 node-1 kernel: [    1.209759] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  4 22:32:21 node-1 kernel: [    1.220327] usb usb2: Product: EHCI Host Controller
Oct  4 22:32:21 node-1 kernel: [    1.225799] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  4 22:32:21 node-1 kernel: [    1.231355] usb usb2: SerialNumber: 0000:00:1d.0
Oct  4 22:32:21 node-1 kernel: [    1.236880] hub 2-0:1.0: USB hub found
Oct  4 22:32:21 node-1 kernel: [    1.242239] hub 2-0:1.0: 2 ports detected
Oct  4 22:32:21 node-1 kernel: [    1.247623] ehci-platform: EHCI generic platform driver
Oct  4 22:32:21 node-1 kernel: [    1.252941] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  4 22:32:21 node-1 kernel: [    1.258300] ohci-pci: OHCI PCI platform driver
Oct  4 22:32:21 node-1 kernel: [    1.263605] ohci-platform: OHCI generic platform driver
Oct  4 22:32:21 node-1 kernel: [    1.268790] uhci_hcd: USB Universal Host Controller Interface driver
Oct  4 22:32:21 node-1 kernel: [    1.274138] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  4 22:32:21 node-1 kernel: [    1.467017] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  4 22:32:21 node-1 kernel: [    1.774762] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  4 22:32:21 node-1 kernel: [    1.791066] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  4 22:32:21 node-1 kernel: [    1.796747] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  4 22:32:21 node-1 kernel: [    1.802584] hub 1-1:1.0: USB hub found
Oct  4 22:32:21 node-1 kernel: [    1.808177] hub 1-1:1.0: 6 ports detected
Oct  4 22:32:21 node-1 kernel: [    1.922648] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  4 22:32:21 node-1 kernel: [    2.312757] i8042: No controller found
Oct  4 22:32:21 node-1 kernel: [    2.318328] mousedev: PS/2 mouse device common for all mice
Oct  4 22:32:21 node-1 kernel: [    2.324047] rtc_cmos 00:02: RTC can wake from S4
Oct  4 22:32:21 node-1 kernel: [    2.327054] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  4 22:32:21 node-1 kernel: [    2.327055] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  4 22:32:21 node-1 kernel: [    2.327567] hub 2-1:1.0: USB hub found
Oct  4 22:32:21 node-1 kernel: [    2.327798] hub 2-1:1.0: 8 ports detected
Oct  4 22:32:21 node-1 kernel: [    2.352326] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  4 22:32:21 node-1 kernel: [    2.358069] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  4 22:32:21 node-1 kernel: [    2.369401] device-mapper: uevent: version 1.0.3
Oct  4 22:32:21 node-1 kernel: [    2.375097] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  4 22:32:21 node-1 kernel: [    2.386472] ledtrig-cpu: registered to indicate activity on CPUs
Oct  4 22:32:21 node-1 kernel: [    2.392461] TCP: cubic registered
Oct  4 22:32:21 node-1 kernel: [    2.398333] NET: Registered protocol family 10
Oct  4 22:32:21 node-1 kernel: [    2.404389] NET: Registered protocol family 17
Oct  4 22:32:21 node-1 kernel: [    2.410169] Key type dns_resolver registered
Oct  4 22:32:21 node-1 kernel: [    2.416205] Loading compiled-in X.509 certificates
Oct  4 22:32:21 node-1 kernel: [    2.422414] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  4 22:32:21 node-1 kernel: [    2.434056] registered taskstats version 1
Oct  4 22:32:21 node-1 kernel: [    2.442101] Key type trusted registered
Oct  4 22:32:21 node-1 kernel: [    2.449714] Key type encrypted registered
Oct  4 22:32:21 node-1 kernel: [    2.455200] AppArmor: AppArmor sha1 policy hashing enabled
Oct  4 22:32:21 node-1 kernel: [    2.460712] IMA: No TPM chip found, activating TPM-bypass!
Oct  4 22:32:21 node-1 kernel: [    2.466822] regulator-dummy: disabling
Oct  4 22:32:21 node-1 kernel: [    2.472321]   Magic number: 4:138:552
Oct  4 22:32:21 node-1 kernel: [    2.477778] tty ttyS28: hash matches
Oct  4 22:32:21 node-1 kernel: [    2.483147] clockevents clockevent3: hash matches
Oct  4 22:32:21 node-1 kernel: [    2.488477] pci 0000:08:00.0: hash matches
Oct  4 22:32:21 node-1 kernel: [    2.493770] acpi PNP0C0F:03: hash matches
Oct  4 22:32:21 node-1 kernel: [    2.498976] acpi device:138: hash matches
Oct  4 22:32:21 node-1 kernel: [    2.504091] acpi device:10b: hash matches
Oct  4 22:32:21 node-1 kernel: [    2.509244] rtc_cmos 00:02: setting system clock to 2016-10-04 22:31:47 UTC (1475620307)
Oct  4 22:32:21 node-1 kernel: [    2.520831] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  4 22:32:21 node-1 kernel: [    2.526080] EDD information not available.
Oct  4 22:32:21 node-1 kernel: [    2.531276] PM: Hibernation image not present or could not be loaded.
Oct  4 22:32:21 node-1 kernel: [    2.532138] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  4 22:32:21 node-1 kernel: [    2.542526] Write protecting the kernel read-only data: 12288k
Oct  4 22:32:21 node-1 kernel: [    2.548347] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  4 22:32:21 node-1 kernel: [    2.559927] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  4 22:32:21 node-1 kernel: [    2.591052] device-mapper: multipath: version 1.6.0 loaded
Oct  4 22:32:21 node-1 kernel: [    2.598588] systemd-udevd[216]: starting version 204
Oct  4 22:32:21 node-1 kernel: [    2.602321] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  4 22:32:21 node-1 kernel: [    2.628419] md: linear personality registered for level -1
Oct  4 22:32:21 node-1 kernel: [    2.642203] md: multipath personality registered for level -4
Oct  4 22:32:21 node-1 kernel: [    2.649726] md: raid0 personality registered for level 0
Oct  4 22:32:21 node-1 kernel: [    2.657758] md: raid1 personality registered for level 1
Oct  4 22:32:21 node-1 kernel: [    2.667145] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  4 22:32:21 node-1 kernel: [    2.673086] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  4 22:32:21 node-1 kernel: [    2.678998] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  4 22:32:21 node-1 kernel: [    2.681489] megasas: FW now in Ready state
Oct  4 22:32:21 node-1 kernel: [    2.681811] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.681906] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.682274] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.682356] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.682468] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.682599] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.682752] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.682945] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.683085] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.683212] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.683376] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.683508] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.683665] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.683797] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.683890] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.684032] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    2.684634] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  4 22:32:21 node-1 kernel: [    2.711359] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct  4 22:32:21 node-1 kernel: [    2.724236] 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
Oct  4 22:32:21 node-1 kernel: [    2.730006] raid6: sse2x1   11298 MB/s
Oct  4 22:32:21 node-1 kernel: [    2.742303] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  4 22:32:21 node-1 kernel: [    2.742304] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  4 22:32:21 node-1 kernel: [    2.742305] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  4 22:32:21 node-1 kernel: [    2.742316] usb 2-1.4: Manufacturer: Avocent
Oct  4 22:32:21 node-1 kernel: [    2.742318] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  4 22:32:21 node-1 kernel: [    2.784824] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  4 22:32:21 node-1 kernel: [    2.797897] raid6: sse2x2   12090 MB/s
Oct  4 22:32:21 node-1 kernel: [    2.869828] raid6: sse2x4   10137 MB/s
Oct  4 22:32:21 node-1 kernel: [    2.941767] raid6: avx2x1   14949 MB/s
Oct  4 22:32:21 node-1 kernel: [    3.013717] raid6: avx2x2   18865 MB/s
Oct  4 22:32:21 node-1 kernel: [    3.085649] raid6: avx2x4   21350 MB/s
Oct  4 22:32:21 node-1 kernel: [    3.091430] raid6: using algorithm avx2x4 (21350 MB/s)
Oct  4 22:32:21 node-1 kernel: [    3.097184] raid6: using avx2x2 recovery algorithm
Oct  4 22:32:21 node-1 kernel: [    3.102781] megasas:IOC Init cmd success
Oct  4 22:32:21 node-1 kernel: [    3.102785] Switched to clocksource tsc
Oct  4 22:32:21 node-1 kernel: [    3.102942] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.103085] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.103233] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.103348] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.103613] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.124980] hidraw: raw HID events driver (C) Jiri Kosina
Oct  4 22:32:21 node-1 kernel: [    3.130684] xor: automatically using best checksumming function:
Oct  4 22:32:21 node-1 kernel: [    3.134848] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct  4 22:32:21 node-1 kernel: [    3.134849] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct  4 22:32:21 node-1 kernel: [    3.134850] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  4 22:32:21 node-1 kernel: [    3.134910] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.134948] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.134982] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.135016] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.135052] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.135090] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.135190] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.144874] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct  4 22:32:21 node-1 kernel: [    3.144875] 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
Oct  4 22:32:21 node-1 kernel: [    3.144876] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  4 22:32:21 node-1 kernel: [    3.144932] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.144969] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.145006] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.145041] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.145141] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.145769] megasas: INIT adapter done
Oct  4 22:32:21 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  4 22:32:21 node-1 kernel: [    3.153811] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct  4 22:32:21 node-1 kernel: [    3.153812] 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
Oct  4 22:32:21 node-1 kernel: [    3.153813] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  4 22:32:21 node-1 kernel: [    3.153845] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.153882] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.153921] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.153952] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.154030] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  4 22:32:21 node-1 kernel: [    3.217539] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  4 22:32:21 node-1 kernel: [    3.217868] scsi0 : LSI SAS based MegaRAID driver
Oct  4 22:32:21 node-1 kernel: [    3.224811] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  4 22:32:21 node-1 kernel: [    3.236098] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  4 22:32:21 node-1 kernel: [    3.240085] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  4 22:32:21 node-1 kernel: [    3.240219] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  4 22:32:21 node-1 kernel: [    3.240399] sd 0:2:0:0: [sda] Write Protect is off
Oct  4 22:32:21 node-1 kernel: [    3.240400] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  4 22:32:21 node-1 kernel: [    3.240463] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  4 22:32:21 node-1 kernel: [    3.266504]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct  4 22:32:21 node-1 kernel: [    3.268163] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  4 22:32:21 node-1 kernel: [    3.361920] usbcore: registered new interface driver usbhid
Oct  4 22:32:21 node-1 kernel: [    3.368518] usbhid: USB HID core driver
Oct  4 22:32:21 node-1 kernel: [    3.375886] 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
Oct  4 22:32:21 node-1 kernel: [    3.388967] 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
Oct  4 22:32:21 node-1 kernel: [    3.397361]    avx       : 35727.000 MB/sec
Oct  4 22:32:21 node-1 kernel: [    3.409127] 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
Oct  4 22:32:21 node-1 kernel: [    3.422958] async_tx: api initialized (async)
Oct  4 22:32:21 node-1 kernel: [    3.423138] 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
Oct  4 22:32:21 node-1 kernel: [    3.423220] 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
Oct  4 22:32:21 node-1 kernel: [    3.423526] 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
Oct  4 22:32:21 node-1 kernel: [    3.475735] md: raid6 personality registered for level 6
Oct  4 22:32:21 node-1 kernel: [    3.483069] md: raid5 personality registered for level 5
Oct  4 22:32:21 node-1 kernel: [    3.490226] md: raid4 personality registered for level 4
Oct  4 22:32:21 node-1 kernel: [    3.500589] md: raid10 personality registered for level 10
Oct  4 22:32:21 node-1 kernel: [    3.540503] random: lvm urandom read with 33 bits of entropy available
Oct  4 22:32:21 node-1 kernel: [    3.564643] multipathd (368): /proc/368/oom_adj is deprecated, please use /proc/368/oom_score_adj instead.
Oct  4 22:32:21 node-1 kernel: [    3.768894] bio: create slab <bio-1> at 1
Oct  4 22:32:21 node-1 kernel: [    4.564744] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  4 22:32:21 node-1 kernel: [    5.068544] init: plymouth-upstart-bridge main process (553) terminated with status 1
Oct  4 22:32:21 node-1 kernel: [    5.081442] init: plymouth-upstart-bridge main process ended, respawning
Oct  4 22:32:21 node-1 kernel: [    5.185421] random: nonblocking pool is initialized
Oct  4 22:32:21 node-1 kernel: [    5.195636] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  4 22:32:21 node-1 kernel: [    5.229493] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  4 22:32:21 node-1 kernel: [    5.456271] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  4 22:32:21 node-1 kernel: [    5.486228] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  4 22:32:21 node-1 kernel: [    5.567321] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  4 22:32:21 node-1 kernel: [    5.729124] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  4 22:32:21 node-1 kernel: [    5.763593] XFS (dm-0): Mounting Filesystem
Oct  4 22:32:21 node-1 kernel: [    6.026864] XFS (dm-0): Ending clean mount
Oct  4 22:32:21 node-1 kernel: [    6.094242] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  4 22:32:21 node-1 kernel: [    6.128627] XFS (dm-1): Mounting Filesystem
Oct  4 22:32:21 node-1 kernel: [    6.252594] XFS (dm-1): Ending clean mount
Oct  4 22:32:21 node-1 kernel: [    8.399882] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  4 22:32:21 node-1 kernel: [    8.426884] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  4 22:32:21 node-1 kernel: [    8.611351] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  4 22:32:21 node-1 kernel: [    8.611369] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  4 22:32:21 node-1 kernel: [    8.611374] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  4 22:32:21 node-1 kernel: [    8.611378] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  4 22:32:21 node-1 kernel: [    8.646281] systemd-udevd[777]: starting version 204
Oct  4 22:32:21 node-1 kernel: [    8.853020] wmi: Mapper loaded
Oct  4 22:32:21 node-1 kernel: [    8.856533] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  4 22:32:21 node-1 kernel: [    8.856540] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  4 22:32:21 node-1 kernel: [    8.856543] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  4 22:32:21 node-1 kernel: [    8.856545] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  4 22:32:21 node-1 kernel: [    8.856609] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  4 22:32:21 node-1 kernel: [    8.858935] power_meter ACPI000D:00: Found ACPI power meter.
Oct  4 22:32:21 node-1 kernel: [    8.858965] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  4 22:32:21 node-1 kernel: [    8.873638] IPMI System Interface driver.
Oct  4 22:32:21 node-1 kernel: [    8.873688] ipmi_si: probing via ACPI
Oct  4 22:32:21 node-1 kernel: [    8.873709] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  4 22:32:21 node-1 kernel: [    8.873710] ipmi_si: Adding ACPI-specified kcs state machine
Oct  4 22:32:21 node-1 kernel: [    8.873720] ipmi_si: probing via SMBIOS
Oct  4 22:32:21 node-1 kernel: [    8.873721] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  4 22:32:21 node-1 kernel: [    8.873722] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  4 22:32:21 node-1 kernel: [    8.873725] ipmi_si: probing via SPMI
Oct  4 22:32:21 node-1 kernel: [    8.873726] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  4 22:32:21 node-1 kernel: [    8.873727] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  4 22:32:21 node-1 kernel: [    8.873729] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  4 22:32:21 node-1 kernel: [    8.874151] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  4 22:32:21 node-1 kernel: [    8.945200] systemd-udevd[824]: renamed network interface eth1 to enp7s0
Oct  4 22:32:21 node-1 kernel: [    8.977050] systemd-udevd[817]: renamed network interface eth0 to enp6s0
Oct  4 22:32:21 node-1 kernel: [    9.015214] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  4 22:32:21 node-1 kernel: [    9.015220] ipmi_si 00:09: IPMI kcs interface initialized
Oct  4 22:32:21 node-1 kernel: [    9.017052] systemd-udevd[828]: renamed network interface eth2 to enp8s0
Oct  4 22:32:21 node-1 kernel: [    9.049015] systemd-udevd[800]: renamed network interface eth3 to enp9s0
Oct  4 22:32:21 node-1 kernel: [    9.245940] type=1400 audit(1475620314.240:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.246094] type=1400 audit(1475620314.240:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.246222] type=1400 audit(1475620314.240:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.247122] type=1400 audit(1475620314.240:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=974 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.247267] type=1400 audit(1475620314.240:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=974 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.247387] type=1400 audit(1475620314.240:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=974 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.265702] type=1400 audit(1475620314.260:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1045 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.265843] type=1400 audit(1475620314.260:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1045 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.266001] type=1400 audit(1475620314.260:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1045 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.266031] type=1400 audit(1475620314.260:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=981 comm="apparmor_parser"
Oct  4 22:32:21 node-1 kernel: [    9.872909] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  4 22:32:21 node-1 kernel: [    9.873865] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  4 22:32:21 node-1 kernel: [   10.030236] enic 0000:06:00.0 enp6s0: Link UP
Oct  4 22:32:21 node-1 kernel: [   10.030659] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  4 22:32:21 node-1 kernel: [   10.030664] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  4 22:32:21 node-1 kernel: [   19.186148] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  4 22:32:22 node-1 failsafe: Failsafe of 120 seconds reached.
Oct  4 22:32:22 node-1 kernel: [   37.660740] init: failsafe main process (8429) killed by TERM signal
Oct  4 22:32:22 node-1 dbus[8458]: [system] AppArmor D-Bus mediation is enabled
Oct  4 22:32:23 node-1 kernel: [   37.870775] audit_printk_skb: 30 callbacks suppressed
Oct  4 22:32:23 node-1 kernel: [   37.870776] type=1400 audit(1475620343.037:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8555 comm="apparmor_parser"
Oct  4 22:32:23 node-1 kernel: [   37.874337] type=1400 audit(1475620343.037:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8554 comm="apparmor_parser"
Oct  4 22:32:23 node-1 kernel: [   37.874342] type=1400 audit(1475620343.037:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8554 comm="apparmor_parser"
Oct  4 22:32:23 node-1 kernel: [   37.874346] type=1400 audit(1475620343.037:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8554 comm="apparmor_parser"
Oct  4 22:32:23 node-1 kernel: [   37.874564] type=1400 audit(1475620343.037:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8554 comm="apparmor_parser"
Oct  4 22:32:23 node-1 kernel: [   37.874566] type=1400 audit(1475620343.037:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8554 comm="apparmor_parser"
Oct  4 22:32:23 node-1 kernel: [   37.874678] type=1400 audit(1475620343.037:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8554 comm="apparmor_parser"
Oct  4 22:32:23 node-1 kernel: [   37.941598] type=1400 audit(1475620343.105:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8557 comm="apparmor_parser"
Oct  4 22:32:23 node-1 anacron[8622]: Anacron 2.3 started on 2016-10-04
Oct  4 22:32:23 node-1 cron[8587]: (CRON) INFO (pidfile fd = 3)
Oct  4 22:32:23 node-1 cron[8626]: (CRON) STARTUP (fork ok)
Oct  4 22:32:23 node-1 anacron[8622]: Will run job `cron.daily' in 5 min.
Oct  4 22:32:23 node-1 anacron[8622]: Will run job `cron.weekly' in 10 min.
Oct  4 22:32:23 node-1 anacron[8622]: Will run job `cron.monthly' in 15 min.
Oct  4 22:32:23 node-1 anacron[8622]: Jobs will be executed sequentially
Oct  4 22:32:23 node-1 multipathd: path checkers start up
Oct  4 22:32:23 node-1 cron[8626]: (CRON) INFO (Running @reboot jobs)
Oct  4 22:32:23 node-1 postfix/master[8766]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  4 22:32:26 node-1 puppet-agent[8951]: Reopening log files
Oct  4 22:32:27 node-1 puppet-agent[8951]: Could not request certificate: Connection refused - connect(2)
Oct  4 22:32:41 node-1 puppet-user[9030]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  4 22:32:41 node-1 puppet-user[9030]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct  4 22:32:42 node-1 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  4 22:32:42 node-1 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  4 22:32:42 node-1 puppet-user[9030]: Finished catalog run in 1.02 seconds
Oct  4 22:32:44 node-1 multipathd: uevent trigger error
Oct  4 22:32:44 node-1 puppet-user[9460]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  4 22:32:44 node-1 puppet-user[9460]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct  4 22:32:44 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  4 22:32:44 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  4 22:32:44 node-1 puppet-user[9460]: (/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"]'
Oct  4 22:32:44 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  4 22:32:44 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  4 22:32:44 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  4 22:32:44 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  4 22:32:44 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  4 22:32:44 node-1 puppet-user[9460]: Finished catalog run in 0.06 seconds
Oct  4 22:32:45 node-1 puppet-user[9930]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  4 22:32:45 node-1 puppet-user[9930]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct  4 22:32:46 node-1 puppet-user[9930]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  4 22:32:46 node-1 puppet-user[9930]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  4 22:32:46 node-1 puppet-user[9930]: Finished catalog run in 0.02 seconds
Oct  4 22:32:47 node-1 puppet-user[10405]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  4 22:32:47 node-1 puppet-user[10405]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct  4 22:32:47 node-1 puppet-user[10405]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  4 22:32:47 node-1 puppet-user[10405]: Finished catalog run in 0.02 seconds
Oct  4 22:32:49 node-1 puppet-user[10988]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  4 22:32:49 node-1 puppet-user[10988]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Oct  4 22:32:49 node-1 puppet-user[10988]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  4 22:32:49 node-1 kernel: [   64.557127] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  4 22:32:49 node-1 kernel: [   64.557179] 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.
Oct  4 22:32:49 node-1 puppet-user[10988]: (/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'
Oct  4 22:32:49 node-1 puppet-user[10988]: Finished catalog run in 0.05 seconds
Oct  4 22:32:51 node-1 puppet-user[11462]: (Scope(Class[main])) MODULAR: sync_time
Oct  4 22:32:51 node-1 puppet-user[11462]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  4 22:32:51 node-1 ntpdate[11881]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Oct  4 22:32:57 node-1 ntpdate[11881]: adjust time server 10.20.0.2 offset -0.000103 sec
Oct  4 22:32:57 node-1 puppet-user[11462]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  4 22:32:57 node-1 puppet-user[11462]: Finished catalog run in 6.20 seconds
Oct  4 22:33:01 node-1 CRON[12212]: (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")
Oct  4 22:33:03 node-1 puppet-user[12269]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  4 22:33:03 node-1 puppet-user[12269]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct  4 22:33:03 node-1 puppet-user[12269]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  4 22:33:03 node-1 puppet-user[12269]: Finished catalog run in 0.06 seconds
Oct  4 22:33:05 node-1 puppet-user[12725]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  4 22:33:05 node-1 puppet-user[12725]: Compiled catalog for node-1.domain.tld in environment production in 0.46 seconds
Oct  4 22:33:05 node-1 puppet-user[12725]: (/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
Oct  4 22:33:05 node-1 puppet-user[12725]: (/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
Oct  4 22:33:05 node-1 puppet-user[12725]: (/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
Oct  4 22:33:05 node-1 puppet-user[12725]: (/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
Oct  4 22:33:05 node-1 puppet-user[12725]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  4 22:33:05 node-1 puppet-user[12725]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct  4 22:33:05 node-1 puppet-user[12725]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  4 22:33:05 node-1 puppet-user[12725]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct  4 22:33:05 node-1 puppet-user[12725]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  4 22:33:05 node-1 puppet-user[12725]: (/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
Oct  4 22:33:05 node-1 puppet-user[12725]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  4 22:33:05 node-1 puppet-user[12725]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct  4 22:33:06 node-1 puppet-user[12725]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  4 22:33:06 node-1 puppet-user[12725]: Finished catalog run in 0.82 seconds
Oct  4 22:33:08 node-1 puppet-user[13233]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  4 22:33:08 node-1 puppet-user[13233]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct  4 22:33:11 node-1 puppet-user[13233]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  4 22:33:13 node-1 kernel: [   88.060445] init: plymouth-upstart-bridge main process ended, respawning
Oct  4 22:33:13 node-1 puppet-agent[8951]: Could not run: SIGTERM
Oct  4 22:33:13 node-1 kernel: [   88.374685] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  4 22:33:13 node-1 ec2: 
Oct  4 22:33:13 node-1 ec2: #############################################################
Oct  4 22:33:13 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  4 22:33:13 node-1 ec2: 1024 59:38:c2:44:28:fb:f6:31:57:18:ee:cf:30:9f:64:1c  root@node-1.domain.tld (DSA)
Oct  4 22:33:13 node-1 ec2: 256 10:c7:fe:6b:cb:86:27:0c:3f:ff:24:6f:8c:f5:95:a8  root@node-1.domain.tld (ECDSA)
Oct  4 22:33:13 node-1 ec2: 256 63:ce:8c:22:93:49:48:89:c5:32:18:69:09:1b:02:d0  root@node-1.domain.tld (ED25519)
Oct  4 22:33:13 node-1 ec2: 2048 cc:b9:3d:32:96:a0:dd:ec:dc:90:10:91:a6:26:ac:2f  root@node-1.domain.tld (RSA)
Oct  4 22:33:13 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  4 22:33:13 node-1 ec2: #############################################################
Oct  4 22:33:27 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  4 22:33:27 node-1 nailgun-agent: D, [2016-10-04T22:33:01.519401 #12215] DEBUG -- : Sleep for 26 seconds before sending request
Oct  4 22:33:27 node-1 nailgun-agent: I, [2016-10-04T22:33:27.541885 #12215]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  4 22:33:28 node-1 nailgun-agent: D, [2016-10-04T22:33:28.212603 #12215] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct  4 22:33:38 node-1 puppet-user[13233]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  4 22:33:38 node-1 puppet-user[13233]: Finished catalog run in 29.78 seconds
Oct  4 22:33:39 node-1 puppet-user[16023]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  4 22:33:40 node-1 puppet-user[16023]: Compiled catalog for node-1.domain.tld in environment production in 0.56 seconds
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.429690 #12215] DEBUG -- : Trying to find block devices
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.429883 #12215] DEBUG -- : Found block device: sda
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.429990 #12215] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.430052 #12215] DEBUG -- : Trying to get list of physical devices
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.430433 #12215] DEBUG -- : Getting udev properties for device: sda
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.434350 #12215] 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
Oct  4 22:33:40 node-1 nailgun-agent: 6005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22363", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.434423 #12215] DEBUG -- : Trying to find out if device sda is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.434537 #12215] DEBUG -- : Device sda removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.434580 #12215] DEBUG -- : Device sda seems to be appropriate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.435631 #12215] DEBUG -- : Getting udev properties for device: dm-0
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.438961 #12215] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-grRnZ6Vi4xoidIL3ZnsWWqsmLoIjZUEshq18mHlpNr4ylhKm2ACY8IU1npnmAwTu /dev/disk/by-uuid/0752b7df-c201-4f99-b004-b5115dc409f5 /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-grRnZ6Vi4xoidIL3ZnsWWqsmLoIjZUEshq18mHlpNr4ylhKm2ACY8IU1npnmAwTu", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0752b7df-c201-4f99-b004-b5115dc409f5", "ID_FS_UUID_ENC"=>"0752b7df-c201-4f99-b004-b5115dc409f5", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23852", "nomdmonddf"=>"1", "nom
Oct  4 22:33:40 node-1 nailgun-agent: dmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.439038 #12215] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.439184 #12215] DEBUG -- : Device dm-0 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.439225 #12215] DEBUG -- : Device dm-0 seems to be appropriate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.439266 #12215] DEBUG -- : Getting udev properties for device: dm-1
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.442684 #12215] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-s6daJchqfKT4HqUOPyULhW7NueIkZhWtZB4Fsy5eT8sjb25dCpYeAKOAGvG5Q0J8 /dev/disk/by-uuid/a32d8202-6cf3-4fd5-989e-39afa1c3f5b7 /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-s6daJchqfKT4HqUOPyULhW7NueIkZhWtZB4Fsy5eT8sjb25dCpYeAKOAGvG5Q0J8", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a32d8202-6cf3-4fd5-989e-39afa1c3f5b7", "ID_FS_UUID_ENC"=>"a32d8202-6cf3-4fd5-989e-39afa1c3f5b7", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5
Oct  4 22:33:40 node-1 nailgun-agent: 0189", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.442908 #12215] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.442996 #12215] DEBUG -- : Device dm-1 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.443037 #12215] DEBUG -- : Device dm-1 seems to be appropriate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.443077 #12215] DEBUG -- : Getting udev properties for device: dm-2
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.446761 #12215] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-9kmvm6ROdg2dR31pCAp9qUmSHcuhZunUiXnVOPAe05LkjqUy8fsHjgytUsOeWVDB /dev/disk/by-uuid/93bc461f-1ef9-4d71-91af-6c2a6b86a346 /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-9kmvm6ROdg2dR31pCAp9qUmSHcuhZunUiXnVOPAe05LkjqUy8fsHjgytUsOeWVDB", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"93bc461f-1ef9-4d71-91af-6c2a6b86a346", "ID_FS_UUID_ENC"=>"93bc461f-1ef9-4d71-91af-6c2a6b86a346", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70258", "nomdmon
Oct  4 22:33:40 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.446837 #12215] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.446926 #12215] DEBUG -- : Device dm-2 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.446966 #12215] DEBUG -- : Device dm-2 seems to be appropriate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.447010 #12215] DEBUG -- : Getting udev properties for device: dm-3
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.450416 #12215] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-2vA0yM0P1wi92tazThrRk7zgzWIdYI7RsQkPd9HP1dbNdQ21NFj1JbB43b7QcorA /dev/disk/by-uuid/0551328c-f3e8-4240-be6a-53320d886bdd /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-2vA0yM0P1wi92tazThrRk7zgzWIdYI7RsQkPd9HP1dbNdQ21NFj1JbB43b7QcorA", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0551328c-f3e8-4240-be6a-53320d886bdd", "ID_FS_UUID_ENC"=>"0551328c-f3e8-4240-be6a-53320d886bdd", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80378", "nomdmonddf"=>"1",
Oct  4 22:33:40 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.450492 #12215] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.450597 #12215] DEBUG -- : Device dm-3 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.450662 #12215] DEBUG -- : Device dm-3 seems to be appropriate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.450702 #12215] DEBUG -- : Getting udev properties for device: dm-4
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.454178 #12215] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-0FmM4rCrcwjHAtvx4KOWOwDF1lhSxPuhmMwhhTBpbQJWS2OT8qokmKHy4M6hjZm5 /dev/disk/by-uuid/ac438202-8ef3-48c5-aa27-c9eceb43ff95 /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-0FmM4rCrcwjHAtvx4KOWOwDF1lhSxPuhmMwhhTBpbQJWS2OT8qokmKHy4M6hjZm5", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ac438202-8ef3-48c5-aa27-c9eceb43ff95", "ID_FS_UUID_ENC"=>"ac438202-8ef3-48c5-aa27-c9eceb43ff95", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81530", "nomdmonddf"=>"1", "nom
Oct  4 22:33:40 node-1 nailgun-agent: dmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.454253 #12215] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.454339 #12215] DEBUG -- : Device dm-4 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.454378 #12215] DEBUG -- : Device dm-4 seems to be appropriate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.454419 #12215] DEBUG -- : Getting udev properties for device: dm-5
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.457597 #12215] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-0FmM4rCrcwjHAtvx4KOWOwDF1lhSxPuhABc3DiKYRca8KWrtzjWzWU2zVloLvvTN /dev/disk/by-uuid/cc077664-8e2b-4d47-b73b-f5ecc5e96ff4 /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-0FmM4rCrcwjHAtvx4KOWOwDF1lhSxPuhABc3DiKYRca8KWrtzjWzWU2zVloLvvTN", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"cc077664-8e2b-4d47-b73b-f5ecc5e96ff4", "ID_FS_UUID_ENC"=>"cc077664-8e2b-4d47-b73b-f5ecc5e96ff4", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82002", "nomdmonddf"=>"1", "nomdmonisw
Oct  4 22:33:40 node-1 nailgun-agent: "=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.457671 #12215] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.457757 #12215] DEBUG -- : Device dm-5 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.457796 #12215] DEBUG -- : Device dm-5 seems to be appropriate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.457909 #12215] DEBUG -- : Getting udev properties for device: ram0
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.460533 #12215] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24535", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.460632 #12215] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.460726 #12215] DEBUG -- : Device ram0 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.460819 #12215] DEBUG -- : Getting udev properties for device: ram1
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.463715 #12215] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24908", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.463770 #12215] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.463842 #12215] DEBUG -- : Device ram1 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.463884 #12215] DEBUG -- : Getting udev properties for device: ram2
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.466752 #12215] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27360", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.466808 #12215] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.466917 #12215] DEBUG -- : Device ram2 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.466975 #12215] DEBUG -- : Getting udev properties for device: ram3
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.469731 #12215] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27912", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.469804 #12215] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.469893 #12215] DEBUG -- : Device ram3 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.469951 #12215] DEBUG -- : Getting udev properties for device: ram4
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.472324 #12215] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28591", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.472429 #12215] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.472520 #12215] DEBUG -- : Device ram4 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.472578 #12215] DEBUG -- : Getting udev properties for device: ram5
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.475556 #12215] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57538", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.475593 #12215] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.475666 #12215] DEBUG -- : Device ram5 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.475728 #12215] DEBUG -- : Getting udev properties for device: ram6
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.478370 #12215] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58112", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.478405 #12215] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.478495 #12215] DEBUG -- : Device ram6 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.478541 #12215] DEBUG -- : Getting udev properties for device: ram7
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.482417 #12215] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58335", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.482478 #12215] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.482562 #12215] DEBUG -- : Device ram7 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.482630 #12215] DEBUG -- : Getting udev properties for device: ram8
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.485058 #12215] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58639", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.485115 #12215] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.485210 #12215] DEBUG -- : Device ram8 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.485252 #12215] DEBUG -- : Getting udev properties for device: ram9
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.487810 #12215] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58757", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.487867 #12215] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.487988 #12215] DEBUG -- : Device ram9 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.488046 #12215] DEBUG -- : Getting udev properties for device: loop0
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.490528 #12215] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22436", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.490584 #12215] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.490656 #12215] DEBUG -- : Device loop0 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.490711 #12215] DEBUG -- : Getting udev properties for device: loop1
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.493524 #12215] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22634", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.493610 #12215] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.493727 #12215] DEBUG -- : Device loop1 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.493770 #12215] DEBUG -- : Getting udev properties for device: loop2
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.497404 #12215] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22943", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.497459 #12215] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.497558 #12215] DEBUG -- : Device loop2 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.497626 #12215] DEBUG -- : Getting udev properties for device: loop3
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.501195 #12215] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23163", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.501250 #12215] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.501319 #12215] DEBUG -- : Device loop3 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.501379 #12215] DEBUG -- : Getting udev properties for device: loop4
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.512058 #12215] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23394", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.512135 #12215] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.512256 #12215] DEBUG -- : Device loop4 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.512308 #12215] DEBUG -- : Getting udev properties for device: loop5
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.516693 #12215] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23600", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.516794 #12215] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.516852 #12215] DEBUG -- : Device loop5 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.516881 #12215] DEBUG -- : Getting udev properties for device: loop6
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.519719 #12215] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23750", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.519795 #12215] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.519971 #12215] DEBUG -- : Device loop6 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.520027 #12215] DEBUG -- : Getting udev properties for device: loop7
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.522708 #12215] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23969", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.522786 #12215] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.522877 #12215] DEBUG -- : Device loop7 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.523044 #12215] DEBUG -- : Getting udev properties for device: ram10
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.525770 #12215] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"25312", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.525847 #12215] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.525940 #12215] DEBUG -- : Device ram10 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.526000 #12215] DEBUG -- : Getting udev properties for device: ram11
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.529838 #12215] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"25586", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.529913 #12215] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.530007 #12215] DEBUG -- : Device ram11 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.530065 #12215] DEBUG -- : Getting udev properties for device: ram12
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.533489 #12215] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"26027", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.533562 #12215] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.533679 #12215] DEBUG -- : Device ram12 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.533741 #12215] DEBUG -- : Getting udev properties for device: ram13
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.536256 #12215] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"26323", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.536330 #12215] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.536438 #12215] DEBUG -- : Device ram13 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.536494 #12215] DEBUG -- : Getting udev properties for device: ram14
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.539183 #12215] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"26774", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.539249 #12215] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.539334 #12215] DEBUG -- : Device ram14 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.539384 #12215] DEBUG -- : Getting udev properties for device: ram15
Oct  4 22:33:40 node-1 puppet-user[16023]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  4 22:33:40 node-1 puppet-user[16023]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  4 22:33:40 node-1 puppet-user[16023]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  4 22:33:40 node-1 puppet-user[16023]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  4 22:33:40 node-1 puppet-user[16023]: Finished catalog run in 0.11 seconds
Oct  4 22:33:40 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.541828 #12215] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"27113", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.541962 #12215] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542063 #12215] DEBUG -- : Device ram15 removable parameter: "0"
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542147 #12215] 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"}]
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542183 #12215] DEBUG -- : Block device seems to be physical data storage: sda
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542262 #12215] DEBUG -- : Found block device: dm-0
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542300 #12215] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542337 #12215] DEBUG -- : Found block device: dm-1
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542368 #12215] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542393 #12215] DEBUG -- : Found block device: dm-2
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542420 #12215] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542505 #12215] DEBUG -- : Found block device: dm-3
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542534 #12215] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542557 #12215] DEBUG -- : Found block device: dm-4
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542584 #12215] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542607 #12215] DEBUG -- : Found block device: dm-5
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542633 #12215] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542657 #12215] DEBUG -- : Found block device: ram0
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542684 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542707 #12215] DEBUG -- : Found block device: ram1
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542737 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542846 #12215] DEBUG -- : Found block device: ram2
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542876 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542900 #12215] DEBUG -- : Found block device: ram3
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542927 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542952 #12215] DEBUG -- : Found block device: ram4
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.542980 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543002 #12215] DEBUG -- : Found block device: ram5
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543029 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543053 #12215] DEBUG -- : Found block device: ram6
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543162 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543188 #12215] DEBUG -- : Found block device: ram7
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543216 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543244 #12215] DEBUG -- : Found block device: ram8
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543270 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543294 #12215] DEBUG -- : Found block device: ram9
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543323 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543347 #12215] DEBUG -- : Found block device: loop0
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543374 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543495 #12215] DEBUG -- : Found block device: loop1
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543524 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543547 #12215] DEBUG -- : Found block device: loop2
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543572 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543595 #12215] DEBUG -- : Found block device: loop3
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543624 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543646 #12215] DEBUG -- : Found block device: loop4
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543674 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543699 #12215] DEBUG -- : Found block device: loop5
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543800 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543826 #12215] DEBUG -- : Found block device: loop6
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543851 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543875 #12215] DEBUG -- : Found block device: loop7
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543901 #12215] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543923 #12215] DEBUG -- : Found block device: ram10
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543949 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.543973 #12215] DEBUG -- : Found block device: ram11
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544001 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544105 #12215] DEBUG -- : Found block device: ram12
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544131 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544153 #12215] DEBUG -- : Found block device: ram13
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544178 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544202 #12215] DEBUG -- : Found block device: ram14
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544227 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544249 #12215] DEBUG -- : Found block device: ram15
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544274 #12215] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.544429 #12215] 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}]
Oct  4 22:33:40 node-1 nailgun-agent: D, [2016-10-04T22:33:40.794027 #12215] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct  4 22:33:40 node-1 nailgun-agent: I, [2016-10-04T22:33:40.794345 #12215]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct  4 22:33:42 node-1 puppet-user[16663]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  4 22:33:43 node-1 puppet-user[16663]: Compiled catalog for node-1.domain.tld in environment production in 0.88 seconds
Oct  4 22:33:43 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  4 22:33:43 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  4 22:33:43 node-1 crontab[17107]: (root) LIST (root)
Oct  4 22:33:43 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  4 22:33:43 node-1 crontab[17108]: (root) REPLACE (root)
Oct  4 22:33:44 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  4 22:33:45 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/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
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  4 22:33:46 node-1 puppet-user[16663]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct  4 22:33:46 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8402" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:46 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  4 22:33:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:33:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:33:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:33:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:33:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:34:58 node-1 ntpdate[27942]: no servers can be used, exiting
<27>Oct  4 22:34:58 node-1 ntpdate[28223]: no servers can be used, exiting
<27>Oct  4 22:35:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:45 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:45 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:45 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:45 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:45 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:45 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:45 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:35:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:42 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:42 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:42 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:42 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:42 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:42 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:50 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:50 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:50 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:51 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:51 node-1 multipathd: uevent trigger error
<27>Oct  4 22:36:53 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  4 22:36:53 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  4 22:36:59 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  4 22:36:59 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  4 22:37:04 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  4 22:37:10 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  4 22:37:10 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  4 22:37:17 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:17 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:17 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:17 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:17 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:17 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:30 node-1 multipathd: uevent trigger error
<129>Oct  4 22:37:32 node-1 haproxy[15576]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:32 node-1 haproxy[15576]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:33 node-1 haproxy[15583]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:33 node-1 haproxy[15583]: proxy mysqld has no server available!
<27>Oct  4 22:37:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:39 node-1 multipathd: uevent trigger error
<129>Oct  4 22:37:41 node-1 haproxy[18176]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:41 node-1 haproxy[18176]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:42 node-1 haproxy[18180]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:42 node-1 haproxy[18180]: proxy mysqld has no server available!
<129>Oct  4 22:37:42 node-1 haproxy[18180]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:42 node-1 haproxy[18180]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:43 node-1 haproxy[18180]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:43 node-1 haproxy[18180]: proxy object-storage has no server available!
<27>Oct  4 22:37:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:44 node-1 multipathd: uevent trigger error
<129>Oct  4 22:37:46 node-1 haproxy[19582]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:46 node-1 haproxy[19582]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:47 node-1 haproxy[19586]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:47 node-1 haproxy[19586]: proxy neutron has no server available!
<129>Oct  4 22:37:47 node-1 haproxy[19586]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:47 node-1 haproxy[19586]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:47 node-1 haproxy[19586]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:47 node-1 haproxy[19586]: proxy mysqld has no server available!
<129>Oct  4 22:37:47 node-1 haproxy[19586]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:48 node-1 haproxy[19586]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:48 node-1 haproxy[19586]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:48 node-1 haproxy[19586]: proxy object-storage has no server available!
<27>Oct  4 22:37:49 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:49 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:49 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:49 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:49 node-1 multipathd: uevent trigger error
<129>Oct  4 22:37:52 node-1 haproxy[20966]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:52 node-1 haproxy[20966]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:52 node-1 haproxy[20966]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:52 node-1 haproxy[20966]: proxy keystone-1 has no server available!
<129>Oct  4 22:37:52 node-1 haproxy[20966]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:52 node-1 haproxy[20966]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:52 node-1 haproxy[20966]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:52 node-1 haproxy[20966]: proxy keystone-2 has no server available!
<129>Oct  4 22:37:53 node-1 haproxy[20972]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:53 node-1 haproxy[20972]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:53 node-1 haproxy[20972]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:53 node-1 haproxy[20972]: proxy neutron has no server available!
<129>Oct  4 22:37:53 node-1 haproxy[20972]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:53 node-1 haproxy[20972]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:53 node-1 haproxy[20972]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:53 node-1 haproxy[20972]: proxy mysqld has no server available!
<129>Oct  4 22:37:53 node-1 haproxy[20972]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:54 node-1 haproxy[20972]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:54 node-1 haproxy[20972]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:54 node-1 haproxy[20972]: proxy object-storage has no server available!
<27>Oct  4 22:37:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-1 multipathd: uevent trigger error
<129>Oct  4 22:37:57 node-1 haproxy[22290]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:57 node-1 haproxy[22290]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:57 node-1 haproxy[22290]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:57 node-1 haproxy[22290]: proxy keystone-1 has no server available!
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:58 node-1 haproxy[22294]: proxy keystone-2 has no server available!
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:58 node-1 haproxy[22294]: proxy neutron has no server available!
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:58 node-1 haproxy[22294]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:58 node-1 haproxy[22294]: proxy mysqld has no server available!
<129>Oct  4 22:37:59 node-1 haproxy[22294]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:59 node-1 haproxy[22294]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:59 node-1 haproxy[22294]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:59 node-1 haproxy[22294]: proxy object-storage has no server available!
<129>Oct  4 22:37:59 node-1 haproxy[22294]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:59 node-1 haproxy[22294]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:37:59 node-1 haproxy[22294]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:37:59 node-1 haproxy[22294]: proxy aodh has no server available!
<27>Oct  4 22:38:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-1 multipathd: uevent trigger error
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:03 node-1 haproxy[23674]: proxy keystone-1 has no server available!
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:03 node-1 haproxy[23674]: proxy keystone-2 has no server available!
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:03 node-1 haproxy[23674]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:03 node-1 haproxy[23674]: proxy neutron has no server available!
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:04 node-1 haproxy[23678]: proxy mysqld has no server available!
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:04 node-1 haproxy[23678]: proxy object-storage has no server available!
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:04 node-1 haproxy[23678]: proxy aodh has no server available!
<129>Oct  4 22:38:04 node-1 haproxy[23678]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:05 node-1 haproxy[23678]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:05 node-1 haproxy[23678]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:05 node-1 haproxy[23678]: proxy ceilometer has no server available!
<27>Oct  4 22:38:06 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:06 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:06 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:06 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:06 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:06 node-1 multipathd: uevent trigger error
<129>Oct  4 22:38:08 node-1 haproxy[25054]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:08 node-1 haproxy[25054]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:08 node-1 haproxy[25054]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:08 node-1 haproxy[25054]: proxy keystone-1 has no server available!
<129>Oct  4 22:38:08 node-1 haproxy[25054]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:09 node-1 haproxy[25058]: proxy keystone-2 has no server available!
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:09 node-1 haproxy[25058]: proxy neutron has no server available!
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:09 node-1 haproxy[25058]: proxy mysqld has no server available!
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:09 node-1 haproxy[25058]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:09 node-1 haproxy[25058]: proxy object-storage has no server available!
<129>Oct  4 22:38:10 node-1 haproxy[25058]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:10 node-1 haproxy[25058]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:10 node-1 haproxy[25058]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:10 node-1 haproxy[25058]: proxy aodh has no server available!
<129>Oct  4 22:38:10 node-1 haproxy[25058]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:10 node-1 haproxy[25058]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:10 node-1 haproxy[25058]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:10 node-1 haproxy[25058]: proxy ceilometer has no server available!
<27>Oct  4 22:38:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:11 node-1 multipathd: uevent trigger error
<129>Oct  4 22:38:13 node-1 haproxy[26389]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:14 node-1 haproxy[26395]: proxy keystone-1 has no server available!
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:14 node-1 haproxy[26395]: proxy keystone-2 has no server available!
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:14 node-1 haproxy[26395]: proxy neutron has no server available!
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:14 node-1 haproxy[26395]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:14 node-1 haproxy[26395]: proxy mysqld has no server available!
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:15 node-1 haproxy[26395]: proxy object-storage has no server available!
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:15 node-1 haproxy[26395]: proxy aodh has no server available!
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:15 node-1 haproxy[26395]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:15 node-1 haproxy[26395]: proxy ceilometer has no server available!
<27>Oct  4 22:38:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:17 node-1 multipathd: uevent trigger error
<129>Oct  4 22:38:19 node-1 haproxy[27793]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:19 node-1 haproxy[27793]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:19 node-1 haproxy[27793]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:19 node-1 haproxy[27793]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:19 node-1 haproxy[27793]: proxy keystone-1 has no server available!
<129>Oct  4 22:38:19 node-1 haproxy[27793]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:20 node-1 haproxy[27797]: proxy keystone-2 has no server available!
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:20 node-1 haproxy[27797]: proxy glance-api has no server available!
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:20 node-1 haproxy[27797]: proxy glance-glare has no server available!
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:20 node-1 haproxy[27797]: proxy neutron has no server available!
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:20 node-1 haproxy[27797]: proxy glance-registry has no server available!
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:20 node-1 haproxy[27797]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:20 node-1 haproxy[27797]: proxy mysqld has no server available!
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:21 node-1 haproxy[27797]: proxy object-storage has no server available!
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:21 node-1 haproxy[27797]: proxy aodh has no server available!
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:21 node-1 haproxy[27797]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:21 node-1 haproxy[27797]: proxy ceilometer has no server available!
<27>Oct  4 22:38:22 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:22 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:22 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:22 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:22 node-1 multipathd: uevent trigger error
<129>Oct  4 22:38:25 node-1 haproxy[29329]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:25 node-1 haproxy[29329]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:25 node-1 haproxy[29329]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:25 node-1 haproxy[29329]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:25 node-1 haproxy[29329]: proxy keystone-1 has no server available!
<129>Oct  4 22:38:25 node-1 haproxy[29329]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:25 node-1 haproxy[29329]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:25 node-1 haproxy[29329]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:25 node-1 haproxy[29329]: proxy keystone-2 has no server available!
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:26 node-1 haproxy[29333]: proxy nova-api has no server available!
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:26 node-1 haproxy[29333]: proxy nova-metadata-api has no server available!
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:26 node-1 haproxy[29333]: proxy glance-api has no server available!
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:26 node-1 haproxy[29333]: proxy glance-glare has no server available!
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:26 node-1 haproxy[29333]: proxy neutron has no server available!
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:26 node-1 haproxy[29333]: proxy glance-registry has no server available!
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:26 node-1 haproxy[29333]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:26 node-1 haproxy[29333]: proxy mysqld has no server available!
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:27 node-1 haproxy[29333]: proxy object-storage has no server available!
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:27 node-1 haproxy[29333]: proxy aodh has no server available!
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:27 node-1 haproxy[29333]: proxy ceilometer has no server available!
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:27 node-1 haproxy[29333]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:27 node-1 haproxy[29333]: proxy nova-novncproxy has no server available!
<27>Oct  4 22:38:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:28 node-1 multipathd: uevent trigger error
<129>Oct  4 22:38:30 node-1 haproxy[30667]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:31 node-1 haproxy[30671]: proxy keystone-1 has no server available!
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:31 node-1 haproxy[30671]: proxy keystone-2 has no server available!
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:31 node-1 haproxy[30671]: proxy nova-api has no server available!
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:31 node-1 haproxy[30671]: proxy nova-metadata-api has no server available!
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:31 node-1 haproxy[30671]: proxy cinder-api has no server available!
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:31 node-1 haproxy[30671]: proxy glance-api has no server available!
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:31 node-1 haproxy[30671]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:31 node-1 haproxy[30671]: proxy glance-glare has no server available!
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:32 node-1 haproxy[30671]: proxy neutron has no server available!
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:32 node-1 haproxy[30671]: proxy glance-registry has no server available!
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:32 node-1 haproxy[30671]: proxy mysqld has no server available!
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:32 node-1 haproxy[30671]: proxy object-storage has no server available!
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:32 node-1 haproxy[30671]: proxy aodh has no server available!
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:32 node-1 haproxy[30671]: proxy ceilometer has no server available!
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:32 node-1 haproxy[30671]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:32 node-1 haproxy[30671]: proxy nova-novncproxy has no server available!
<27>Oct  4 22:38:34 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:34 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:34 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:34 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:34 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:34 node-1 multipathd: uevent trigger error
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:36 node-1 haproxy[32067]: proxy keystone-1 has no server available!
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:36 node-1 haproxy[32067]: proxy keystone-2 has no server available!
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:36 node-1 haproxy[32067]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy nova-api has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy nova-metadata-api has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy cinder-api has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy glance-api has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy glance-glare has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy neutron has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy glance-registry has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy mysqld has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:37 node-1 haproxy[32089]: proxy object-storage has no server available!
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:37 node-1 haproxy[32089]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:38 node-1 haproxy[32089]: proxy aodh has no server available!
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:38 node-1 haproxy[32089]: proxy ceilometer has no server available!
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:38 node-1 haproxy[32089]: proxy heat-api has no server available!
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:38 node-1 haproxy[32089]: proxy heat-api-cfn has no server available!
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:38 node-1 haproxy[32089]: proxy heat-api-cloudwatch has no server available!
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  4 22:38:38 node-1 haproxy[32089]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:38 node-1 haproxy[32089]: proxy nova-novncproxy has no server available!
<27>Oct  4 22:38:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:38:50 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  4 22:39:15 node-1 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>Oct  4 22:39:17 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  4 22:39:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:39:49 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  4 22:40:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:40:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:40:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:40:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:40:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:40:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:26 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:26 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:26 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:26 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:26 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:26 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:37 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:37 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:37 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:37 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:37 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:37 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:42:56 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:56 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:56 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:56 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:56 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:56 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:56 node-1 multipathd: uevent trigger error
<43>Oct  4 22:42:57 node-1 apache2_error [Tue Oct 04 22:42:48.086824 2016] [mpm_event:notice] [pid 9766:tid 139742093170560] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  4 22:42:57 node-1 apache2_error [Tue Oct 04 22:42:48.086967 2016] [core:notice] [pid 9766:tid 139742093170560] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  4 22:42:57 node-1 apache2_error [Tue Oct 04 22:42:50.981980 2016] [mpm_event:notice] [pid 9766:tid 139742093170560] AH00491: caught SIGTERM, shutting down
<43>Oct  4 22:42:57 node-1 apache2_error [Tue Oct 04 22:42:52.066761 2016] [mpm_worker:notice] [pid 10117:tid 139843014260608] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  4 22:42:57 node-1 apache2_error [Tue Oct 04 22:42:52.066810 2016] [core:notice] [pid 10117:tid 139843014260608] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 22:42:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:42:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:43:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:43:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:43:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:43:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:43:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:43:03 node-1 multipathd: uevent trigger error
<27>Oct  4 22:43:03 node-1 multipathd: uevent trigger error
<43>Oct  4 22:44:07 node-1 apache2_error [Tue Oct 04 22:44:04.826690 2016] [mpm_worker:notice] [pid 10117:tid 139843014260608] AH00295: caught SIGTERM, shutting down
<43>Oct  4 22:44:07 node-1 apache2_error [Tue Oct 04 22:44:05.585179 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 22:44:07 node-1 apache2_error [Tue Oct 04 22:44:05.585214 2016] [core:notice] [pid 22810:tid 140113780041600] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  4 22:44:57 node-1 apache2_error [Tue Oct 04 22:44:49.401735 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 22:44:57 node-1 apache2_error [Tue Oct 04 22:44:49.597599 2016] [mpm_worker:warn] [pid 22810:tid 140113780041600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 22:44:57 node-1 apache2_error [Tue Oct 04 22:44:49.602824 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 22:44:57 node-1 apache2_error [Tue Oct 04 22:44:49.602864 2016] [core:notice] [pid 22810:tid 140113780041600] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 22:45:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:39 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:44 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:45:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:45:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:24 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:24 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:24 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:24 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:24 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:47 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:47 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:47 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:47 node-1 multipathd: uevent trigger error
<27>Oct  4 22:46:47 node-1 multipathd: uevent trigger error
<27>Oct  4 22:47:36 node-1 multipathd: uevent trigger error
<27>Oct  4 22:47:36 node-1 multipathd: uevent trigger error
<27>Oct  4 22:47:36 node-1 multipathd: uevent trigger error
<27>Oct  4 22:47:36 node-1 multipathd: uevent trigger error
<27>Oct  4 22:47:36 node-1 multipathd: uevent trigger error
<27>Oct  4 22:47:36 node-1 multipathd: uevent trigger error
<27>Oct  4 22:48:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:48:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:48:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:48:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:48:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:48:48 node-1 multipathd: uevent trigger error
<27>Oct  4 22:48:56 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:49:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:49:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:49:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:49:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:49:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:49:43 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:05 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:05 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:06 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:06 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:50:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:51:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:52:31 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:31 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:31 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:31 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:31 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:31 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:52 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:52 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:52 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:52 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:52 node-1 multipathd: uevent trigger error
<27>Oct  4 22:52:52 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:38 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:38 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:38 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:38 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:38 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:38 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:53:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:46 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct  4 22:54:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct  4 22:54:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct  4 22:54:54 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct  4 22:54:54 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct  4 22:54:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:55 node-1 multipathd: uevent trigger error
<27>Oct  4 22:54:59 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:55:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:08 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:40 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:40 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:40 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:40 node-1 multipathd: uevent trigger error
<27>Oct  4 22:55:40 node-1 multipathd: uevent trigger error
<27>Oct  4 22:57:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:57:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:57:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:57:59 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:00 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:00 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:58:11 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:12 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:12 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:16 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:28 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:33 node-1 multipathd: uevent trigger error
<27>Oct  4 22:58:34 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct  4 22:59:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:23 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:29 node-1 multipathd: uevent trigger error
<27>Oct  4 22:59:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:51 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:51 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:51 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:51 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:51 node-1 multipathd: uevent trigger error
<27>Oct  4 23:00:51 node-1 multipathd: uevent trigger error
<27>Oct  4 23:01:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 23:01:17 node-1 multipathd: uevent trigger error
<27>Oct  4 23:01:17 node-1 multipathd: uevent trigger error
<27>Oct  4 23:01:17 node-1 multipathd: uevent trigger error
<27>Oct  4 23:01:17 node-1 multipathd: uevent trigger error
<27>Oct  4 23:01:17 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:35 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:35 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:35 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:35 node-1 multipathd: uevent trigger error
<27>Oct  4 23:02:35 node-1 multipathd: uevent trigger error
<11>Oct  4 23:02:48 node-1 liberasurecode[83986]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:48 node-1 liberasurecode[83986]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:48 node-1 liberasurecode[83986]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:48 node-1 liberasurecode[83986]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:48 node-1 liberasurecode[84015]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:48 node-1 liberasurecode[84015]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:48 node-1 liberasurecode[84015]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:48 node-1 liberasurecode[84015]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:50 node-1 liberasurecode[84517]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:50 node-1 liberasurecode[84517]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:50 node-1 liberasurecode[84517]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:50 node-1 liberasurecode[84517]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85094]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85094]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85094]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85094]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85133]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85133]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85174]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85174]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85174]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85174]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85236]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85236]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85236]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85236]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85250]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85250]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85250]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85250]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85267]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85267]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85267]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85267]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85279]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85279]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85279]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:02:54 node-1 liberasurecode[85279]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:03 node-1 liberasurecode[85780]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:03 node-1 liberasurecode[85780]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:03 node-1 liberasurecode[85780]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:03 node-1 liberasurecode[85780]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  4 23:03:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:03:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:03:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:03:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:03:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  4 23:04:09 node-1 apache2_error [Tue Oct 04 23:03:59.430882 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 23:04:09 node-1 apache2_error [Tue Oct 04 23:03:59.816317 2016] [mpm_worker:warn] [pid 22810:tid 140113780041600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 23:04:09 node-1 apache2_error [Tue Oct 04 23:03:59.821236 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 23:04:09 node-1 apache2_error [Tue Oct 04 23:03:59.821257 2016] [core:notice] [pid 22810:tid 140113780041600] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  4 23:04:39 node-1 apache2_error [Tue Oct 04 23:04:36.840036 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 23:04:39 node-1 apache2_error [Tue Oct 04 23:04:37.032983 2016] [mpm_worker:warn] [pid 22810:tid 140113780041600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 23:04:39 node-1 apache2_error [Tue Oct 04 23:04:37.042045 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 23:04:39 node-1 apache2_error [Tue Oct 04 23:04:37.042095 2016] [core:notice] [pid 22810:tid 140113780041600] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 23:04:41 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:41 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:41 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:41 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:41 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-1 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-1 multipathd: uevent trigger error
<11>Oct  4 23:05:01 node-1 liberasurecode[104894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:05:01 node-1 liberasurecode[104894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:05:01 node-1 liberasurecode[104894]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:05:01 node-1 liberasurecode[104894]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  4 23:05:27 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:27 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:27 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:27 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:27 node-1 multipathd: uevent trigger error
<43>Oct  4 23:05:29 node-1 apache2_error [Tue Oct 04 23:05:23.229597 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 23:05:29 node-1 apache2_error [Tue Oct 04 23:05:23.618073 2016] [mpm_worker:warn] [pid 22810:tid 140113780041600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 23:05:29 node-1 apache2_error [Tue Oct 04 23:05:23.629819 2016] [mpm_worker:notice] [pid 22810:tid 140113780041600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 23:05:29 node-1 apache2_error [Tue Oct 04 23:05:23.629853 2016] [core:notice] [pid 22810:tid 140113780041600] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 23:05:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:33 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:58 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:58 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:58 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:58 node-1 multipathd: uevent trigger error
<27>Oct  4 23:05:58 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:19 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:26 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:26 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:26 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:26 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:26 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:32 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  4 23:06:42 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:42 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:42 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:42 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:42 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:46 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:46 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:46 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:47 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:47 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-1 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  4 23:07:20 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:20 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:20 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:20 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:20 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:47 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:47 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:47 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:47 node-1 multipathd: uevent trigger error
<27>Oct  4 23:07:47 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:01 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:01 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:01 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:01 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:01 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:08 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:08 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:08 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:08 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:08 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:12 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:24 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:29 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:34 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:34 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:34 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:34 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:34 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:34 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:39 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:43 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:43 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:43 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:43 node-1 multipathd: uevent trigger error
<27>Oct  4 23:08:43 node-1 multipathd: uevent trigger error
<11>Oct  4 23:10:02 node-1 liberasurecode[170615]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:10:02 node-1 liberasurecode[170615]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:10:02 node-1 liberasurecode[170615]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:10:02 node-1 liberasurecode[170615]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
