Oct  5 23:26:19 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8383" x-info="http://www.rsyslog.com"] start
Oct  5 23:26:19 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  5 23:26:19 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct  5 23:26:19 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct  5 23:26:19 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  5 23:26:19 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  5 23:26:19 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  5 23:26:19 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  5 23:26:19 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=15add32f-618a-4289-b256-8a6bc5fff7ed nomdmonddf nomdmonisw
Oct  5 23:26:19 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct  5 23:26:19 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct  5 23:26:19 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct  5 23:26:19 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct  5 23:26:19 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  5 23:26:19 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  5 23:26:19 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  5 23:26:19 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  5 23:26:19 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  5 23:26:19 node-1 kernel: [    0.000000] No AGP bridge found
Oct  5 23:26:19 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  5 23:26:19 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct  5 23:26:19 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  5 23:26:19 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct  5 23:26:19 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  5 23:26:19 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  5 23:26:19 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  5 23:26:19 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  5 23:26:19 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  5 23:26:19 node-1 kernel: [    0.000000]   2 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000]   3 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000]   4 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000]   5 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000]   6 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000]   7 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000]   8 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000]   9 disabled
Oct  5 23:26:19 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  5 23:26:19 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  5 23:26:19 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  5 23:26:19 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  5 23:26:19 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  5 23:26:19 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  5 23:26:19 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  5 23:26:19 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  5 23:26:19 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  5 23:26:19 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  5 23:26:19 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  5 23:26:19 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  5 23:26:19 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  5 23:26:19 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  5 23:26:19 node-1 kernel: [    0.000000] Zone ranges:
Oct  5 23:26:19 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] Movable zone start for each node
Oct  5 23:26:19 node-1 kernel: [    0.000000] Early memory node ranges
Oct  5 23:26:19 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct  5 23:26:19 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  5 23:26:19 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  5 23:26:19 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  5 23:26:19 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct  5 23:26:19 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct  5 23:26:19 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  5 23:26:19 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  5 23:26:19 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  5 23:26:19 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  5 23:26:19 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  5 23:26:19 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  5 23:26:19 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  5 23:26:19 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  5 23:26:19 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  5 23:26:19 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  5 23:26:19 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  5 23:26:19 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  5 23:26:19 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  5 23:26:19 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  5 23:26:19 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  5 23:26:19 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  5 23:26:19 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  5 23:26:19 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  5 23:26:19 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct  5 23:26:19 node-1 kernel: [    0.000000] Policy zone: Normal
Oct  5 23:26:19 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=15add32f-618a-4289-b256-8a6bc5fff7ed nomdmonddf nomdmonisw
Oct  5 23:26:19 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  5 23:26:19 node-1 kernel: [    0.000000] Checking aperture...
Oct  5 23:26:19 node-1 kernel: [    0.000000] No AGP bridge found
Oct  5 23:26:19 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  5 23:26:19 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  5 23:26:19 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct  5 23:26:19 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  5 23:26:19 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  5 23:26:19 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  5 23:26:19 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  5 23:26:19 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  5 23:26:19 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  5 23:26:19 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  5 23:26:19 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  5 23:26:19 node-1 kernel: [    0.000000] console [tty0] enabled
Oct  5 23:26:19 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  5 23:26:19 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  5 23:26:19 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  5 23:26:19 node-1 kernel: [    0.000000] hpet clockevent registered
Oct  5 23:26:19 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  5 23:26:19 node-1 kernel: [    0.004000] tsc: Detected 3492.212 MHz processor
Oct  5 23:26:19 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.42 BogoMIPS (lpj=13968848)
Oct  5 23:26:19 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  5 23:26:19 node-1 kernel: [    0.000047] Security Framework initialized
Oct  5 23:26:19 node-1 kernel: [    0.000064] AppArmor: AppArmor initialized
Oct  5 23:26:19 node-1 kernel: [    0.000066] Yama: becoming mindful.
Oct  5 23:26:19 node-1 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.006335] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.008258] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.008286] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.008576] Initializing cgroup subsys memory
Oct  5 23:26:19 node-1 kernel: [    0.008584] Initializing cgroup subsys devices
Oct  5 23:26:19 node-1 kernel: [    0.008586] Initializing cgroup subsys freezer
Oct  5 23:26:19 node-1 kernel: [    0.008588] Initializing cgroup subsys blkio
Oct  5 23:26:19 node-1 kernel: [    0.008589] Initializing cgroup subsys perf_event
Oct  5 23:26:19 node-1 kernel: [    0.008592] Initializing cgroup subsys hugetlb
Oct  5 23:26:19 node-1 kernel: [    0.008611] CPU: Physical Processor ID: 0
Oct  5 23:26:19 node-1 kernel: [    0.008613] CPU: Processor Core ID: 0
Oct  5 23:26:19 node-1 kernel: [    0.008616] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  5 23:26:19 node-1 kernel: [    0.008616] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  5 23:26:19 node-1 kernel: [    0.009311] mce: CPU supports 22 MCE banks
Oct  5 23:26:19 node-1 kernel: [    0.009338] CPU0: Thermal monitoring enabled (TM1)
Oct  5 23:26:19 node-1 kernel: [    0.009359] process: using mwait in idle threads
Oct  5 23:26:19 node-1 kernel: [    0.009362] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  5 23:26:19 node-1 kernel: [    0.009362] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  5 23:26:19 node-1 kernel: [    0.009362] tlb_flushall_shift: 6
Oct  5 23:26:19 node-1 kernel: [    0.009450] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  5 23:26:19 node-1 kernel: [    0.010176] ACPI: Core revision 20131115
Oct  5 23:26:19 node-1 kernel: [    0.022844] ACPI: All ACPI Tables successfully acquired
Oct  5 23:26:19 node-1 kernel: [    0.023006] ftrace: allocating 28614 entries in 112 pages
Oct  5 23:26:19 node-1 kernel: [    0.031710] dmar: Host address width 46
Oct  5 23:26:19 node-1 kernel: [    0.031712] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  5 23:26:19 node-1 kernel: [    0.031718] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  5 23:26:19 node-1 kernel: [    0.031720] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  5 23:26:19 node-1 kernel: [    0.031724] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  5 23:26:19 node-1 kernel: [    0.031725] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  5 23:26:19 node-1 kernel: [    0.031727] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  5 23:26:19 node-1 kernel: [    0.031728] dmar: ATSR flags: 0x0
Oct  5 23:26:19 node-1 kernel: [    0.031729] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  5 23:26:19 node-1 kernel: [    0.031730] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  5 23:26:19 node-1 kernel: [    0.031846] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  5 23:26:19 node-1 kernel: [    0.031847] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  5 23:26:19 node-1 kernel: [    0.031848] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  5 23:26:19 node-1 kernel: [    0.031849] HPET id 0 under DRHD base 0xc7ffc000
Oct  5 23:26:19 node-1 kernel: [    0.031850] Your BIOS is broken and requested that x2apic be disabled.
Oct  5 23:26:19 node-1 kernel: [    0.031850] This will slightly decrease performance.
Oct  5 23:26:19 node-1 kernel: [    0.031850] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  5 23:26:19 node-1 kernel: [    0.032283] Enabled IRQ remapping in xapic mode
Oct  5 23:26:19 node-1 kernel: [    0.032284] x2apic not enabled, IRQ remapping is in xapic mode
Oct  5 23:26:19 node-1 kernel: [    0.032288] Switched APIC routing to physical flat.
Oct  5 23:26:19 node-1 kernel: [    0.032907] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  5 23:26:19 node-1 kernel: [    0.072560] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  5 23:26:19 node-1 kernel: [    0.072565] TSC deadline timer enabled
Oct  5 23:26:19 node-1 kernel: [    0.072573] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  5 23:26:19 node-1 kernel: [    0.072578] ... version:                3
Oct  5 23:26:19 node-1 kernel: [    0.072579] ... bit width:              48
Oct  5 23:26:19 node-1 kernel: [    0.072580] ... generic registers:      4
Oct  5 23:26:19 node-1 kernel: [    0.072581] ... value mask:             0000ffffffffffff
Oct  5 23:26:19 node-1 kernel: [    0.072582] ... max period:             0000ffffffffffff
Oct  5 23:26:19 node-1 kernel: [    0.072583] ... fixed-purpose events:   3
Oct  5 23:26:19 node-1 kernel: [    0.072584] ... event mask:             000000070000000f
Oct  5 23:26:19 node-1 kernel: [    0.073959] x86: Booting SMP configuration:
Oct  5 23:26:19 node-1 kernel: [    0.088067] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  5 23:26:19 node-1 kernel: [    0.073961] .... node  #0, CPUs:        #1  #2  #3
Oct  5 23:26:19 node-1 kernel: [    0.115976] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  5 23:26:19 node-1 kernel: [    0.270123] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  5 23:26:19 node-1 kernel: [    0.325755] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  5 23:26:19 node-1 kernel: [    0.382615] x86: Booted up 2 nodes, 16 CPUs
Oct  5 23:26:19 node-1 kernel: [    0.382618] smpboot: Total of 16 processors activated (111763.61 BogoMIPS)
Oct  5 23:26:19 node-1 kernel: [    0.406820] devtmpfs: initialized
Oct  5 23:26:19 node-1 kernel: [    0.409312] EVM: security.selinux
Oct  5 23:26:19 node-1 kernel: [    0.409314] EVM: security.SMACK64
Oct  5 23:26:19 node-1 kernel: [    0.409315] EVM: security.ima
Oct  5 23:26:19 node-1 kernel: [    0.409316] EVM: security.capability
Oct  5 23:26:19 node-1 kernel: [    0.409368] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.410023] pinctrl core: initialized pinctrl subsystem
Oct  5 23:26:19 node-1 kernel: [    0.410087] regulator-dummy: no parameters
Oct  5 23:26:19 node-1 kernel: [    0.410119] RTC time: 23:25:39, date: 10/05/16
Oct  5 23:26:19 node-1 kernel: [    0.410153] NET: Registered protocol family 16
Oct  5 23:26:19 node-1 kernel: [    0.410237] cpuidle: using governor ladder
Oct  5 23:26:19 node-1 kernel: [    0.410238] cpuidle: using governor menu
Oct  5 23:26:19 node-1 kernel: [    0.410273] ACPI: bus type PCI registered
Oct  5 23:26:19 node-1 kernel: [    0.410275] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  5 23:26:19 node-1 kernel: [    0.410342] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  5 23:26:19 node-1 kernel: [    0.410344] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  5 23:26:19 node-1 kernel: [    0.424085] PCI: Using configuration type 1 for base access
Oct  5 23:26:19 node-1 kernel: [    0.425078] bio: create slab <bio-0> at 0
Oct  5 23:26:19 node-1 kernel: [    0.425355] ACPI: Added _OSI(Module Device)
Oct  5 23:26:19 node-1 kernel: [    0.425357] ACPI: Added _OSI(Processor Device)
Oct  5 23:26:19 node-1 kernel: [    0.425358] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  5 23:26:19 node-1 kernel: [    0.425359] ACPI: Added _OSI(Processor Aggregator Device)
Oct  5 23:26:19 node-1 kernel: [    0.438104] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  5 23:26:19 node-1 kernel: [    0.448840] ACPI: Interpreter enabled
Oct  5 23:26:19 node-1 kernel: [    0.448846] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  5 23:26:19 node-1 kernel: [    0.448850] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  5 23:26:19 node-1 kernel: [    0.448853] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  5 23:26:19 node-1 kernel: [    0.448860] ACPI: (supports S0 S4 S5)
Oct  5 23:26:19 node-1 kernel: [    0.448861] ACPI: Using IOAPIC for interrupt routing
Oct  5 23:26:19 node-1 kernel: [    0.448903] HEST: Table parsing has been initialized.
Oct  5 23:26:19 node-1 kernel: [    0.448905] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  5 23:26:19 node-1 kernel: [    0.449464] ACPI: No dock devices found.
Oct  5 23:26:19 node-1 kernel: [    0.461151] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  5 23:26:19 node-1 kernel: [    0.461156] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  5 23:26:19 node-1 kernel: [    0.461159] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  5 23:26:19 node-1 kernel: [    0.461186] PCI host bridge to bus 0000:ff
Oct  5 23:26:19 node-1 kernel: [    0.461188] pci_bus 0000:ff: root bus resource [bus ff]
Oct  5 23:26:19 node-1 kernel: [    0.461196] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  5 23:26:19 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  5 23:26:19 node-1 kernel: [    0.461234] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.461264] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461299] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461328] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.461357] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.461388] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461417] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461446] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461474] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461501] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461527] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461555] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461581] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461608] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461634] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461662] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461689] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461716] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.461744] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461769] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.461795] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461821] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461851] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.461887] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461918] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461948] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.461979] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462010] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462041] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462071] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462103] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462134] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462165] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462196] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462229] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462263] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462292] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462320] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462351] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462384] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462422] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462457] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462490] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462521] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462550] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462580] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462609] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462640] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462669] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462700] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462729] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462758] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462787] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462816] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462848] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462880] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.462942] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  5 23:26:19 node-1 kernel: [    0.462945] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  5 23:26:19 node-1 kernel: [    0.462948] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  5 23:26:19 node-1 kernel: [    0.462966] PCI host bridge to bus 0000:7f
Oct  5 23:26:19 node-1 kernel: [    0.462968] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  5 23:26:19 node-1 kernel: [    0.462973] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463000] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.463028] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463057] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463079] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.463103] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.463129] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463155] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463178] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463200] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463222] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463245] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463269] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463291] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463314] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463341] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463362] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463385] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463408] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.463432] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463457] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.463479] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463502] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463529] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  5 23:26:19 node-1 kernel: [    0.463563] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463590] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463617] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463643] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463668] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463694] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463720] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463749] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463774] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463801] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463829] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463856] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463885] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463911] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463938] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463967] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.463992] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464019] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464047] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464073] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464098] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464122] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464148] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464175] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464201] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464229] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464258] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464284] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464307] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464333] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464359] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464389] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.464416] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.465675] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  5 23:26:19 node-1 kernel: [    0.465679] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  5 23:26:19 node-1 kernel: [    0.466811] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  5 23:26:19 node-1 kernel: [    0.467326] PCI host bridge to bus 0000:00
Oct  5 23:26:19 node-1 kernel: [    0.467329] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  5 23:26:19 node-1 kernel: [    0.467330] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  5 23:26:19 node-1 kernel: [    0.467332] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  5 23:26:19 node-1 kernel: [    0.467333] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  5 23:26:19 node-1 kernel: [    0.467334] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  5 23:26:19 node-1 kernel: [    0.467336] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  5 23:26:19 node-1 kernel: [    0.467337] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  5 23:26:19 node-1 kernel: [    0.467343] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  5 23:26:19 node-1 kernel: [    0.467425] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.467456] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.467497] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  5 23:26:19 node-1 kernel: [    0.467517] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.467546] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.467586] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  5 23:26:19 node-1 kernel: [    0.467605] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.467634] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.467678] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  5 23:26:19 node-1 kernel: [    0.467693] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.467764] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.467841] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.467918] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  5 23:26:19 node-1 kernel: [    0.467923] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  5 23:26:19 node-1 kernel: [    0.468009] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  5 23:26:19 node-1 kernel: [    0.468156] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  5 23:26:19 node-1 kernel: [    0.468173] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  5 23:26:19 node-1 kernel: [    0.468252] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.468305] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  5 23:26:19 node-1 kernel: [    0.468329] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.468384] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.468428] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  5 23:26:19 node-1 kernel: [    0.468456] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.468513] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.468556] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  5 23:26:19 node-1 kernel: [    0.468581] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  5 23:26:19 node-1 kernel: [    0.468598] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  5 23:26:19 node-1 kernel: [    0.468677] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.468727] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  5 23:26:19 node-1 kernel: [    0.468753] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  5 23:26:19 node-1 kernel: [    0.469004] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  5 23:26:19 node-1 kernel: [    0.469009] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  5 23:26:19 node-1 kernel: [    0.469016] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.469021] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.469029] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  5 23:26:19 node-1 kernel: [    0.469059] pci 0000:01:00.0: supports D1 D2
Oct  5 23:26:19 node-1 kernel: [    0.478900] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  5 23:26:19 node-1 kernel: [    0.478907] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  5 23:26:19 node-1 kernel: [    0.478911] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  5 23:26:19 node-1 kernel: [    0.479079] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.479113] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  5 23:26:19 node-1 kernel: [    0.486899] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  5 23:26:19 node-1 kernel: [    0.486902] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.486904] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  5 23:26:19 node-1 kernel: [    0.486958] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.487026] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.487102] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.487148] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  5 23:26:19 node-1 kernel: [    0.487151] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.487153] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  5 23:26:19 node-1 kernel: [    0.487205] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.487343] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.487396] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  5 23:26:19 node-1 kernel: [    0.487399] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.487401] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.487450] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.487569] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.487609] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.487729] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.487765] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.487885] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.487920] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  5 23:26:19 node-1 kernel: [    0.488039] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  5 23:26:19 node-1 kernel: [    0.488079] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  5 23:26:19 node-1 kernel: [    0.488082] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.488084] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.488142] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  5 23:26:19 node-1 kernel: [    0.488206] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.488295] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.488335] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  5 23:26:19 node-1 kernel: [    0.488415] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  5 23:26:19 node-1 kernel: [    0.488531] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  5 23:26:19 node-1 kernel: [    0.488533] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.488535] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.488594] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  5 23:26:19 node-1 kernel: [    0.488653] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.488700] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.488920] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  5 23:26:19 node-1 kernel: [    0.488924] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  5 23:26:19 node-1 kernel: [    0.488991] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  5 23:26:19 node-1 kernel: [    0.489049] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.489096] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.489337] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  5 23:26:19 node-1 kernel: [    0.489340] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  5 23:26:19 node-1 kernel: [    0.489410] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  5 23:26:19 node-1 kernel: [    0.489474] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.489527] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  5 23:26:19 node-1 kernel: [    0.489747] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  5 23:26:19 node-1 kernel: [    0.489751] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  5 23:26:19 node-1 kernel: [    0.489927] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  5 23:26:19 node-1 kernel: [    0.489965] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  5 23:26:19 node-1 kernel: [    0.490041] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  5 23:26:19 node-1 kernel: [    0.490059] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  5 23:26:19 node-1 kernel: [    0.490073] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  5 23:26:19 node-1 kernel: [    0.490086] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  5 23:26:19 node-1 kernel: [    0.490136] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  5 23:26:19 node-1 kernel: [    0.494914] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  5 23:26:19 node-1 kernel: [    0.494923] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  5 23:26:19 node-1 kernel: [    0.494975] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  5 23:26:19 node-1 kernel: [    0.495598] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  5 23:26:19 node-1 kernel: [    0.495601] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  5 23:26:19 node-1 kernel: [    0.495726] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  5 23:26:19 node-1 kernel: [    0.495836] PCI host bridge to bus 0000:80
Oct  5 23:26:19 node-1 kernel: [    0.495838] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  5 23:26:19 node-1 kernel: [    0.495840] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  5 23:26:19 node-1 kernel: [    0.495841] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  5 23:26:19 node-1 kernel: [    0.495849] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.495913] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.495981] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  5 23:26:19 node-1 kernel: [    0.496044] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  5 23:26:19 node-1 kernel: [    0.496049] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  5 23:26:19 node-1 kernel: [    0.496123] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  5 23:26:19 node-1 kernel: [    0.496427] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  5 23:26:19 node-1 kernel: [    0.496459] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  5 23:26:19 node-1 kernel: [    0.496489] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  5 23:26:19 node-1 kernel: [    0.496518] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  5 23:26:19 node-1 kernel: [    0.496547] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  5 23:26:19 node-1 kernel: [    0.496578] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  5 23:26:19 node-1 kernel: [    0.496608] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  5 23:26:19 node-1 kernel: [    0.496637] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  5 23:26:19 node-1 kernel: [    0.496724] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  5 23:26:19 node-1 kernel: [    0.496728] ACPI: \_SB_.UNC1: notify handler is installed
Oct  5 23:26:19 node-1 kernel: [    0.496729] ACPI: \_SB_.UNC0: notify handler is installed
Oct  5 23:26:19 node-1 kernel: [    0.496745] ACPI: \_SB_.PCI0: notify handler is installed
Oct  5 23:26:19 node-1 kernel: [    0.496798] ACPI: \_SB_.PCI1: notify handler is installed
Oct  5 23:26:19 node-1 kernel: [    0.496877] Found 4 acpi root devices
Oct  5 23:26:19 node-1 kernel: [    0.496988] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  5 23:26:19 node-1 kernel: [    0.496990] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  5 23:26:19 node-1 kernel: [    0.496992] vgaarb: loaded
Oct  5 23:26:19 node-1 kernel: [    0.496993] vgaarb: bridge control possible 0000:0c:00.0
Oct  5 23:26:19 node-1 kernel: [    0.497116] SCSI subsystem initialized
Oct  5 23:26:19 node-1 kernel: [    0.497180] libata version 3.00 loaded.
Oct  5 23:26:19 node-1 kernel: [    0.497197] ACPI: bus type USB registered
Oct  5 23:26:19 node-1 kernel: [    0.497207] usbcore: registered new interface driver usbfs
Oct  5 23:26:19 node-1 kernel: [    0.497212] usbcore: registered new interface driver hub
Oct  5 23:26:19 node-1 kernel: [    0.497236] usbcore: registered new device driver usb
Oct  5 23:26:19 node-1 kernel: [    0.497406] PCI: Using ACPI for IRQ routing
Oct  5 23:26:19 node-1 kernel: [    0.501016] PCI: pci_cache_line_size set to 64 bytes
Oct  5 23:26:19 node-1 kernel: [    0.501234] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  5 23:26:19 node-1 kernel: [    0.501236] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct  5 23:26:19 node-1 kernel: [    0.501236] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  5 23:26:19 node-1 kernel: [    0.501302] NetLabel: Initializing
Oct  5 23:26:19 node-1 kernel: [    0.501304] NetLabel:  domain hash size = 128
Oct  5 23:26:19 node-1 kernel: [    0.501305] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  5 23:26:19 node-1 kernel: [    0.501314] NetLabel:  unlabeled traffic allowed by default
Oct  5 23:26:19 node-1 kernel: [    0.501372] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  5 23:26:19 node-1 kernel: [    0.501376] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  5 23:26:19 node-1 kernel: [    0.503434] Switched to clocksource hpet
Oct  5 23:26:19 node-1 kernel: [    0.507521] AppArmor: AppArmor Filesystem Enabled
Oct  5 23:26:19 node-1 kernel: [    0.507534] pnp: PnP ACPI init
Oct  5 23:26:19 node-1 kernel: [    0.507541] ACPI: bus type PNP registered
Oct  5 23:26:19 node-1 kernel: [    0.507652] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  5 23:26:19 node-1 kernel: [    0.507660] pnp 00:01: [dma 4]
Oct  5 23:26:19 node-1 kernel: [    0.507672] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  5 23:26:19 node-1 kernel: [    0.507698] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  5 23:26:19 node-1 kernel: [    0.507717] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  5 23:26:19 node-1 kernel: [    0.507735] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  5 23:26:19 node-1 kernel: [    0.507767] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  5 23:26:19 node-1 kernel: [    0.507821] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507823] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  5 23:26:19 node-1 kernel: [    0.507824] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507826] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507827] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507831] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507833] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  5 23:26:19 node-1 kernel: [    0.507835] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507836] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507838] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507839] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507841] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507842] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  5 23:26:19 node-1 kernel: [    0.507844] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  5 23:26:19 node-1 kernel: [    0.507928] pnp 00:07: [dma 0 disabled]
Oct  5 23:26:19 node-1 kernel: [    0.507957] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  5 23:26:19 node-1 kernel: [    0.508032] pnp 00:08: [dma 0 disabled]
Oct  5 23:26:19 node-1 kernel: [    0.508063] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  5 23:26:19 node-1 kernel: [    0.508115] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  5 23:26:19 node-1 kernel: [    0.508464] pnp: PnP ACPI: found 10 devices
Oct  5 23:26:19 node-1 kernel: [    0.508466] ACPI: bus type PNP unregistered
Oct  5 23:26:19 node-1 kernel: [    0.514723] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  5 23:26:19 node-1 kernel: [    0.514725] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  5 23:26:19 node-1 kernel: [    0.514728] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  5 23:26:19 node-1 kernel: [    0.514732] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  5 23:26:19 node-1 kernel: [    0.514734] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.514749] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.514781] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  5 23:26:19 node-1 kernel: [    0.514795] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  5 23:26:19 node-1 kernel: [    0.514824] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  5 23:26:19 node-1 kernel: [    0.514838] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  5 23:26:19 node-1 kernel: [    0.514867] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  5 23:26:19 node-1 kernel: [    0.514881] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  5 23:26:19 node-1 kernel: [    0.514910] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  5 23:26:19 node-1 kernel: [    0.514912] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.514927] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.514955] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  5 23:26:19 node-1 kernel: [    0.514957] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.514972] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515000] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  5 23:26:19 node-1 kernel: [    0.515002] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.515005] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515009] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  5 23:26:19 node-1 kernel: [    0.515011] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.515013] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515017] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  5 23:26:19 node-1 kernel: [    0.515021] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  5 23:26:19 node-1 kernel: [    0.515029] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  5 23:26:19 node-1 kernel: [    0.515033] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  5 23:26:19 node-1 kernel: [    0.515039] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  5 23:26:19 node-1 kernel: [    0.515040] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  5 23:26:19 node-1 kernel: [    0.515041] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  5 23:26:19 node-1 kernel: [    0.515042] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  5 23:26:19 node-1 kernel: [    0.515043] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  5 23:26:19 node-1 kernel: [    0.515044] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  5 23:26:19 node-1 kernel: [    0.515045] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  5 23:26:19 node-1 kernel: [    0.515046] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  5 23:26:19 node-1 kernel: [    0.515047] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.515047] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515048] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.515049] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515050] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.515051] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515052] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.515053] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515054] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  5 23:26:19 node-1 kernel: [    0.515054] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515055] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  5 23:26:19 node-1 kernel: [    0.515057] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  5 23:26:19 node-1 kernel: [    0.515057] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  5 23:26:19 node-1 kernel: [    0.515059] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  5 23:26:19 node-1 kernel: [    0.515060] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  5 23:26:19 node-1 kernel: [    0.515061] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  5 23:26:19 node-1 kernel: [    0.515103] NET: Registered protocol family 2
Oct  5 23:26:19 node-1 kernel: [    0.515358] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.515695] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.515840] TCP: Hash tables configured (established 262144 bind 65536)
Oct  5 23:26:19 node-1 kernel: [    0.515883] TCP: reno registered
Oct  5 23:26:19 node-1 kernel: [    0.515914] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.516010] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.516157] NET: Registered protocol family 1
Oct  5 23:26:19 node-1 kernel: [    0.551541] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  5 23:26:19 node-1 kernel: [    0.551555] PCI: CLS 64 bytes, default 64
Oct  5 23:26:19 node-1 kernel: [    0.551629] Trying to unpack rootfs image as initramfs...
Oct  5 23:26:19 node-1 kernel: [    0.770493] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct  5 23:26:19 node-1 kernel: [    0.770546] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  5 23:26:19 node-1 kernel: [    0.770549] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct  5 23:26:19 node-1 kernel: [    0.770963] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.770969] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.770974] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.770979] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.770988] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.770999] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771008] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771017] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771025] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771033] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771039] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771046] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771052] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771060] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771067] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771075] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  5 23:26:19 node-1 kernel: [    0.771153] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  5 23:26:19 node-1 kernel: [    0.771156] Scanning for low memory corruption every 60 seconds
Oct  5 23:26:19 node-1 kernel: [    0.771547] Initialise system trusted keyring
Oct  5 23:26:19 node-1 kernel: [    0.771599] audit: initializing netlink socket (disabled)
Oct  5 23:26:19 node-1 kernel: [    0.771614] type=2000 audit(1475709938.724:1): initialized
Oct  5 23:26:19 node-1 kernel: [    0.789363] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  5 23:26:19 node-1 kernel: [    0.790904] zbud: loaded
Oct  5 23:26:19 node-1 kernel: [    0.791029] VFS: Disk quotas dquot_6.5.2
Oct  5 23:26:19 node-1 kernel: [    0.791065] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  5 23:26:19 node-1 kernel: [    0.791449] fuse init (API version 7.22)
Oct  5 23:26:19 node-1 kernel: [    0.791510] msgmni has been set to 32768
Oct  5 23:26:19 node-1 kernel: [    0.791557] Key type big_key registered
Oct  5 23:26:19 node-1 kernel: [    0.792071] Key type asymmetric registered
Oct  5 23:26:19 node-1 kernel: [    0.792073] Asymmetric key parser 'x509' registered
Oct  5 23:26:19 node-1 kernel: [    0.792095] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  5 23:26:19 node-1 kernel: [    0.792164] io scheduler noop registered
Oct  5 23:26:19 node-1 kernel: [    0.792166] io scheduler deadline registered (default)
Oct  5 23:26:19 node-1 kernel: [    0.792185] io scheduler cfq registered
Oct  5 23:26:19 node-1 kernel: [    0.792699] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    0.792926] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    0.793044] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    0.793155] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    0.793270] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    0.793369] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    0.793819] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  5 23:26:19 node-1 kernel: [    0.793845] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  5 23:26:19 node-1 kernel: [    0.793861] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  5 23:26:19 node-1 kernel: [    0.793870] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793873] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793875] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  5 23:26:19 node-1 kernel: [    0.793880] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793882] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793883] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793884] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793886] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793887] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793889] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793890] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793891] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793893] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793894] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793896] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793898] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  5 23:26:19 node-1 kernel: [    0.793903] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793906] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  5 23:26:19 node-1 kernel: [    0.793920] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793924] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  5 23:26:19 node-1 kernel: [    0.793934] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793936] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  5 23:26:19 node-1 kernel: [    0.793939] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  5 23:26:19 node-1 kernel: [    0.793974] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  5 23:26:19 node-1 kernel: [    0.793980] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  5 23:26:19 node-1 kernel: [    0.793984] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  5 23:26:19 node-1 kernel: [    0.793994] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  5 23:26:19 node-1 kernel: [    0.794035] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  5 23:26:19 node-1 kernel: [    0.794036] vesafb: scrolling: redraw
Oct  5 23:26:19 node-1 kernel: [    0.794038] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  5 23:26:19 node-1 kernel: [    0.814828] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  5 23:26:19 node-1 kernel: [    0.823452] Console: switching to colour frame buffer device 80x30
Oct  5 23:26:19 node-1 kernel: [    0.832120] fb0: VESA VGA frame buffer device
Oct  5 23:26:19 node-1 kernel: [    0.832316] intel_idle: MWAIT substates: 0x2120
Oct  5 23:26:19 node-1 kernel: [    0.832317] intel_idle: v0.4 model 0x3F
Oct  5 23:26:19 node-1 kernel: [    0.832318] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  5 23:26:19 node-1 kernel: [    0.832551] ipmi message handler version 39.2
Oct  5 23:26:19 node-1 kernel: [    0.832831] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  5 23:26:19 node-1 kernel: [    0.833268] ACPI: AC Adapter [P111] (on-line)
Oct  5 23:26:19 node-1 kernel: [    0.838491] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  5 23:26:19 node-1 kernel: [    0.849473] ACPI: Power Button [PWRB]
Oct  5 23:26:19 node-1 kernel: [    0.855226] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  5 23:26:19 node-1 kernel: [    0.866848] ACPI: Power Button [PWRF]
Oct  5 23:26:19 node-1 kernel: [    0.892967] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  5 23:26:19 node-1 kernel: [    0.904612] pstore: Registered erst as persistent store backend
Oct  5 23:26:19 node-1 kernel: [    0.910798] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  5 23:26:19 node-1 kernel: [    0.922726] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  5 23:26:19 node-1 kernel: [    0.949458] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  5 23:26:19 node-1 kernel: [    0.982715] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  5 23:26:19 node-1 kernel: [    0.996749] Linux agpgart interface v0.103
Oct  5 23:26:19 node-1 kernel: [    1.004384] brd: module loaded
Oct  5 23:26:19 node-1 kernel: [    1.011427] loop: module loaded
Oct  5 23:26:19 node-1 kernel: [    1.018132] libphy: Fixed MDIO Bus: probed
Oct  5 23:26:19 node-1 kernel: [    1.024595] tun: Universal TUN/TAP device driver, 1.6
Oct  5 23:26:19 node-1 kernel: [    1.031120] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  5 23:26:19 node-1 kernel: [    1.037742] PPP generic driver version 2.4.2
Oct  5 23:26:19 node-1 kernel: [    1.044178] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  5 23:26:19 node-1 kernel: [    1.050626] ehci-pci: EHCI PCI platform driver
Oct  5 23:26:19 node-1 kernel: [    1.057151] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  5 23:26:19 node-1 kernel: [    1.063564] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  5 23:26:19 node-1 kernel: [    1.076109] ehci-pci 0000:00:1a.0: debug port 2
Oct  5 23:26:19 node-1 kernel: [    1.086315] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  5 23:26:19 node-1 kernel: [    1.086333] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  5 23:26:19 node-1 kernel: [    1.102930] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  5 23:26:19 node-1 kernel: [    1.109009] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  5 23:26:19 node-1 kernel: [    1.115187] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  5 23:26:19 node-1 kernel: [    1.127103] usb usb1: Product: EHCI Host Controller
Oct  5 23:26:19 node-1 kernel: [    1.133140] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  5 23:26:19 node-1 kernel: [    1.139194] usb usb1: SerialNumber: 0000:00:1a.0
Oct  5 23:26:19 node-1 kernel: [    1.145164] hub 1-0:1.0: USB hub found
Oct  5 23:26:19 node-1 kernel: [    1.150942] hub 1-0:1.0: 2 ports detected
Oct  5 23:26:19 node-1 kernel: [    1.156747] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  5 23:26:19 node-1 kernel: [    1.162320] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  5 23:26:19 node-1 kernel: [    1.173209] ehci-pci 0000:00:1d.0: debug port 2
Oct  5 23:26:19 node-1 kernel: [    1.182513] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  5 23:26:19 node-1 kernel: [    1.182515] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  5 23:26:19 node-1 kernel: [    1.198849] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  5 23:26:19 node-1 kernel: [    1.204053] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  5 23:26:19 node-1 kernel: [    1.209367] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  5 23:26:19 node-1 kernel: [    1.219946] usb usb2: Product: EHCI Host Controller
Oct  5 23:26:19 node-1 kernel: [    1.225421] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  5 23:26:19 node-1 kernel: [    1.230975] usb usb2: SerialNumber: 0000:00:1d.0
Oct  5 23:26:19 node-1 kernel: [    1.236496] hub 2-0:1.0: USB hub found
Oct  5 23:26:19 node-1 kernel: [    1.241851] hub 2-0:1.0: 2 ports detected
Oct  5 23:26:19 node-1 kernel: [    1.247166] ehci-platform: EHCI generic platform driver
Oct  5 23:26:19 node-1 kernel: [    1.252408] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  5 23:26:19 node-1 kernel: [    1.257733] ohci-pci: OHCI PCI platform driver
Oct  5 23:26:19 node-1 kernel: [    1.263034] ohci-platform: OHCI generic platform driver
Oct  5 23:26:19 node-1 kernel: [    1.268226] uhci_hcd: USB Universal Host Controller Interface driver
Oct  5 23:26:19 node-1 kernel: [    1.273574] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  5 23:26:19 node-1 kernel: [    1.466629] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  5 23:26:19 node-1 kernel: [    1.766432] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  5 23:26:19 node-1 kernel: [    1.782747] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  5 23:26:19 node-1 kernel: [    1.788415] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  5 23:26:19 node-1 kernel: [    1.794139] hub 1-1:1.0: USB hub found
Oct  5 23:26:19 node-1 kernel: [    1.799733] hub 1-1:1.0: 6 ports detected
Oct  5 23:26:19 node-1 kernel: [    1.914269] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  5 23:26:19 node-1 kernel: [    2.312755] i8042: No controller found
Oct  5 23:26:19 node-1 kernel: [    2.318284] mousedev: PS/2 mouse device common for all mice
Oct  5 23:26:19 node-1 kernel: [    2.324022] rtc_cmos 00:02: RTC can wake from S4
Oct  5 23:26:19 node-1 kernel: [    2.326724] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  5 23:26:19 node-1 kernel: [    2.326725] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  5 23:26:19 node-1 kernel: [    2.327370] hub 2-1:1.0: USB hub found
Oct  5 23:26:19 node-1 kernel: [    2.327605] hub 2-1:1.0: 8 ports detected
Oct  5 23:26:19 node-1 kernel: [    2.352324] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  5 23:26:19 node-1 kernel: [    2.358075] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  5 23:26:19 node-1 kernel: [    2.369372] device-mapper: uevent: version 1.0.3
Oct  5 23:26:19 node-1 kernel: [    2.375081] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  5 23:26:19 node-1 kernel: [    2.386465] ledtrig-cpu: registered to indicate activity on CPUs
Oct  5 23:26:19 node-1 kernel: [    2.392446] TCP: cubic registered
Oct  5 23:26:19 node-1 kernel: [    2.398312] NET: Registered protocol family 10
Oct  5 23:26:19 node-1 kernel: [    2.404370] NET: Registered protocol family 17
Oct  5 23:26:19 node-1 kernel: [    2.410146] Key type dns_resolver registered
Oct  5 23:26:19 node-1 kernel: [    2.416201] Loading compiled-in X.509 certificates
Oct  5 23:26:19 node-1 kernel: [    2.422407] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  5 23:26:19 node-1 kernel: [    2.434143] registered taskstats version 1
Oct  5 23:26:19 node-1 kernel: [    2.442293] Key type trusted registered
Oct  5 23:26:19 node-1 kernel: [    2.449902] Key type encrypted registered
Oct  5 23:26:19 node-1 kernel: [    2.455396] AppArmor: AppArmor sha1 policy hashing enabled
Oct  5 23:26:19 node-1 kernel: [    2.460909] IMA: No TPM chip found, activating TPM-bypass!
Oct  5 23:26:19 node-1 kernel: [    2.466985] regulator-dummy: disabling
Oct  5 23:26:19 node-1 kernel: [    2.472506]   Magic number: 4:216:453
Oct  5 23:26:19 node-1 kernel: [    2.478243] rtc_cmos 00:02: setting system clock to 2016-10-05 23:25:41 UTC (1475709941)
Oct  5 23:26:19 node-1 kernel: [    2.490772] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  5 23:26:19 node-1 kernel: [    2.496454] EDD information not available.
Oct  5 23:26:19 node-1 kernel: [    2.502087] PM: Hibernation image not present or could not be loaded.
Oct  5 23:26:19 node-1 kernel: [    2.502951] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  5 23:26:19 node-1 kernel: [    2.514300] Write protecting the kernel read-only data: 12288k
Oct  5 23:26:19 node-1 kernel: [    2.520630] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  5 23:26:19 node-1 kernel: [    2.533744] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  5 23:26:19 node-1 kernel: [    2.565201] device-mapper: multipath: version 1.6.0 loaded
Oct  5 23:26:19 node-1 kernel: [    2.573116] systemd-udevd[216]: starting version 204
Oct  5 23:26:19 node-1 kernel: [    2.593198] md: linear personality registered for level -1
Oct  5 23:26:19 node-1 kernel: [    2.605664] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  5 23:26:19 node-1 kernel: [    2.612870] md: multipath personality registered for level -4
Oct  5 23:26:19 node-1 kernel: [    2.620878] md: raid0 personality registered for level 0
Oct  5 23:26:19 node-1 kernel: [    2.629361] md: raid1 personality registered for level 1
Oct  5 23:26:19 node-1 kernel: [    2.641319] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  5 23:26:19 node-1 kernel: [    2.641320] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  5 23:26:19 node-1 kernel: [    2.641548] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  5 23:26:19 node-1 kernel: [    2.643728] megasas: FW now in Ready state
Oct  5 23:26:19 node-1 kernel: [    2.644036] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.644192] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.644360] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.644455] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.644631] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.644801] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.644924] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.645102] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.645179] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.645295] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.645430] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.645542] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.645895] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.645983] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.646107] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.646204] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.646907] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  5 23:26:19 node-1 kernel: [    2.687484] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct  5 23:26:19 node-1 kernel: [    2.700620] 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  5 23:26:19 node-1 kernel: [    2.701642] raid6: sse2x1   11028 MB/s
Oct  5 23:26:19 node-1 kernel: [    2.721070] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  5 23:26:19 node-1 kernel: [    2.727942] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.727946] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.727950] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.727954] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.727988] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.743305] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  5 23:26:19 node-1 kernel: [    2.749998] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  5 23:26:19 node-1 kernel: [    2.754704] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct  5 23:26:19 node-1 kernel: [    2.754713] 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  5 23:26:19 node-1 kernel: [    2.754742] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  5 23:26:19 node-1 kernel: [    2.754959] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.755119] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.755296] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.755424] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.755515] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.755616] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.755854] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  5 23:26:19 node-1 kernel: [    2.769745] raid6: sse2x2   12964 MB/s
Oct  5 23:26:19 node-1 kernel: [    2.815990] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  5 23:26:19 node-1 kernel: [    2.822475] usb 2-1.4: Manufacturer: Avocent
Oct  5 23:26:19 node-1 kernel: [    2.828850] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  5 23:26:19 node-1 kernel: [    2.837461] raid6: sse2x4    9560 MB/s
Oct  5 23:26:19 node-1 kernel: [    2.909409] raid6: avx2x1   14942 MB/s
Oct  5 23:26:19 node-1 kernel: [    2.981353] raid6: avx2x2   18876 MB/s
Oct  5 23:26:19 node-1 kernel: [    3.053276] raid6: avx2x4   21264 MB/s
Oct  5 23:26:19 node-1 kernel: [    3.059267] raid6: using algorithm avx2x4 (21264 MB/s)
Oct  5 23:26:19 node-1 kernel: [    3.065302] raid6: using avx2x2 recovery algorithm
Oct  5 23:26:19 node-1 kernel: [    3.071209] Switched to clocksource tsc
Oct  5 23:26:19 node-1 kernel: [    3.071483] megasas:IOC Init cmd success
Oct  5 23:26:19 node-1 kernel: [    3.082295] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct  5 23:26:19 node-1 kernel: [    3.082298] 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  5 23:26:19 node-1 kernel: [    3.082299] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  5 23:26:19 node-1 kernel: [    3.084362] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.084402] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.084444] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.084484] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.084566] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.097291] megasas: INIT adapter done
Oct  5 23:26:19 node-1 kernel: [    3.099045] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct  5 23:26:19 node-1 kernel: [    3.099046] 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  5 23:26:19 node-1 kernel: [    3.099047] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  5 23:26:19 node-1 kernel: [    3.099111] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.099149] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.099186] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.099221] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.099300] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  5 23:26:19 node-1 kernel: [    3.150582] xor: automatically using best checksumming function:
Oct  5 23:26:19 node-1 kernel: [    3.150596] hidraw: raw HID events driver (C) Jiri Kosina
Oct  5 23:26:19 node-1 kernel: [    3.165197] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  5 23:26:19 node-1 kernel: [    3.165520] scsi0 : LSI SAS based MegaRAID driver
Oct  5 23:26:19 node-1 kernel: [    3.172662] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  5 23:26:19 node-1 kernel: [    3.183604] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  5 23:26:19 node-1 kernel: [    3.187735] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  5 23:26:19 node-1 kernel: [    3.187742] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  5 23:26:19 node-1 kernel: [    3.188078] sd 0:2:0:0: [sda] Write Protect is off
Oct  5 23:26:19 node-1 kernel: [    3.188079] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  5 23:26:19 node-1 kernel: [    3.188142] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  5 23:26:19 node-1 kernel: [    3.189236]    avx       : 35662.000 MB/sec
Oct  5 23:26:19 node-1 kernel: [    3.219306]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct  5 23:26:19 node-1 kernel: [    3.220913] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  5 23:26:19 node-1 kernel: [    3.240486] usbcore: registered new interface driver usbhid
Oct  5 23:26:19 node-1 kernel: [    3.240486] usbhid: USB HID core driver
Oct  5 23:26:19 node-1 kernel: [    3.263713] async_tx: api initialized (async)
Oct  5 23:26:19 node-1 kernel: [    3.288788] 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  5 23:26:19 node-1 kernel: [    3.301583] 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  5 23:26:19 node-1 kernel: [    3.314654] 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  5 23:26:19 node-1 kernel: [    3.327697] 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  5 23:26:19 node-1 kernel: [    3.341082] 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  5 23:26:19 node-1 kernel: [    3.341111] md: raid6 personality registered for level 6
Oct  5 23:26:19 node-1 kernel: [    3.341111] md: raid5 personality registered for level 5
Oct  5 23:26:19 node-1 kernel: [    3.341111] md: raid4 personality registered for level 4
Oct  5 23:26:19 node-1 kernel: [    3.374807] 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  5 23:26:19 node-1 kernel: [    3.389357] md: raid10 personality registered for level 10
Oct  5 23:26:19 node-1 kernel: [    3.402015] random: lvm urandom read with 31 bits of entropy available
Oct  5 23:26:19 node-1 kernel: [    3.451960] multipathd (369): /proc/369/oom_adj is deprecated, please use /proc/369/oom_score_adj instead.
Oct  5 23:26:19 node-1 kernel: [    3.573765] bio: create slab <bio-1> at 1
Oct  5 23:26:19 node-1 kernel: [    4.330348] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  5 23:26:19 node-1 kernel: [    4.963659] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  5 23:26:19 node-1 kernel: [    5.000638] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  5 23:26:19 node-1 kernel: [    5.059664] random: nonblocking pool is initialized
Oct  5 23:26:19 node-1 kernel: [    5.129347] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  5 23:26:19 node-1 kernel: [    5.165285] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  5 23:26:19 node-1 kernel: [    5.277528] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  5 23:26:19 node-1 kernel: [    5.471432] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  5 23:26:19 node-1 kernel: [    5.514529] XFS (dm-0): Mounting Filesystem
Oct  5 23:26:19 node-1 kernel: [    5.734784] XFS (dm-0): Ending clean mount
Oct  5 23:26:19 node-1 kernel: [    5.790170] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  5 23:26:19 node-1 kernel: [    5.840642] XFS (dm-1): Mounting Filesystem
Oct  5 23:26:19 node-1 kernel: [    6.062577] XFS (dm-1): Ending clean mount
Oct  5 23:26:19 node-1 kernel: [    7.916280] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  5 23:26:19 node-1 kernel: [    7.930111] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  5 23:26:19 node-1 kernel: [    8.074388] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  5 23:26:19 node-1 kernel: [    8.074392] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  5 23:26:19 node-1 kernel: [    8.074397] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  5 23:26:19 node-1 kernel: [    8.074401] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  5 23:26:19 node-1 kernel: [    8.110938] systemd-udevd[776]: starting version 204
Oct  5 23:26:19 node-1 kernel: [    8.298596] power_meter ACPI000D:00: Found ACPI power meter.
Oct  5 23:26:19 node-1 kernel: [    8.298613] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  5 23:26:19 node-1 kernel: [    8.305311] IPMI System Interface driver.
Oct  5 23:26:19 node-1 kernel: [    8.305372] ipmi_si: probing via ACPI
Oct  5 23:26:19 node-1 kernel: [    8.305389] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  5 23:26:19 node-1 kernel: [    8.305390] ipmi_si: Adding ACPI-specified kcs state machine
Oct  5 23:26:19 node-1 kernel: [    8.305408] ipmi_si: probing via SMBIOS
Oct  5 23:26:19 node-1 kernel: [    8.305409] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  5 23:26:19 node-1 kernel: [    8.305409] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  5 23:26:19 node-1 kernel: [    8.305411] ipmi_si: probing via SPMI
Oct  5 23:26:19 node-1 kernel: [    8.305411] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  5 23:26:19 node-1 kernel: [    8.305412] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  5 23:26:19 node-1 kernel: [    8.305413] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  5 23:26:19 node-1 kernel: [    8.324975] wmi: Mapper loaded
Oct  5 23:26:19 node-1 kernel: [    8.342933] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  5 23:26:19 node-1 kernel: [    8.343820] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  5 23:26:19 node-1 kernel: [    8.343825] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  5 23:26:19 node-1 kernel: [    8.343827] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  5 23:26:19 node-1 kernel: [    8.343829] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  5 23:26:19 node-1 kernel: [    8.343876] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  5 23:26:19 node-1 kernel: [    8.397225] systemd-udevd[823]: renamed network interface eth0 to enp6s0
Oct  5 23:26:19 node-1 kernel: [    8.421102] systemd-udevd[796]: renamed network interface eth1 to enp7s0
Oct  5 23:26:19 node-1 kernel: [    8.448152] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  5 23:26:19 node-1 kernel: [    8.448162] ipmi_si 00:09: IPMI kcs interface initialized
Oct  5 23:26:19 node-1 kernel: [    8.481081] systemd-udevd[794]: renamed network interface eth2 to enp8s0
Oct  5 23:26:19 node-1 kernel: [    8.509030] systemd-udevd[797]: renamed network interface eth3 to enp9s0
Oct  5 23:26:19 node-1 kernel: [    8.805949] type=1400 audit(1475709947.827:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.806102] type=1400 audit(1475709947.827:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1050 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.806228] type=1400 audit(1475709947.827:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1050 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.807010] type=1400 audit(1475709947.827:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1051 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.807163] type=1400 audit(1475709947.827:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1051 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.807284] type=1400 audit(1475709947.827:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1051 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.814980] type=1400 audit(1475709947.835:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.815132] type=1400 audit(1475709947.835:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1052 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.815261] type=1400 audit(1475709947.835:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1052 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    8.852018] type=1400 audit(1475709947.871:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Oct  5 23:26:19 node-1 kernel: [    9.299341] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  5 23:26:19 node-1 kernel: [    9.300085] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  5 23:26:19 node-1 kernel: [    9.474055] enic 0000:06:00.0 enp6s0: Link UP
Oct  5 23:26:19 node-1 kernel: [    9.475073] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  5 23:26:19 node-1 kernel: [    9.475082] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  5 23:26:19 node-1 kernel: [   18.755998] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  5 23:26:20 node-1 failsafe: Failsafe of 120 seconds reached.
Oct  5 23:26:21 node-1 kernel: [   41.919488] init: failsafe main process (8410) killed by TERM signal
Oct  5 23:26:21 node-1 dbus[8439]: [system] AppArmor D-Bus mediation is enabled
Oct  5 23:26:21 node-1 kernel: [   42.322295] audit_printk_skb: 30 callbacks suppressed
Oct  5 23:26:21 node-1 kernel: [   42.322298] type=1400 audit(1475709981.411:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8537 comm="apparmor_parser"
Oct  5 23:26:21 node-1 kernel: [   42.322303] type=1400 audit(1475709981.411:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Oct  5 23:26:21 node-1 kernel: [   42.322306] type=1400 audit(1475709981.411:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Oct  5 23:26:21 node-1 kernel: [   42.322523] type=1400 audit(1475709981.411:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Oct  5 23:26:21 node-1 kernel: [   42.322525] type=1400 audit(1475709981.411:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Oct  5 23:26:21 node-1 kernel: [   42.322638] type=1400 audit(1475709981.411:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Oct  5 23:26:21 node-1 kernel: [   42.327222] type=1400 audit(1475709981.415:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8538 comm="apparmor_parser"
Oct  5 23:26:21 node-1 kernel: [   42.387136] type=1400 audit(1475709981.475:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8540 comm="apparmor_parser"
Oct  5 23:26:21 node-1 cron[8569]: (CRON) INFO (pidfile fd = 3)
Oct  5 23:26:21 node-1 anacron[8605]: Anacron 2.3 started on 2016-10-05
Oct  5 23:26:21 node-1 cron[8606]: (CRON) STARTUP (fork ok)
Oct  5 23:26:21 node-1 anacron[8605]: Will run job `cron.daily' in 5 min.
Oct  5 23:26:21 node-1 anacron[8605]: Will run job `cron.weekly' in 10 min.
Oct  5 23:26:21 node-1 anacron[8605]: Will run job `cron.monthly' in 15 min.
Oct  5 23:26:21 node-1 anacron[8605]: Jobs will be executed sequentially
Oct  5 23:26:21 node-1 cron[8606]: (CRON) INFO (Running @reboot jobs)
Oct  5 23:26:21 node-1 multipathd: path checkers start up
Oct  5 23:26:22 node-1 postfix/master[8747]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  5 23:26:25 node-1 puppet-agent[8931]: Reopening log files
Oct  5 23:26:26 node-1 puppet-agent[8931]: Could not request certificate: Connection refused - connect(2)
Oct  5 23:26:34 node-1 puppet-user[9010]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  5 23:26:34 node-1 puppet-user[9010]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct  5 23:26:35 node-1 puppet-user[9010]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  5 23:26:35 node-1 puppet-user[9010]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  5 23:26:36 node-1 puppet-user[9010]: Finished catalog run in 1.01 seconds
Oct  5 23:26:37 node-1 multipathd: uevent trigger error
Oct  5 23:26:37 node-1 puppet-user[9440]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  5 23:26:37 node-1 puppet-user[9440]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct  5 23:26:37 node-1 puppet-user[9440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  5 23:26:37 node-1 puppet-user[9440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  5 23:26:37 node-1 puppet-user[9440]: (/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  5 23:26:37 node-1 puppet-user[9440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  5 23:26:37 node-1 puppet-user[9440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  5 23:26:37 node-1 puppet-user[9440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  5 23:26:37 node-1 puppet-user[9440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  5 23:26:37 node-1 puppet-user[9440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  5 23:26:37 node-1 puppet-user[9440]: Finished catalog run in 0.05 seconds
Oct  5 23:26:39 node-1 puppet-user[9925]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  5 23:26:39 node-1 puppet-user[9925]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct  5 23:26:39 node-1 puppet-user[9925]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  5 23:26:39 node-1 puppet-user[9925]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  5 23:26:39 node-1 puppet-user[9925]: Finished catalog run in 0.03 seconds
Oct  5 23:26:40 node-1 puppet-user[10494]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  5 23:26:40 node-1 puppet-user[10494]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  5 23:26:41 node-1 puppet-user[10494]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  5 23:26:41 node-1 puppet-user[10494]: Finished catalog run in 0.05 seconds
Oct  5 23:26:42 node-1 puppet-user[10941]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  5 23:26:42 node-1 puppet-user[10941]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Oct  5 23:26:42 node-1 puppet-user[10941]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  5 23:26:42 node-1 puppet-user[10941]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Oct  5 23:26:42 node-1 puppet-user[10941]: Finished catalog run in 0.42 seconds
Oct  5 23:26:44 node-1 puppet-user[11420]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  5 23:26:44 node-1 puppet-user[11420]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Oct  5 23:26:44 node-1 puppet-user[11420]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Oct  5 23:26:44 node-1 puppet-user[11420]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  5 23:26:44 node-1 puppet-user[11420]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  5 23:26:44 node-1 puppet-user[11420]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  5 23:26:44 node-1 puppet-user[11420]: Finished catalog run in 0.21 seconds
Oct  5 23:26:46 node-1 puppet-user[11893]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  5 23:26:46 node-1 puppet-user[11893]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Oct  5 23:26:46 node-1 puppet-user[11893]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  5 23:26:46 node-1 kernel: [   67.192190] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  5 23:26:46 node-1 kernel: [   67.192240] 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  5 23:26:46 node-1 puppet-user[11893]: (/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  5 23:26:46 node-1 puppet-user[11893]: Finished catalog run in 0.05 seconds
Oct  5 23:26:47 node-1 puppet-user[12355]: (Scope(Class[main])) MODULAR: sync_time
Oct  5 23:26:48 node-1 puppet-user[12355]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  5 23:26:48 node-1 ntpdate[12771]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Oct  5 23:26:54 node-1 ntpdate[12771]: adjust time server 10.20.0.2 offset -0.013235 sec
Oct  5 23:26:54 node-1 puppet-user[12355]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  5 23:26:54 node-1 puppet-user[12355]: Finished catalog run in 6.18 seconds
Oct  5 23:26:59 node-1 puppet-user[13153]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  5 23:26:59 node-1 puppet-user[13153]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct  5 23:27:00 node-1 puppet-user[13153]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  5 23:27:00 node-1 puppet-user[13153]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs"]'
Oct  5 23:27:00 node-1 puppet-user[13153]: Finished catalog run in 0.06 seconds
Oct  5 23:27:01 node-1 puppet-user[13607]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  5 23:27:01 node-1 CRON[14024]: (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  5 23:27:01 node-1 puppet-user[13607]: Compiled catalog for node-1.domain.tld in environment production in 0.47 seconds
Oct  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/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  5 23:27:02 node-1 puppet-user[13607]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  5 23:27:02 node-1 puppet-user[13607]: Finished catalog run in 0.84 seconds
Oct  5 23:27:03 node-1 kernel: [   84.056075] init: plymouth-upstart-bridge main process ended, respawning
Oct  5 23:27:03 node-1 puppet-agent[8931]: Could not run: SIGTERM
Oct  5 23:27:03 node-1 kernel: [   84.321427] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  5 23:27:03 node-1 ec2: 
Oct  5 23:27:03 node-1 ec2: #############################################################
Oct  5 23:27:03 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  5 23:27:03 node-1 ec2: 1024 23:fd:21:68:c6:4a:7f:39:42:21:51:00:81:5e:90:20  root@node-1.domain.tld (DSA)
Oct  5 23:27:03 node-1 ec2: 256 53:89:d0:59:69:fc:ee:a7:84:41:4b:65:d6:27:d1:36  root@node-1.domain.tld (ECDSA)
Oct  5 23:27:03 node-1 ec2: 256 4b:78:e0:15:05:cb:2e:3e:39:9d:38:a0:eb:f9:34:15  root@node-1.domain.tld (ED25519)
Oct  5 23:27:03 node-1 ec2: 2048 65:5f:6e:60:d1:f3:fc:0d:37:3a:af:69:59:3f:51:e8  root@node-1.domain.tld (RSA)
Oct  5 23:27:03 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  5 23:27:03 node-1 ec2: #############################################################
Oct  5 23:27:04 node-1 puppet-user[14280]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  5 23:27:04 node-1 puppet-user[14280]: Compiled catalog for node-1.domain.tld in environment production in 0.12 seconds
Oct  5 23:27:07 node-1 puppet-user[14280]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  5 23:27:13 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  5 23:27:13 node-1 nailgun-agent: D, [2016-10-05T23:27:01.826287 #14027] DEBUG -- : Sleep for 12 seconds before sending request
Oct  5 23:27:13 node-1 nailgun-agent: I, [2016-10-05T23:27:13.841681 #14027]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  5 23:27:14 node-1 nailgun-agent: D, [2016-10-05T23:27:14.262968 #14027] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.509339 #14027] DEBUG -- : Trying to find block devices
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.509628 #14027] DEBUG -- : Found block device: sda
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.509722 #14027] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.509773 #14027] DEBUG -- : Trying to get list of physical devices
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.510165 #14027] DEBUG -- : Getting udev properties for device: sda
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.513973 #14027] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Oct  5 23:27:26 node-1 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75796", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.514036 #14027] DEBUG -- : Trying to find out if device sda is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.514131 #14027] DEBUG -- : Device sda removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.514218 #14027] DEBUG -- : Device sda seems to be appropriate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.515116 #14027] DEBUG -- : Getting udev properties for device: dm-0
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.518576 #14027] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-D5W0BAtefSUgfQ8C5Mvahgf3q1tEECggwZj1gTwznQ7lPM2xeHtu1jssKzUsadpf /dev/disk/by-uuid/2e3af0a2-52ae-4f1e-b0e2-515170ec23af /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-D5W0BAtefSUgfQ8C5Mvahgf3q1tEECggwZj1gTwznQ7lPM2xeHtu1jssKzUsadpf", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2e3af0a2-52ae-4f1e-b0e2-515170ec23af", "ID_FS_UUID_ENC"=>"2e3af0a2-52ae-4f1e-b0e2-515170ec23af", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28850", "nomdmonddf"=>"1", "nom
Oct  5 23:27:26 node-1 nailgun-agent: dmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.518653 #14027] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.518737 #14027] DEBUG -- : Device dm-0 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.518774 #14027] DEBUG -- : Device dm-0 seems to be appropriate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.518812 #14027] DEBUG -- : Getting udev properties for device: dm-1
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.521726 #14027] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-GycYyjZyBOt5RvzMekC77lAwyhOb8ZfhWQS3yN72a9pZDpYLt92GGQnu9XUQ3okq /dev/disk/by-uuid/8fcb8ec2-355c-449b-b479-b5af1fa270c0 /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-GycYyjZyBOt5RvzMekC77lAwyhOb8ZfhWQS3yN72a9pZDpYLt92GGQnu9XUQ3okq", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8fcb8ec2-355c-449b-b479-b5af1fa270c0", "ID_FS_UUID_ENC"=>"8fcb8ec2-355c-449b-b479-b5af1fa270c0", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4
Oct  5 23:27:26 node-1 nailgun-agent: 5051", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.521805 #14027] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.521893 #14027] DEBUG -- : Device dm-1 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.521933 #14027] DEBUG -- : Device dm-1 seems to be appropriate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.521977 #14027] DEBUG -- : Getting udev properties for device: dm-2
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.525220 #14027] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-ZVuHvcnQ3fo3M6pEuRSQDq4lYmSRxyrwgeNUPBerUZGtAAopm63ulT1KuwIovbju /dev/disk/by-uuid/a668b396-dc88-44d3-818b-2e1322b47362 /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-ZVuHvcnQ3fo3M6pEuRSQDq4lYmSRxyrwgeNUPBerUZGtAAopm63ulT1KuwIovbju", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a668b396-dc88-44d3-818b-2e1322b47362", "ID_FS_UUID_ENC"=>"a668b396-dc88-44d3-818b-2e1322b47362", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50300", "nomdmon
Oct  5 23:27:26 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.525294 #14027] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.525381 #14027] DEBUG -- : Device dm-2 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.525419 #14027] DEBUG -- : Device dm-2 seems to be appropriate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.525483 #14027] DEBUG -- : Getting udev properties for device: dm-3
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.528159 #14027] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-6P9edg4IR6rfDYnuThThkvhEdl7m4xlgiAsU1ifdG1IHGwcMyUx018SFQwivxrBp /dev/disk/by-uuid/3302dc16-b26d-4714-9a6c-827a5a5449e5 /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-6P9edg4IR6rfDYnuThThkvhEdl7m4xlgiAsU1ifdG1IHGwcMyUx018SFQwivxrBp", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3302dc16-b26d-4714-9a6c-827a5a5449e5", "ID_FS_UUID_ENC"=>"3302dc16-b26d-4714-9a6c-827a5a5449e5", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60867", "nomdmonddf"=>"1",
Oct  5 23:27:26 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.528227 #14027] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.528288 #14027] DEBUG -- : Device dm-3 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.528313 #14027] DEBUG -- : Device dm-3 seems to be appropriate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.528340 #14027] DEBUG -- : Getting udev properties for device: dm-4
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.531246 #14027] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-3c2jn3JqX5orcqasgfox7VyY0wqN6U4O2Ih5JWZBARye5jSFpmcR07C0pc1LbvVc /dev/disk/by-uuid/15add32f-618a-4289-b256-8a6bc5fff7ed /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-3c2jn3JqX5orcqasgfox7VyY0wqN6U4O2Ih5JWZBARye5jSFpmcR07C0pc1LbvVc", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"15add32f-618a-4289-b256-8a6bc5fff7ed", "ID_FS_UUID_ENC"=>"15add32f-618a-4289-b256-8a6bc5fff7ed", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64355", "nomdmonddf"=>"1", "nom
Oct  5 23:27:26 node-1 nailgun-agent: dmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.531295 #14027] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.531355 #14027] DEBUG -- : Device dm-4 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.531402 #14027] DEBUG -- : Device dm-4 seems to be appropriate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.531429 #14027] DEBUG -- : Getting udev properties for device: dm-5
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.534372 #14027] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-3c2jn3JqX5orcqasgfox7VyY0wqN6U4OyVhNFsjsH4mQVHSlBEC5fHjD3u9dTihS /dev/disk/by-uuid/55085798-69c7-4439-a8c2-0f38eb38b475 /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-3c2jn3JqX5orcqasgfox7VyY0wqN6U4OyVhNFsjsH4mQVHSlBEC5fHjD3u9dTihS", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"55085798-69c7-4439-a8c2-0f38eb38b475", "ID_FS_UUID_ENC"=>"55085798-69c7-4439-a8c2-0f38eb38b475", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64930", "nomdmonddf"=>"1", "nomdmonisw
Oct  5 23:27:26 node-1 nailgun-agent: "=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.534424 #14027] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.534487 #14027] DEBUG -- : Device dm-5 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.534513 #14027] DEBUG -- : Device dm-5 seems to be appropriate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.534541 #14027] DEBUG -- : Getting udev properties for device: ram0
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.537529 #14027] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11558", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.537562 #14027] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.537630 #14027] DEBUG -- : Device ram0 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.537690 #14027] DEBUG -- : Getting udev properties for device: ram1
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.540146 #14027] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12563", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.540179 #14027] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.540243 #14027] DEBUG -- : Device ram1 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.540270 #14027] DEBUG -- : Getting udev properties for device: ram2
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.543273 #14027] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13042", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.543342 #14027] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.543457 #14027] DEBUG -- : Device ram2 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.543511 #14027] DEBUG -- : Getting udev properties for device: ram3
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.546347 #14027] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13214", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.546415 #14027] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.546509 #14027] DEBUG -- : Device ram3 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.546580 #14027] DEBUG -- : Getting udev properties for device: ram4
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.549523 #14027] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13280", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.549561 #14027] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.549620 #14027] DEBUG -- : Device ram4 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.549658 #14027] DEBUG -- : Getting udev properties for device: ram5
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.552135 #14027] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13481", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.552198 #14027] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.552337 #14027] DEBUG -- : Device ram5 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.552383 #14027] DEBUG -- : Getting udev properties for device: ram6
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.554754 #14027] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13555", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.554782 #14027] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.554844 #14027] DEBUG -- : Device ram6 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.554896 #14027] DEBUG -- : Getting udev properties for device: ram7
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.557565 #14027] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13635", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.557643 #14027] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.557735 #14027] DEBUG -- : Device ram7 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.557779 #14027] DEBUG -- : Getting udev properties for device: ram8
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.560653 #14027] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13730", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.560693 #14027] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.560732 #14027] DEBUG -- : Device ram8 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.560770 #14027] DEBUG -- : Getting udev properties for device: ram9
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.563341 #14027] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13801", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.563369 #14027] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.563430 #14027] DEBUG -- : Device ram9 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.563504 #14027] DEBUG -- : Getting udev properties for device: loop0
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.566392 #14027] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8914", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.566420 #14027] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.566497 #14027] DEBUG -- : Device loop0 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.566540 #14027] DEBUG -- : Getting udev properties for device: loop1
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.569043 #14027] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9098", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.569080 #14027] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.569120 #14027] DEBUG -- : Device loop1 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.569153 #14027] DEBUG -- : Getting udev properties for device: loop2
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.571624 #14027] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9249", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.571658 #14027] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.571711 #14027] DEBUG -- : Device loop2 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.571745 #14027] DEBUG -- : Getting udev properties for device: loop3
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.580760 #14027] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9505", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.580797 #14027] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.580854 #14027] DEBUG -- : Device loop3 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.580880 #14027] DEBUG -- : Getting udev properties for device: loop4
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.583215 #14027] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9933", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.583242 #14027] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.583306 #14027] DEBUG -- : Device loop4 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.583341 #14027] DEBUG -- : Getting udev properties for device: loop5
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.585372 #14027] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10192", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.585400 #14027] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.585451 #14027] DEBUG -- : Device loop5 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.585474 #14027] DEBUG -- : Getting udev properties for device: loop6
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.587876 #14027] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10648", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.587937 #14027] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.587979 #14027] DEBUG -- : Device loop6 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.588002 #14027] DEBUG -- : Getting udev properties for device: loop7
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.591054 #14027] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11277", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.591099 #14027] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.591243 #14027] DEBUG -- : Device loop7 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.591279 #14027] DEBUG -- : Getting udev properties for device: ram10
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.594590 #14027] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12625", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.594625 #14027] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.594667 #14027] DEBUG -- : Device ram10 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.594722 #14027] DEBUG -- : Getting udev properties for device: ram11
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.598391 #14027] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12675", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.598421 #14027] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.598460 #14027] DEBUG -- : Device ram11 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.598485 #14027] DEBUG -- : Getting udev properties for device: ram12
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.601355 #14027] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12757", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.601385 #14027] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.601428 #14027] DEBUG -- : Device ram12 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.601453 #14027] DEBUG -- : Getting udev properties for device: ram13
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.604576 #14027] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12803", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.604643 #14027] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.604747 #14027] DEBUG -- : Device ram13 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.604796 #14027] DEBUG -- : Getting udev properties for device: ram14
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.607263 #14027] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12860", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.607331 #14027] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.607430 #14027] DEBUG -- : Device ram14 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.607482 #14027] DEBUG -- : Getting udev properties for device: ram15
Oct  5 23:27:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610224 #14027] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12981", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610255 #14027] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610303 #14027] DEBUG -- : Device ram15 removable parameter: "0"
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610346 #14027] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610362 #14027] DEBUG -- : Block device seems to be physical data storage: sda
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610403 #14027] DEBUG -- : Found block device: dm-0
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610421 #14027] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610437 #14027] DEBUG -- : Found block device: dm-1
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610450 #14027] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610459 #14027] DEBUG -- : Found block device: dm-2
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610510 #14027] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610546 #14027] DEBUG -- : Found block device: dm-3
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610574 #14027] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610597 #14027] DEBUG -- : Found block device: dm-4
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610625 #14027] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610649 #14027] DEBUG -- : Found block device: dm-5
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610677 #14027] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610700 #14027] DEBUG -- : Found block device: ram0
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610730 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610754 #14027] DEBUG -- : Found block device: ram1
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610831 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610856 #14027] DEBUG -- : Found block device: ram2
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610881 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610904 #14027] DEBUG -- : Found block device: ram3
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610929 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610953 #14027] DEBUG -- : Found block device: ram4
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.610979 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611001 #14027] DEBUG -- : Found block device: ram5
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611027 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611052 #14027] DEBUG -- : Found block device: ram6
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611129 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611153 #14027] DEBUG -- : Found block device: ram7
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611179 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611202 #14027] DEBUG -- : Found block device: ram8
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611228 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611250 #14027] DEBUG -- : Found block device: ram9
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611277 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611300 #14027] DEBUG -- : Found block device: loop0
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611328 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611352 #14027] DEBUG -- : Found block device: loop1
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611428 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611454 #14027] DEBUG -- : Found block device: loop2
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611481 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611503 #14027] DEBUG -- : Found block device: loop3
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611529 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611553 #14027] DEBUG -- : Found block device: loop4
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611579 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611601 #14027] DEBUG -- : Found block device: loop5
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611626 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611650 #14027] DEBUG -- : Found block device: loop6
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611676 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611751 #14027] DEBUG -- : Found block device: loop7
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611778 #14027] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611802 #14027] DEBUG -- : Found block device: ram10
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611827 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611850 #14027] DEBUG -- : Found block device: ram11
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611877 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611899 #14027] DEBUG -- : Found block device: ram12
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611925 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611948 #14027] DEBUG -- : Found block device: ram13
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.611973 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.612054 #14027] DEBUG -- : Found block device: ram14
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.612079 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.612103 #14027] DEBUG -- : Found block device: ram15
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.612128 #14027] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.612198 #14027] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct  5 23:27:26 node-1 nailgun-agent: D, [2016-10-05T23:27:26.797965 #14027] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct  5 23:27:26 node-1 nailgun-agent: I, [2016-10-05T23:27:26.798374 #14027]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct  5 23:27:35 node-1 puppet-user[14280]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  5 23:27:35 node-1 puppet-user[14280]: Finished catalog run in 30.43 seconds
Oct  5 23:27:37 node-1 puppet-user[17092]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  5 23:27:37 node-1 puppet-user[17092]: Compiled catalog for node-1.domain.tld in environment production in 0.62 seconds
Oct  5 23:27:38 node-1 puppet-user[17092]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  5 23:27:38 node-1 puppet-user[17092]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  5 23:27:38 node-1 puppet-user[17092]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  5 23:27:38 node-1 puppet-user[17092]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  5 23:27:38 node-1 puppet-user[17092]: Finished catalog run in 0.08 seconds
Oct  5 23:27:39 node-1 puppet-user[17551]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  5 23:27:40 node-1 puppet-user[17551]: Compiled catalog for node-1.domain.tld in environment production in 0.83 seconds
Oct  5 23:27:41 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  5 23:27:41 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  5 23:27:41 node-1 crontab[17988]: (root) LIST (root)
Oct  5 23:27:41 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  5 23:27:41 node-1 crontab[17989]: (root) REPLACE (root)
Oct  5 23:27:42 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:43 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  5 23:27:43 node-1 puppet-user[17551]: (/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  5 23:27:44 node-1 puppet-user[17551]: (/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  5 23:27:44 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  5 23:27:44 node-1 puppet-user[17551]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  5 23:27:44 node-1 puppet-user[17551]: (/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  5 23:27:44 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8383" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  5 23:27:44 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  5 23:27:46 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:46 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:46 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:46 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:46 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:27:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:28:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:28:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:28:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:28:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:28:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:28:51 node-1 ntpdate[28585]: no servers can be used, exiting
<27>Oct  5 23:28:51 node-1 ntpdate[28940]: no servers can be used, exiting
<27>Oct  5 23:29:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:23 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:37 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:37 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:37 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:37 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:37 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:40 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:40 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:40 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:40 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:40 node-1 multipathd: uevent trigger error
<27>Oct  5 23:29:40 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:34 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:34 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:34 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:34 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:34 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:42 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:42 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:42 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:42 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:42 node-1 multipathd: uevent trigger error
<27>Oct  5 23:30:45 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  5 23:30:45 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  5 23:30:51 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  5 23:30:51 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  5 23:30:56 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  5 23:31:02 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  5 23:31:02 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  5 23:31:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:11 node-1 ntpdate[14461]: the NTP socket is in use, exiting
<27>Oct  5 23:31:11 node-1 ntpdate[14513]: the NTP socket is in use, exiting
<27>Oct  5 23:31:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:22 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:22 node-1 multipathd: uevent trigger error
<129>Oct  5 23:31:24 node-1 haproxy[17211]: 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  5 23:31:24 node-1 haproxy[17211]: Backup Server mysqld/node-2 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  5 23:31:25 node-1 haproxy[17215]: Backup Server mysqld/node-3 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  5 23:31:25 node-1 haproxy[17215]: proxy mysqld has no server available!
<27>Oct  5 23:31:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:30 node-1 multipathd: uevent trigger error
<129>Oct  5 23:31:33 node-1 haproxy[19861]: 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  5 23:31:33 node-1 haproxy[19861]: Backup Server mysqld/node-2 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  5 23:31:34 node-1 haproxy[19865]: Backup Server mysqld/node-3 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  5 23:31:34 node-1 haproxy[19865]: proxy mysqld has no server available!
<129>Oct  5 23:31:34 node-1 haproxy[19865]: 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  5 23:31:34 node-1 haproxy[19865]: Server object-storage/node-2 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  5 23:31:35 node-1 haproxy[19865]: Server object-storage/node-3 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  5 23:31:35 node-1 haproxy[19865]: proxy object-storage has no server available!
<27>Oct  5 23:31:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:36 node-1 multipathd: uevent trigger error
<129>Oct  5 23:31:38 node-1 haproxy[21280]: 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  5 23:31:38 node-1 haproxy[21280]: Server neutron/node-2 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  5 23:31:39 node-1 haproxy[21284]: Server neutron/node-3 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  5 23:31:39 node-1 haproxy[21284]: proxy neutron has no server available!
<129>Oct  5 23:31:39 node-1 haproxy[21284]: 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  5 23:31:39 node-1 haproxy[21284]: Backup Server mysqld/node-2 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  5 23:31:39 node-1 haproxy[21284]: Backup Server mysqld/node-3 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  5 23:31:39 node-1 haproxy[21284]: proxy mysqld has no server available!
<129>Oct  5 23:31:40 node-1 haproxy[21284]: 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  5 23:31:40 node-1 haproxy[21284]: Server object-storage/node-2 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  5 23:31:40 node-1 haproxy[21284]: Server object-storage/node-3 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  5 23:31:40 node-1 haproxy[21284]: proxy object-storage has no server available!
<27>Oct  5 23:31:41 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:41 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:41 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:41 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:41 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:41 node-1 multipathd: uevent trigger error
<129>Oct  5 23:31:44 node-1 haproxy[22716]: 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  5 23:31:44 node-1 haproxy[22716]: Server keystone-1/node-2 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  5 23:31:44 node-1 haproxy[22716]: Server keystone-1/node-3 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  5 23:31:44 node-1 haproxy[22716]: proxy keystone-1 has no server available!
<129>Oct  5 23:31:44 node-1 haproxy[22716]: 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  5 23:31:44 node-1 haproxy[22716]: Server keystone-2/node-2 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  5 23:31:44 node-1 haproxy[22716]: Server keystone-2/node-3 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  5 23:31:44 node-1 haproxy[22716]: proxy keystone-2 has no server available!
<129>Oct  5 23:31:45 node-1 haproxy[22720]: 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  5 23:31:45 node-1 haproxy[22720]: Server neutron/node-2 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  5 23:31:45 node-1 haproxy[22720]: Server neutron/node-3 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  5 23:31:45 node-1 haproxy[22720]: proxy neutron has no server available!
<129>Oct  5 23:31:45 node-1 haproxy[22720]: 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  5 23:31:45 node-1 haproxy[22720]: Backup Server mysqld/node-2 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  5 23:31:45 node-1 haproxy[22720]: Backup Server mysqld/node-3 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  5 23:31:45 node-1 haproxy[22720]: proxy mysqld has no server available!
<129>Oct  5 23:31:45 node-1 haproxy[22720]: 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  5 23:31:46 node-1 haproxy[22720]: Server object-storage/node-2 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  5 23:31:46 node-1 haproxy[22720]: Server object-storage/node-3 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  5 23:31:46 node-1 haproxy[22720]: proxy object-storage has no server available!
<27>Oct  5 23:31:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:47 node-1 multipathd: uevent trigger error
<129>Oct  5 23:31:49 node-1 haproxy[24089]: 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  5 23:31:49 node-1 haproxy[24089]: Server keystone-1/node-2 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  5 23:31:49 node-1 haproxy[24089]: Server keystone-1/node-3 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  5 23:31:49 node-1 haproxy[24089]: proxy keystone-1 has no server available!
<129>Oct  5 23:31:50 node-1 haproxy[24093]: 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  5 23:31:50 node-1 haproxy[24093]: Server keystone-2/node-2 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  5 23:31:50 node-1 haproxy[24093]: Server keystone-2/node-3 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  5 23:31:50 node-1 haproxy[24093]: proxy keystone-2 has no server available!
<129>Oct  5 23:31:50 node-1 haproxy[24093]: 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  5 23:31:50 node-1 haproxy[24093]: Server neutron/node-2 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  5 23:31:50 node-1 haproxy[24093]: Server neutron/node-3 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  5 23:31:50 node-1 haproxy[24093]: proxy neutron has no server available!
<129>Oct  5 23:31:50 node-1 haproxy[24093]: 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  5 23:31:50 node-1 haproxy[24093]: Backup Server mysqld/node-2 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  5 23:31:50 node-1 haproxy[24093]: Backup Server mysqld/node-3 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  5 23:31:50 node-1 haproxy[24093]: proxy mysqld has no server available!
<129>Oct  5 23:31:51 node-1 haproxy[24093]: 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  5 23:31:51 node-1 haproxy[24093]: Server object-storage/node-2 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  5 23:31:51 node-1 haproxy[24093]: Server object-storage/node-3 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  5 23:31:51 node-1 haproxy[24093]: proxy object-storage has no server available!
<129>Oct  5 23:31:51 node-1 haproxy[24093]: 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  5 23:31:51 node-1 haproxy[24093]: Server aodh/node-2 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  5 23:31:51 node-1 haproxy[24093]: Server aodh/node-3 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  5 23:31:51 node-1 haproxy[24093]: proxy aodh has no server available!
<27>Oct  5 23:31:53 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:53 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:53 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:53 node-1 multipathd: uevent trigger error
<129>Oct  5 23:31:55 node-1 haproxy[25517]: 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  5 23:31:55 node-1 haproxy[25517]: Server keystone-1/node-2 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  5 23:31:55 node-1 haproxy[25517]: Server keystone-1/node-3 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  5 23:31:55 node-1 haproxy[25517]: proxy keystone-1 has no server available!
<129>Oct  5 23:31:55 node-1 haproxy[25517]: 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  5 23:31:55 node-1 haproxy[25517]: Server keystone-2/node-2 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  5 23:31:55 node-1 haproxy[25517]: Server keystone-2/node-3 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  5 23:31:55 node-1 haproxy[25517]: proxy keystone-2 has no server available!
<129>Oct  5 23:31:55 node-1 haproxy[25517]: 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  5 23:31:55 node-1 haproxy[25517]: Server neutron/node-2 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  5 23:31:56 node-1 haproxy[25523]: Server neutron/node-3 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  5 23:31:56 node-1 haproxy[25523]: proxy neutron has no server available!
<129>Oct  5 23:31:56 node-1 haproxy[25523]: 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  5 23:31:56 node-1 haproxy[25523]: Backup Server mysqld/node-2 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  5 23:31:56 node-1 haproxy[25523]: Backup Server mysqld/node-3 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  5 23:31:56 node-1 haproxy[25523]: proxy mysqld has no server available!
<129>Oct  5 23:31:56 node-1 haproxy[25523]: 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  5 23:31:56 node-1 haproxy[25523]: Server object-storage/node-2 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  5 23:31:56 node-1 haproxy[25523]: Server object-storage/node-3 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  5 23:31:56 node-1 haproxy[25523]: proxy object-storage has no server available!
<129>Oct  5 23:31:56 node-1 haproxy[25523]: 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  5 23:31:56 node-1 haproxy[25523]: Server aodh/node-2 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  5 23:31:56 node-1 haproxy[25523]: Server aodh/node-3 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  5 23:31:56 node-1 haproxy[25523]: proxy aodh has no server available!
<129>Oct  5 23:31:56 node-1 haproxy[25523]: 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  5 23:31:57 node-1 haproxy[25523]: Server ceilometer/node-2 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  5 23:31:57 node-1 haproxy[25523]: Server ceilometer/node-3 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  5 23:31:57 node-1 haproxy[25523]: proxy ceilometer has no server available!
<27>Oct  5 23:31:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:31:58 node-1 multipathd: uevent trigger error
<129>Oct  5 23:32:00 node-1 haproxy[26945]: 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  5 23:32:00 node-1 haproxy[26945]: Server keystone-1/node-2 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  5 23:32:01 node-1 haproxy[26949]: Server keystone-1/node-3 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  5 23:32:01 node-1 haproxy[26949]: proxy keystone-1 has no server available!
<129>Oct  5 23:32:01 node-1 haproxy[26949]: 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  5 23:32:01 node-1 haproxy[26949]: Server keystone-2/node-2 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  5 23:32:01 node-1 haproxy[26949]: Server keystone-2/node-3 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  5 23:32:01 node-1 haproxy[26949]: proxy keystone-2 has no server available!
<129>Oct  5 23:32:01 node-1 haproxy[26949]: 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  5 23:32:01 node-1 haproxy[26949]: Server neutron/node-2 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  5 23:32:01 node-1 haproxy[26949]: Server neutron/node-3 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  5 23:32:01 node-1 haproxy[26949]: proxy neutron has no server available!
<129>Oct  5 23:32:01 node-1 haproxy[26949]: 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  5 23:32:01 node-1 haproxy[26949]: Backup Server mysqld/node-2 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  5 23:32:01 node-1 haproxy[26949]: Backup Server mysqld/node-3 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  5 23:32:01 node-1 haproxy[26949]: proxy mysqld has no server available!
<129>Oct  5 23:32:01 node-1 haproxy[26949]: 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  5 23:32:02 node-1 haproxy[26949]: Server object-storage/node-2 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  5 23:32:02 node-1 haproxy[26949]: Server object-storage/node-3 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  5 23:32:02 node-1 haproxy[26949]: proxy object-storage has no server available!
<129>Oct  5 23:32:02 node-1 haproxy[26949]: 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  5 23:32:02 node-1 haproxy[26949]: Server aodh/node-2 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  5 23:32:02 node-1 haproxy[26949]: Server aodh/node-3 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  5 23:32:02 node-1 haproxy[26949]: proxy aodh has no server available!
<129>Oct  5 23:32:02 node-1 haproxy[26949]: 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  5 23:32:02 node-1 haproxy[26949]: Server ceilometer/node-2 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  5 23:32:02 node-1 haproxy[26949]: Server ceilometer/node-3 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  5 23:32:02 node-1 haproxy[26949]: proxy ceilometer has no server available!
<27>Oct  5 23:32:04 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:04 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:04 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:04 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:04 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:04 node-1 multipathd: uevent trigger error
<129>Oct  5 23:32:06 node-1 haproxy[28382]: 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  5 23:32:06 node-1 haproxy[28382]: Server horizon/node-2 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  5 23:32:06 node-1 haproxy[28382]: 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  5 23:32:06 node-1 haproxy[28382]: Server keystone-1/node-2 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  5 23:32:06 node-1 haproxy[28382]: Server keystone-1/node-3 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  5 23:32:06 node-1 haproxy[28382]: proxy keystone-1 has no server available!
<129>Oct  5 23:32:06 node-1 haproxy[28382]: 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  5 23:32:06 node-1 haproxy[28382]: Server keystone-2/node-2 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  5 23:32:07 node-1 haproxy[28386]: Server keystone-2/node-3 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  5 23:32:07 node-1 haproxy[28386]: proxy keystone-2 has no server available!
<129>Oct  5 23:32:07 node-1 haproxy[28386]: 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  5 23:32:07 node-1 haproxy[28386]: Server neutron/node-2 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  5 23:32:07 node-1 haproxy[28386]: Server neutron/node-3 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  5 23:32:07 node-1 haproxy[28386]: proxy neutron has no server available!
<129>Oct  5 23:32:07 node-1 haproxy[28386]: 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  5 23:32:07 node-1 haproxy[28386]: Backup Server mysqld/node-2 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  5 23:32:07 node-1 haproxy[28386]: Backup Server mysqld/node-3 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  5 23:32:07 node-1 haproxy[28386]: proxy mysqld has no server available!
<129>Oct  5 23:32:07 node-1 haproxy[28386]: 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  5 23:32:07 node-1 haproxy[28386]: Server object-storage/node-2 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  5 23:32:07 node-1 haproxy[28386]: Server object-storage/node-3 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  5 23:32:07 node-1 haproxy[28386]: proxy object-storage has no server available!
<129>Oct  5 23:32:07 node-1 haproxy[28386]: 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  5 23:32:07 node-1 haproxy[28386]: Server aodh/node-2 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  5 23:32:08 node-1 haproxy[28386]: Server aodh/node-3 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  5 23:32:08 node-1 haproxy[28386]: proxy aodh has no server available!
<129>Oct  5 23:32:08 node-1 haproxy[28386]: 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  5 23:32:08 node-1 haproxy[28386]: Server ceilometer/node-2 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  5 23:32:08 node-1 haproxy[28386]: Server ceilometer/node-3 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  5 23:32:08 node-1 haproxy[28386]: proxy ceilometer has no server available!
<27>Oct  5 23:32:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:09 node-1 multipathd: uevent trigger error
<129>Oct  5 23:32:12 node-1 haproxy[29822]: 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  5 23:32:12 node-1 haproxy[29822]: Server horizon/node-2 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  5 23:32:12 node-1 haproxy[29822]: 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  5 23:32:12 node-1 haproxy[29822]: Server keystone-1/node-2 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  5 23:32:12 node-1 haproxy[29822]: Server keystone-1/node-3 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  5 23:32:12 node-1 haproxy[29822]: proxy keystone-1 has no server available!
<129>Oct  5 23:32:12 node-1 haproxy[29822]: 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  5 23:32:12 node-1 haproxy[29822]: Server keystone-2/node-2 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  5 23:32:12 node-1 haproxy[29822]: Server keystone-2/node-3 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  5 23:32:12 node-1 haproxy[29822]: proxy keystone-2 has no server available!
<129>Oct  5 23:32:12 node-1 haproxy[29822]: 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  5 23:32:12 node-1 haproxy[29822]: Server glance-api/node-2 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  5 23:32:12 node-1 haproxy[29822]: Server glance-api/node-3 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  5 23:32:12 node-1 haproxy[29822]: proxy glance-api has no server available!
<129>Oct  5 23:32:12 node-1 haproxy[29822]: 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  5 23:32:13 node-1 haproxy[29826]: Server glance-glare/node-2 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  5 23:32:13 node-1 haproxy[29826]: Server glance-glare/node-3 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  5 23:32:13 node-1 haproxy[29826]: proxy glance-glare has no server available!
<129>Oct  5 23:32:13 node-1 haproxy[29826]: 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  5 23:32:13 node-1 haproxy[29826]: Server neutron/node-2 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  5 23:32:13 node-1 haproxy[29826]: Server neutron/node-3 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  5 23:32:13 node-1 haproxy[29826]: proxy neutron has no server available!
<129>Oct  5 23:32:13 node-1 haproxy[29826]: 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  5 23:32:13 node-1 haproxy[29826]: Server glance-registry/node-2 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  5 23:32:13 node-1 haproxy[29826]: Server glance-registry/node-3 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  5 23:32:13 node-1 haproxy[29826]: proxy glance-registry has no server available!
<129>Oct  5 23:32:13 node-1 haproxy[29826]: 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  5 23:32:13 node-1 haproxy[29826]: Backup Server mysqld/node-2 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  5 23:32:13 node-1 haproxy[29826]: Backup Server mysqld/node-3 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  5 23:32:13 node-1 haproxy[29826]: proxy mysqld has no server available!
<129>Oct  5 23:32:13 node-1 haproxy[29826]: 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  5 23:32:13 node-1 haproxy[29826]: Server object-storage/node-2 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  5 23:32:13 node-1 haproxy[29826]: Server object-storage/node-3 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  5 23:32:13 node-1 haproxy[29826]: proxy object-storage has no server available!
<129>Oct  5 23:32:13 node-1 haproxy[29826]: 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  5 23:32:13 node-1 haproxy[29826]: Server aodh/node-2 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  5 23:32:14 node-1 haproxy[29826]: Server aodh/node-3 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  5 23:32:14 node-1 haproxy[29826]: proxy aodh has no server available!
<129>Oct  5 23:32:14 node-1 haproxy[29826]: 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  5 23:32:14 node-1 haproxy[29826]: Server ceilometer/node-2 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  5 23:32:14 node-1 haproxy[29826]: Server ceilometer/node-3 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  5 23:32:14 node-1 haproxy[29826]: proxy ceilometer has no server available!
<27>Oct  5 23:32:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:15 node-1 multipathd: uevent trigger error
<129>Oct  5 23:32:18 node-1 haproxy[31291]: 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  5 23:32:18 node-1 haproxy[31291]: Server horizon/node-2 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  5 23:32:18 node-1 haproxy[31291]: 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  5 23:32:18 node-1 haproxy[31291]: Server keystone-1/node-2 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  5 23:32:18 node-1 haproxy[31291]: Server keystone-1/node-3 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  5 23:32:18 node-1 haproxy[31291]: proxy keystone-1 has no server available!
<129>Oct  5 23:32:18 node-1 haproxy[31291]: 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  5 23:32:18 node-1 haproxy[31291]: Server keystone-2/node-2 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  5 23:32:18 node-1 haproxy[31291]: Server keystone-2/node-3 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  5 23:32:18 node-1 haproxy[31291]: proxy keystone-2 has no server available!
<129>Oct  5 23:32:18 node-1 haproxy[31291]: 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  5 23:32:18 node-1 haproxy[31291]: Server nova-api/node-2 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  5 23:32:18 node-1 haproxy[31291]: Server nova-api/node-3 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  5 23:32:18 node-1 haproxy[31291]: proxy nova-api has no server available!
<129>Oct  5 23:32:18 node-1 haproxy[31291]: 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  5 23:32:18 node-1 haproxy[31291]: Server nova-metadata-api/node-2 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  5 23:32:18 node-1 haproxy[31291]: Server nova-metadata-api/node-3 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  5 23:32:18 node-1 haproxy[31291]: proxy nova-metadata-api has no server available!
<129>Oct  5 23:32:18 node-1 haproxy[31291]: 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  5 23:32:19 node-1 haproxy[31295]: Server glance-api/node-2 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  5 23:32:19 node-1 haproxy[31295]: Server glance-api/node-3 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  5 23:32:19 node-1 haproxy[31295]: proxy glance-api has no server available!
<129>Oct  5 23:32:19 node-1 haproxy[31295]: 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  5 23:32:19 node-1 haproxy[31295]: Server glance-glare/node-2 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  5 23:32:19 node-1 haproxy[31295]: Server glance-glare/node-3 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  5 23:32:19 node-1 haproxy[31295]: proxy glance-glare has no server available!
<129>Oct  5 23:32:19 node-1 haproxy[31295]: 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  5 23:32:19 node-1 haproxy[31295]: Server neutron/node-2 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  5 23:32:19 node-1 haproxy[31295]: Server neutron/node-3 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  5 23:32:19 node-1 haproxy[31295]: proxy neutron has no server available!
<129>Oct  5 23:32:19 node-1 haproxy[31295]: 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  5 23:32:19 node-1 haproxy[31295]: Server glance-registry/node-2 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  5 23:32:19 node-1 haproxy[31295]: Server glance-registry/node-3 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  5 23:32:19 node-1 haproxy[31295]: proxy glance-registry has no server available!
<129>Oct  5 23:32:19 node-1 haproxy[31295]: 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  5 23:32:19 node-1 haproxy[31295]: Backup Server mysqld/node-2 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  5 23:32:19 node-1 haproxy[31295]: Backup Server mysqld/node-3 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  5 23:32:19 node-1 haproxy[31295]: proxy mysqld has no server available!
<129>Oct  5 23:32:19 node-1 haproxy[31295]: 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  5 23:32:19 node-1 haproxy[31295]: Server object-storage/node-2 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  5 23:32:19 node-1 haproxy[31295]: Server object-storage/node-3 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  5 23:32:19 node-1 haproxy[31295]: proxy object-storage has no server available!
<129>Oct  5 23:32:19 node-1 haproxy[31295]: 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  5 23:32:19 node-1 haproxy[31295]: Server aodh/node-2 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  5 23:32:19 node-1 haproxy[31295]: Server aodh/node-3 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  5 23:32:19 node-1 haproxy[31295]: proxy aodh has no server available!
<129>Oct  5 23:32:19 node-1 haproxy[31295]: 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  5 23:32:20 node-1 haproxy[31295]: Server ceilometer/node-2 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  5 23:32:20 node-1 haproxy[31295]: Server ceilometer/node-3 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  5 23:32:20 node-1 haproxy[31295]: proxy ceilometer has no server available!
<129>Oct  5 23:32:20 node-1 haproxy[31295]: 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  5 23:32:20 node-1 haproxy[31295]: Server nova-novncproxy/node-2 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  5 23:32:20 node-1 haproxy[31295]: Server nova-novncproxy/node-3 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  5 23:32:20 node-1 haproxy[31295]: proxy nova-novncproxy has no server available!
<27>Oct  5 23:32:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:21 node-1 multipathd: uevent trigger error
<129>Oct  5 23:32:23 node-1 haproxy[340]: 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  5 23:32:23 node-1 haproxy[340]: Server horizon/node-2 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  5 23:32:23 node-1 haproxy[340]: 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  5 23:32:23 node-1 haproxy[340]: Server keystone-1/node-2 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  5 23:32:23 node-1 haproxy[340]: Server keystone-1/node-3 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  5 23:32:23 node-1 haproxy[340]: proxy keystone-1 has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Server keystone-2/node-2 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  5 23:32:24 node-1 haproxy[344]: Server keystone-2/node-3 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  5 23:32:24 node-1 haproxy[344]: proxy keystone-2 has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Server nova-api/node-2 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  5 23:32:24 node-1 haproxy[344]: Server nova-api/node-3 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  5 23:32:24 node-1 haproxy[344]: proxy nova-api has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Server nova-metadata-api/node-2 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  5 23:32:24 node-1 haproxy[344]: Server nova-metadata-api/node-3 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  5 23:32:24 node-1 haproxy[344]: proxy nova-metadata-api has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Backup Server cinder-api/node-2 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  5 23:32:24 node-1 haproxy[344]: Backup Server cinder-api/node-3 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  5 23:32:24 node-1 haproxy[344]: proxy cinder-api has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Server glance-api/node-2 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  5 23:32:24 node-1 haproxy[344]: Server glance-api/node-3 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  5 23:32:24 node-1 haproxy[344]: proxy glance-api has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Server glance-glare/node-2 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  5 23:32:24 node-1 haproxy[344]: Server glance-glare/node-3 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  5 23:32:24 node-1 haproxy[344]: proxy glance-glare has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Server neutron/node-2 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  5 23:32:24 node-1 haproxy[344]: Server neutron/node-3 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  5 23:32:24 node-1 haproxy[344]: proxy neutron has no server available!
<129>Oct  5 23:32:24 node-1 haproxy[344]: 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  5 23:32:24 node-1 haproxy[344]: Server glance-registry/node-2 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  5 23:32:25 node-1 haproxy[344]: Server glance-registry/node-3 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  5 23:32:25 node-1 haproxy[344]: proxy glance-registry has no server available!
<129>Oct  5 23:32:25 node-1 haproxy[344]: 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  5 23:32:25 node-1 haproxy[344]: Backup Server mysqld/node-2 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  5 23:32:25 node-1 haproxy[344]: Backup Server mysqld/node-3 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  5 23:32:25 node-1 haproxy[344]: proxy mysqld has no server available!
<129>Oct  5 23:32:25 node-1 haproxy[344]: 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  5 23:32:25 node-1 haproxy[344]: Server object-storage/node-2 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  5 23:32:25 node-1 haproxy[344]: Server object-storage/node-3 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  5 23:32:25 node-1 haproxy[344]: proxy object-storage has no server available!
<129>Oct  5 23:32:25 node-1 haproxy[344]: 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  5 23:32:25 node-1 haproxy[344]: Server aodh/node-2 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  5 23:32:25 node-1 haproxy[344]: Server aodh/node-3 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  5 23:32:25 node-1 haproxy[344]: proxy aodh has no server available!
<129>Oct  5 23:32:25 node-1 haproxy[344]: 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  5 23:32:25 node-1 haproxy[344]: Server ceilometer/node-2 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  5 23:32:25 node-1 haproxy[344]: Server ceilometer/node-3 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  5 23:32:25 node-1 haproxy[344]: proxy ceilometer has no server available!
<129>Oct  5 23:32:25 node-1 haproxy[344]: 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  5 23:32:25 node-1 haproxy[344]: Server nova-novncproxy/node-2 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  5 23:32:25 node-1 haproxy[344]: Server nova-novncproxy/node-3 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  5 23:32:25 node-1 haproxy[344]: proxy nova-novncproxy has no server available!
<27>Oct  5 23:32:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:26 node-1 multipathd: uevent trigger error
<129>Oct  5 23:32:29 node-1 haproxy[1803]: 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  5 23:32:29 node-1 haproxy[1803]: Server horizon/node-2 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  5 23:32:29 node-1 haproxy[1803]: 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  5 23:32:29 node-1 haproxy[1803]: Server keystone-1/node-2 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  5 23:32:29 node-1 haproxy[1803]: Server keystone-1/node-3 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  5 23:32:29 node-1 haproxy[1803]: proxy keystone-1 has no server available!
<129>Oct  5 23:32:29 node-1 haproxy[1803]: 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  5 23:32:29 node-1 haproxy[1803]: Server keystone-2/node-2 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  5 23:32:29 node-1 haproxy[1803]: Server keystone-2/node-3 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  5 23:32:29 node-1 haproxy[1803]: proxy keystone-2 has no server available!
<129>Oct  5 23:32:29 node-1 haproxy[1803]: 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  5 23:32:29 node-1 haproxy[1803]: Server nova-api/node-2 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  5 23:32:29 node-1 haproxy[1803]: Server nova-api/node-3 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  5 23:32:29 node-1 haproxy[1803]: proxy nova-api has no server available!
<129>Oct  5 23:32:29 node-1 haproxy[1803]: 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  5 23:32:29 node-1 haproxy[1803]: Server nova-metadata-api/node-2 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  5 23:32:30 node-1 haproxy[1808]: Server nova-metadata-api/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy nova-metadata-api has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Backup Server cinder-api/node-2 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  5 23:32:30 node-1 haproxy[1808]: Backup Server cinder-api/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy cinder-api has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Server glance-api/node-2 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  5 23:32:30 node-1 haproxy[1808]: Server glance-api/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy glance-api has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Server glance-glare/node-2 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  5 23:32:30 node-1 haproxy[1808]: Server glance-glare/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy glance-glare has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Server neutron/node-2 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  5 23:32:30 node-1 haproxy[1808]: Server neutron/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy neutron has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Server glance-registry/node-2 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  5 23:32:30 node-1 haproxy[1808]: Server glance-registry/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy glance-registry has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Backup Server mysqld/node-2 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  5 23:32:30 node-1 haproxy[1808]: Backup Server mysqld/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy mysqld has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Server object-storage/node-2 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  5 23:32:30 node-1 haproxy[1808]: Server object-storage/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy object-storage has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Server aodh/node-2 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  5 23:32:30 node-1 haproxy[1808]: Server aodh/node-3 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  5 23:32:30 node-1 haproxy[1808]: proxy aodh has no server available!
<129>Oct  5 23:32:30 node-1 haproxy[1808]: 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  5 23:32:30 node-1 haproxy[1808]: Server ceilometer/node-2 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  5 23:32:31 node-1 haproxy[1808]: Server ceilometer/node-3 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  5 23:32:31 node-1 haproxy[1808]: proxy ceilometer has no server available!
<129>Oct  5 23:32:31 node-1 haproxy[1808]: 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  5 23:32:31 node-1 haproxy[1808]: Server heat-api/node-2 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  5 23:32:31 node-1 haproxy[1808]: Server heat-api/node-3 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  5 23:32:31 node-1 haproxy[1808]: proxy heat-api has no server available!
<129>Oct  5 23:32:31 node-1 haproxy[1808]: 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  5 23:32:31 node-1 haproxy[1808]: Server heat-api-cfn/node-2 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  5 23:32:31 node-1 haproxy[1808]: Server heat-api-cfn/node-3 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  5 23:32:31 node-1 haproxy[1808]: proxy heat-api-cfn has no server available!
<129>Oct  5 23:32:31 node-1 haproxy[1808]: 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  5 23:32:31 node-1 haproxy[1808]: Server heat-api-cloudwatch/node-2 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  5 23:32:31 node-1 haproxy[1808]: Server heat-api-cloudwatch/node-3 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  5 23:32:31 node-1 haproxy[1808]: proxy heat-api-cloudwatch has no server available!
<129>Oct  5 23:32:31 node-1 haproxy[1808]: 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  5 23:32:31 node-1 haproxy[1808]: Server nova-novncproxy/node-2 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  5 23:32:31 node-1 haproxy[1808]: Server nova-novncproxy/node-3 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  5 23:32:31 node-1 haproxy[1808]: proxy nova-novncproxy has no server available!
<27>Oct  5 23:32:32 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:32 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:32 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:32 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:32 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:32:43 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  5 23:33:07 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  5 23:33:09 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  5 23:33:31 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  5 23:33:36 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  5 23:34:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:34:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:34:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:34:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:34:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:49 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:49 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:49 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:49 node-1 multipathd: uevent trigger error
<27>Oct  5 23:35:49 node-1 multipathd: uevent trigger error
<43>Oct  5 23:36:04 node-1 apache2_error [Wed Oct 05 23:36:00.231013 2016] [mpm_event:notice] [pid 6803:tid 140471653398400] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  5 23:36:04 node-1 apache2_error [Wed Oct 05 23:36:00.231148 2016] [core:notice] [pid 6803:tid 140471653398400] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  5 23:36:04 node-1 apache2_error [Wed Oct 05 23:36:03.120870 2016] [mpm_event:notice] [pid 6803:tid 140471653398400] AH00491: caught SIGTERM, shutting down
<43>Oct  5 23:36:04 node-1 apache2_error [Wed Oct 05 23:36:04.212150 2016] [mpm_worker:notice] [pid 7526:tid 140148330370944] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  5 23:36:04 node-1 apache2_error [Wed Oct 05 23:36:04.212228 2016] [core:notice] [pid 7526:tid 140148330370944] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  5 23:36:08 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:08 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:08 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:08 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:12 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:12 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:19 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:19 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:19 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:19 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:19 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  5 23:36:54 node-1 apache2_error [Wed Oct 05 23:36:53.353442 2016] [mpm_worker:notice] [pid 7526:tid 140148330370944] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  5 23:36:54 node-1 apache2_error [Wed Oct 05 23:36:53.361898 2016] [mpm_worker:warn] [pid 7526:tid 140148330370944] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  5 23:36:54 node-1 apache2_error [Wed Oct 05 23:36:53.362674 2016] [mpm_worker:notice] [pid 7526:tid 140148330370944] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  5 23:36:54 node-1 apache2_error [Wed Oct 05 23:36:53.362689 2016] [core:notice] [pid 7526:tid 140148330370944] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  5 23:36:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:36:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:37:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:37:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:37:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:37:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:37:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:37:01 node-1 multipathd: uevent trigger error
<43>Oct  5 23:38:05 node-1 apache2_error [Wed Oct 05 23:38:04.888465 2016] [mpm_worker:notice] [pid 7526:tid 140148330370944] AH00295: caught SIGTERM, shutting down
<43>Oct  5 23:38:15 node-1 apache2_error [Wed Oct 05 23:38:05.652097 2016] [mpm_worker:notice] [pid 28733:tid 140643021944704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  5 23:38:15 node-1 apache2_error [Wed Oct 05 23:38:05.652154 2016] [core:notice] [pid 28733:tid 140643021944704] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  5 23:38:55 node-1 apache2_error [Wed Oct 05 23:38:49.848878 2016] [mpm_worker:notice] [pid 28733:tid 140643021944704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  5 23:38:55 node-1 apache2_error [Wed Oct 05 23:38:49.863418 2016] [mpm_worker:warn] [pid 28733:tid 140643021944704] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  5 23:38:55 node-1 apache2_error [Wed Oct 05 23:38:49.866877 2016] [mpm_worker:notice] [pid 28733:tid 140643021944704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  5 23:38:55 node-1 apache2_error [Wed Oct 05 23:38:49.866899 2016] [core:notice] [pid 28733:tid 140643021944704] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  5 23:39:36 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  5 23:40:10 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:10 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:10 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:10 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:10 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:30 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:52 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:52 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:52 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:52 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:52 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:57 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:57 node-1 multipathd: uevent trigger error
<27>Oct  5 23:40:57 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:41:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:42:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  5 23:43:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:43:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:43:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:43:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:43:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:43:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:05 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:05 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:05 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:05 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:11 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:44:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:45:39 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  5 23:46:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:46:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:46:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:46:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:46:56 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:47:21 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:01 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:31 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:31 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:31 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:31 node-1 multipathd: uevent trigger error
<27>Oct  5 23:48:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  5 23:49:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:15 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Interface
<27>Oct  5 23:49:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Port
<27>Oct  5 23:49:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-prv" in table Port
<27>Oct  5 23:49:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct  5 23:49:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct  5 23:49:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct  5 23:49:23 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:23 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:23 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:23 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:23 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:36 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:50 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:50 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:50 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:50 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:50 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:50 node-1 multipathd: uevent trigger error
<27>Oct  5 23:49:50 node-1 multipathd: uevent trigger error
<27>Oct  5 23:50:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:50:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:50:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:50:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:50:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:50:07 node-1 multipathd: uevent trigger error
<27>Oct  5 23:51:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  5 23:52:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:27 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:52:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:09 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:47 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:53:59 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:06 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:06 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:06 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:06 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:06 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  5 23:54:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:54:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:55:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:55:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:55:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:55:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:55:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:13 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:13 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:13 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:13 node-1 multipathd: uevent trigger error
<11>Oct  5 23:56:26 node-1 liberasurecode[21491]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:26 node-1 liberasurecode[21491]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:26 node-1 liberasurecode[21491]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:26 node-1 liberasurecode[21491]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:26 node-1 liberasurecode[21519]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:26 node-1 liberasurecode[21519]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:26 node-1 liberasurecode[21519]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:26 node-1 liberasurecode[21519]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:27 node-1 liberasurecode[22123]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:27 node-1 liberasurecode[22123]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:27 node-1 liberasurecode[22123]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:27 node-1 liberasurecode[22123]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22671]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22671]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22753]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22753]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22753]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:32 node-1 liberasurecode[22753]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22820]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22820]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22820]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22820]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22834]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22834]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22863]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22863]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22863]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22863]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22877]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22877]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22877]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:33 node-1 liberasurecode[22877]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:49 node-1 liberasurecode[23910]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:49 node-1 liberasurecode[23910]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:49 node-1 liberasurecode[23910]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  5 23:56:49 node-1 liberasurecode[23910]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  5 23:56:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:56:58 node-1 multipathd: uevent trigger error
<27>Oct  5 23:57:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  5 23:57:46 node-1 apache2_error [Wed Oct 05 23:57:45.193501 2016] [mpm_worker:notice] [pid 28733:tid 140643021944704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  5 23:57:46 node-1 apache2_error [Wed Oct 05 23:57:45.576101 2016] [mpm_worker:warn] [pid 28733:tid 140643021944704] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  5 23:57:46 node-1 apache2_error [Wed Oct 05 23:57:45.579996 2016] [mpm_worker:notice] [pid 28733:tid 140643021944704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  5 23:57:46 node-1 apache2_error [Wed Oct 05 23:57:45.580022 2016] [core:notice] [pid 28733:tid 140643021944704] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  5 23:58:26 node-1 apache2_error [Wed Oct 05 23:58:22.727065 2016] [mpm_worker:notice] [pid 28733:tid 140643021944704] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  5 23:58:26 node-1 apache2_error [Wed Oct 05 23:58:22.920843 2016] [mpm_worker:warn] [pid 28733:tid 140643021944704] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  5 23:58:26 node-1 apache2_error [Wed Oct 05 23:58:22.928793 2016] [mpm_worker:notice] [pid 28733:tid 140643021944704] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  5 23:58:26 node-1 apache2_error [Wed Oct 05 23:58:22.928823 2016] [core:notice] [pid 28733:tid 140643021944704] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  5 23:58:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:26 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:33 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:33 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:33 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:33 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:33 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:39 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:58:48 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:03 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:03 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:03 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:03 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:03 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:23 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:29 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  5 23:59:38 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:38 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:38 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:38 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:43 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:49 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:49 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:49 node-1 multipathd: uevent trigger error
<27>Oct  5 23:59:49 node-1 multipathd: uevent trigger error
<11>Oct  6 00:00:01 node-1 liberasurecode[2748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 00:00:01 node-1 liberasurecode[2748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 00:00:01 node-1 liberasurecode[2748]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 00:00:01 node-1 liberasurecode[2748]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  6 00:00:02 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:02 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:02 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:02 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:02 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:09 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:09 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:09 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:10 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:10 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:25 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  6 00:00:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:39 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:39 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:39 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:39 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:39 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:46 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:47 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:47 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:47 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:47 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:52 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:52 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:52 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:52 node-1 multipathd: uevent trigger error
<27>Oct  6 00:00:52 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:08 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:08 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:08 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:08 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:08 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:12 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:12 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:12 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:12 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:12 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:17 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:17 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:17 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:17 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:21 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:21 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:21 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:21 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:21 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:26 node-1 multipathd: uevent trigger error
<27>Oct  6 00:02:26 node-1 multipathd: uevent trigger error
