Oct 12 18:39:35 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8381" x-info="http://www.rsyslog.com"] start
Oct 12 18:39:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 12 18:39:35 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 12 18:39:35 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 12 18:39:35 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 12 18:39:35 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 12 18:39:35 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 12 18:39:35 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 12 18:39:35 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=9bbb3a6b-f513-41a5-b7a0-883993494d8b nomdmonddf nomdmonisw
Oct 12 18:39:35 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 12 18:39:35 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 12 18:39:35 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 12 18:39:35 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 12 18:39:35 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 12 18:39:35 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 12 18:39:35 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 12 18:39:35 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 12 18:39:35 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 12 18:39:35 node-1 kernel: [    0.000000] No AGP bridge found
Oct 12 18:39:35 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 12 18:39:35 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 12 18:39:35 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 12 18:39:35 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 12 18:39:35 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 12 18:39:35 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 12 18:39:35 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 12 18:39:35 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 12 18:39:35 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 12 18:39:35 node-1 kernel: [    0.000000]   2 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000]   3 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000]   4 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000]   5 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000]   6 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000]   7 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000]   8 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000]   9 disabled
Oct 12 18:39:35 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 12 18:39:35 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 12 18:39:35 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 12 18:39:35 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 12 18:39:35 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 12 18:39:35 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 12 18:39:35 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 12 18:39:35 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 12 18:39:35 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 12 18:39:35 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 12 18:39:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 12 18:39:35 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 12 18:39:35 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 12 18:39:35 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 12 18:39:35 node-1 kernel: [    0.000000] Zone ranges:
Oct 12 18:39:35 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 12 18:39:35 node-1 kernel: [    0.000000] Early memory node ranges
Oct 12 18:39:35 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 12 18:39:35 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 12 18:39:35 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 12 18:39:35 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 12 18:39:35 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 12 18:39:35 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 12 18:39:35 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 12 18:39:35 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 12 18:39:35 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 12 18:39:35 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 12 18:39:35 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 12 18:39:35 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 12 18:39:35 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 12 18:39:35 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 12 18:39:35 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 12 18:39:35 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 12 18:39:35 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 12 18:39:35 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 12 18:39:35 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 12 18:39:35 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 12 18:39:35 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 12 18:39:35 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 12 18:39:35 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 12 18:39:35 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 12 18:39:35 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 12 18:39:35 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 12 18:39:35 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=9bbb3a6b-f513-41a5-b7a0-883993494d8b nomdmonddf nomdmonisw
Oct 12 18:39:35 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 12 18:39:35 node-1 kernel: [    0.000000] Checking aperture...
Oct 12 18:39:35 node-1 kernel: [    0.000000] No AGP bridge found
Oct 12 18:39:35 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 12 18:39:35 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 12 18:39:35 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct 12 18:39:35 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 12 18:39:35 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 12 18:39:35 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 12 18:39:35 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 12 18:39:35 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 12 18:39:35 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 12 18:39:35 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 12 18:39:35 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 12 18:39:35 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 12 18:39:35 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 12 18:39:35 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 12 18:39:35 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 12 18:39:35 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 12 18:39:35 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 12 18:39:35 node-1 kernel: [    0.004000] tsc: Detected 3491.867 MHz processor
Oct 12 18:39:35 node-1 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.73 BogoMIPS (lpj=13967468)
Oct 12 18:39:35 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 12 18:39:35 node-1 kernel: [    0.000043] Security Framework initialized
Oct 12 18:39:35 node-1 kernel: [    0.000062] AppArmor: AppArmor initialized
Oct 12 18:39:35 node-1 kernel: [    0.000063] Yama: becoming mindful.
Oct 12 18:39:35 node-1 kernel: [    0.001453] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.006361] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.008286] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.008314] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.008606] Initializing cgroup subsys memory
Oct 12 18:39:35 node-1 kernel: [    0.008614] Initializing cgroup subsys devices
Oct 12 18:39:35 node-1 kernel: [    0.008616] Initializing cgroup subsys freezer
Oct 12 18:39:35 node-1 kernel: [    0.008618] Initializing cgroup subsys blkio
Oct 12 18:39:35 node-1 kernel: [    0.008619] Initializing cgroup subsys perf_event
Oct 12 18:39:35 node-1 kernel: [    0.008622] Initializing cgroup subsys hugetlb
Oct 12 18:39:35 node-1 kernel: [    0.008641] CPU: Physical Processor ID: 0
Oct 12 18:39:35 node-1 kernel: [    0.008642] CPU: Processor Core ID: 0
Oct 12 18:39:35 node-1 kernel: [    0.008646] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 12 18:39:35 node-1 kernel: [    0.008646] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 12 18:39:35 node-1 kernel: [    0.009340] mce: CPU supports 22 MCE banks
Oct 12 18:39:35 node-1 kernel: [    0.009367] CPU0: Thermal monitoring enabled (TM1)
Oct 12 18:39:35 node-1 kernel: [    0.009388] process: using mwait in idle threads
Oct 12 18:39:35 node-1 kernel: [    0.009391] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 12 18:39:35 node-1 kernel: [    0.009391] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 12 18:39:35 node-1 kernel: [    0.009391] tlb_flushall_shift: 6
Oct 12 18:39:35 node-1 kernel: [    0.009480] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 12 18:39:35 node-1 kernel: [    0.010202] ACPI: Core revision 20131115
Oct 12 18:39:35 node-1 kernel: [    0.022859] ACPI: All ACPI Tables successfully acquired
Oct 12 18:39:35 node-1 kernel: [    0.023019] ftrace: allocating 28614 entries in 112 pages
Oct 12 18:39:35 node-1 kernel: [    0.031724] dmar: Host address width 46
Oct 12 18:39:35 node-1 kernel: [    0.031726] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 12 18:39:35 node-1 kernel: [    0.031732] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 12 18:39:35 node-1 kernel: [    0.031734] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 12 18:39:35 node-1 kernel: [    0.031738] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 12 18:39:35 node-1 kernel: [    0.031739] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 12 18:39:35 node-1 kernel: [    0.031740] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 12 18:39:35 node-1 kernel: [    0.031741] dmar: ATSR flags: 0x0
Oct 12 18:39:35 node-1 kernel: [    0.031743] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 12 18:39:35 node-1 kernel: [    0.031744] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 12 18:39:35 node-1 kernel: [    0.031859] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 12 18:39:35 node-1 kernel: [    0.031861] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 12 18:39:35 node-1 kernel: [    0.031862] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 12 18:39:35 node-1 kernel: [    0.031863] HPET id 0 under DRHD base 0xc7ffc000
Oct 12 18:39:35 node-1 kernel: [    0.031864] Your BIOS is broken and requested that x2apic be disabled.
Oct 12 18:39:35 node-1 kernel: [    0.031864] This will slightly decrease performance.
Oct 12 18:39:35 node-1 kernel: [    0.031864] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 12 18:39:35 node-1 kernel: [    0.032296] Enabled IRQ remapping in xapic mode
Oct 12 18:39:35 node-1 kernel: [    0.032297] x2apic not enabled, IRQ remapping is in xapic mode
Oct 12 18:39:35 node-1 kernel: [    0.032301] Switched APIC routing to physical flat.
Oct 12 18:39:35 node-1 kernel: [    0.032921] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 12 18:39:35 node-1 kernel: [    0.072570] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 12 18:39:35 node-1 kernel: [    0.072576] TSC deadline timer enabled
Oct 12 18:39:35 node-1 kernel: [    0.072583] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 12 18:39:35 node-1 kernel: [    0.072589] ... version:                3
Oct 12 18:39:35 node-1 kernel: [    0.072590] ... bit width:              48
Oct 12 18:39:35 node-1 kernel: [    0.072591] ... generic registers:      4
Oct 12 18:39:35 node-1 kernel: [    0.072592] ... value mask:             0000ffffffffffff
Oct 12 18:39:35 node-1 kernel: [    0.072593] ... max period:             0000ffffffffffff
Oct 12 18:39:35 node-1 kernel: [    0.072594] ... fixed-purpose events:   3
Oct 12 18:39:35 node-1 kernel: [    0.072595] ... event mask:             000000070000000f
Oct 12 18:39:35 node-1 kernel: [    0.073967] x86: Booting SMP configuration:
Oct 12 18:39:35 node-1 kernel: [    0.088072] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 12 18:39:35 node-1 kernel: [    0.073969] .... node  #0, CPUs:        #1  #2  #3
Oct 12 18:39:35 node-1 kernel: [    0.115981] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 12 18:39:35 node-1 kernel: [    0.270128] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 12 18:39:35 node-1 kernel: [    0.325743] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 12 18:39:35 node-1 kernel: [    0.382398] x86: Booted up 2 nodes, 16 CPUs
Oct 12 18:39:35 node-1 kernel: [    0.382401] smpboot: Total of 16 processors activated (111760.80 BogoMIPS)
Oct 12 18:39:35 node-1 kernel: [    0.405998] devtmpfs: initialized
Oct 12 18:39:35 node-1 kernel: [    0.408344] EVM: security.selinux
Oct 12 18:39:35 node-1 kernel: [    0.408346] EVM: security.SMACK64
Oct 12 18:39:35 node-1 kernel: [    0.408347] EVM: security.ima
Oct 12 18:39:35 node-1 kernel: [    0.408348] EVM: security.capability
Oct 12 18:39:35 node-1 kernel: [    0.408399] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.409049] pinctrl core: initialized pinctrl subsystem
Oct 12 18:39:35 node-1 kernel: [    0.409110] regulator-dummy: no parameters
Oct 12 18:39:35 node-1 kernel: [    0.409142] RTC time: 18:39:00, date: 10/12/16
Oct 12 18:39:35 node-1 kernel: [    0.409177] NET: Registered protocol family 16
Oct 12 18:39:35 node-1 kernel: [    0.409260] cpuidle: using governor ladder
Oct 12 18:39:35 node-1 kernel: [    0.409262] cpuidle: using governor menu
Oct 12 18:39:35 node-1 kernel: [    0.409298] ACPI: bus type PCI registered
Oct 12 18:39:35 node-1 kernel: [    0.409299] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 12 18:39:35 node-1 kernel: [    0.409347] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 12 18:39:35 node-1 kernel: [    0.409349] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 12 18:39:35 node-1 kernel: [    0.423089] PCI: Using configuration type 1 for base access
Oct 12 18:39:35 node-1 kernel: [    0.424086] bio: create slab <bio-0> at 0
Oct 12 18:39:35 node-1 kernel: [    0.424357] ACPI: Added _OSI(Module Device)
Oct 12 18:39:35 node-1 kernel: [    0.424359] ACPI: Added _OSI(Processor Device)
Oct 12 18:39:35 node-1 kernel: [    0.424360] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 12 18:39:35 node-1 kernel: [    0.424361] ACPI: Added _OSI(Processor Aggregator Device)
Oct 12 18:39:35 node-1 kernel: [    0.437150] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 12 18:39:35 node-1 kernel: [    0.447629] ACPI: Interpreter enabled
Oct 12 18:39:35 node-1 kernel: [    0.447634] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 12 18:39:35 node-1 kernel: [    0.447638] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 12 18:39:35 node-1 kernel: [    0.447640] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 12 18:39:35 node-1 kernel: [    0.447647] ACPI: (supports S0 S4 S5)
Oct 12 18:39:35 node-1 kernel: [    0.447649] ACPI: Using IOAPIC for interrupt routing
Oct 12 18:39:35 node-1 kernel: [    0.447690] HEST: Table parsing has been initialized.
Oct 12 18:39:35 node-1 kernel: [    0.447693] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 12 18:39:35 node-1 kernel: [    0.448252] ACPI: No dock devices found.
Oct 12 18:39:35 node-1 kernel: [    0.459882] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 12 18:39:35 node-1 kernel: [    0.459887] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 12 18:39:35 node-1 kernel: [    0.459890] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 12 18:39:35 node-1 kernel: [    0.459916] PCI host bridge to bus 0000:ff
Oct 12 18:39:35 node-1 kernel: [    0.459919] pci_bus 0000:ff: root bus resource [bus ff]
Oct 12 18:39:35 node-1 kernel: [    0.459927] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.459966] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 12 18:39:35 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 12 18:39:35 node-1 kernel: [    0.459996] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460031] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460060] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.460088] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.460118] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460146] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460175] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460203] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460230] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460256] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460284] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460310] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460336] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460362] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460390] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460417] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460443] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.460471] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460496] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.460521] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460547] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460576] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.460610] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460641] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460670] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460700] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460731] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460761] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460791] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460821] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460851] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460882] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460916] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460948] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.460981] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461011] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461038] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461069] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461100] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461136] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461171] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461203] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461233] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461263] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461293] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461321] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461351] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461379] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461410] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461438] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461467] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461494] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461522] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461553] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461584] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461640] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 12 18:39:35 node-1 kernel: [    0.461643] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 12 18:39:35 node-1 kernel: [    0.461646] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 12 18:39:35 node-1 kernel: [    0.461663] PCI host bridge to bus 0000:7f
Oct 12 18:39:35 node-1 kernel: [    0.461665] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 12 18:39:35 node-1 kernel: [    0.461670] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461697] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.461725] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461754] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461776] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.461800] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.461826] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461852] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461876] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461898] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461922] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461950] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461976] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.461999] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462025] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462051] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462073] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462096] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462118] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.462142] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462164] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.462186] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462208] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462234] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 12 18:39:35 node-1 kernel: [    0.462267] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462293] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462319] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462345] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462370] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462396] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462422] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462450] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462474] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462502] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462529] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462557] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462585] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462611] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462637] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462667] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462692] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462718] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462746] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462773] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462798] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462824] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462851] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462877] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462902] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462928] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462957] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.462981] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.463003] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.463026] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.463051] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.463080] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.463105] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.464348] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 12 18:39:35 node-1 kernel: [    0.464351] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 12 18:39:35 node-1 kernel: [    0.465480] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 12 18:39:35 node-1 kernel: [    0.465990] PCI host bridge to bus 0000:00
Oct 12 18:39:35 node-1 kernel: [    0.465992] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 12 18:39:35 node-1 kernel: [    0.465994] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 12 18:39:35 node-1 kernel: [    0.465995] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 12 18:39:35 node-1 kernel: [    0.465996] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 12 18:39:35 node-1 kernel: [    0.465998] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 12 18:39:35 node-1 kernel: [    0.465999] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 12 18:39:35 node-1 kernel: [    0.466000] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 12 18:39:35 node-1 kernel: [    0.466006] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 12 18:39:35 node-1 kernel: [    0.466089] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.466120] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.466162] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 12 18:39:35 node-1 kernel: [    0.466181] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.466210] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.466251] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 12 18:39:35 node-1 kernel: [    0.466267] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.466297] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.466339] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 12 18:39:35 node-1 kernel: [    0.466357] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.466428] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.466506] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.466583] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 12 18:39:35 node-1 kernel: [    0.466588] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 12 18:39:35 node-1 kernel: [    0.466674] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 12 18:39:35 node-1 kernel: [    0.466821] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 12 18:39:35 node-1 kernel: [    0.466839] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 12 18:39:35 node-1 kernel: [    0.466917] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.466972] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 12 18:39:35 node-1 kernel: [    0.466994] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.467049] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.467093] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 12 18:39:35 node-1 kernel: [    0.467121] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.467177] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.467220] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 12 18:39:35 node-1 kernel: [    0.467245] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 12 18:39:35 node-1 kernel: [    0.467262] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 12 18:39:35 node-1 kernel: [    0.467340] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.467391] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 12 18:39:35 node-1 kernel: [    0.467417] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 12 18:39:35 node-1 kernel: [    0.467666] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 12 18:39:35 node-1 kernel: [    0.467672] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 12 18:39:35 node-1 kernel: [    0.467678] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.467684] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.467691] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 12 18:39:35 node-1 kernel: [    0.467722] pci 0000:01:00.0: supports D1 D2
Oct 12 18:39:35 node-1 kernel: [    0.473944] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 12 18:39:35 node-1 kernel: [    0.473947] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 12 18:39:35 node-1 kernel: [    0.473949] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 12 18:39:35 node-1 kernel: [    0.474059] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.474093] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 12 18:39:35 node-1 kernel: [    0.481949] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 12 18:39:35 node-1 kernel: [    0.481956] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.481960] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 12 18:39:35 node-1 kernel: [    0.482043] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.482116] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.482219] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.482264] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 12 18:39:35 node-1 kernel: [    0.482267] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.482269] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 12 18:39:35 node-1 kernel: [    0.482322] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.482449] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.482503] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 12 18:39:35 node-1 kernel: [    0.482506] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.482508] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.482557] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.482676] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.482719] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.482858] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.482896] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.483016] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.483052] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 12 18:39:35 node-1 kernel: [    0.483171] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 12 18:39:35 node-1 kernel: [    0.483212] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 12 18:39:35 node-1 kernel: [    0.483214] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.483216] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.483274] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 12 18:39:35 node-1 kernel: [    0.483340] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.483393] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.483434] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 12 18:39:35 node-1 kernel: [    0.483516] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 12 18:39:35 node-1 kernel: [    0.483622] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 12 18:39:35 node-1 kernel: [    0.483624] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.483626] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.483682] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 12 18:39:35 node-1 kernel: [    0.483735] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.483784] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.484025] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 12 18:39:35 node-1 kernel: [    0.484028] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 12 18:39:35 node-1 kernel: [    0.484091] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 12 18:39:35 node-1 kernel: [    0.484145] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.484193] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.484402] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 12 18:39:35 node-1 kernel: [    0.484405] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 12 18:39:35 node-1 kernel: [    0.484463] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 12 18:39:35 node-1 kernel: [    0.484523] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.484575] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 12 18:39:35 node-1 kernel: [    0.484797] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 12 18:39:35 node-1 kernel: [    0.484801] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 12 18:39:35 node-1 kernel: [    0.484999] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 12 18:39:35 node-1 kernel: [    0.485038] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 12 18:39:35 node-1 kernel: [    0.485111] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 12 18:39:35 node-1 kernel: [    0.485130] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 12 18:39:35 node-1 kernel: [    0.485143] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 12 18:39:35 node-1 kernel: [    0.485157] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 12 18:39:35 node-1 kernel: [    0.485207] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 12 18:39:35 node-1 kernel: [    0.489971] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 12 18:39:35 node-1 kernel: [    0.489992] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 12 18:39:35 node-1 kernel: [    0.490024] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 12 18:39:35 node-1 kernel: [    0.490517] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 12 18:39:35 node-1 kernel: [    0.490520] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 12 18:39:35 node-1 kernel: [    0.490644] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 12 18:39:35 node-1 kernel: [    0.490750] PCI host bridge to bus 0000:80
Oct 12 18:39:35 node-1 kernel: [    0.490752] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 12 18:39:35 node-1 kernel: [    0.490753] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 12 18:39:35 node-1 kernel: [    0.490754] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 12 18:39:35 node-1 kernel: [    0.490763] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.490825] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.490892] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 12 18:39:35 node-1 kernel: [    0.490956] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 12 18:39:35 node-1 kernel: [    0.490961] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 12 18:39:35 node-1 kernel: [    0.491034] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 12 18:39:35 node-1 kernel: [    0.491335] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 12 18:39:35 node-1 kernel: [    0.491367] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 12 18:39:35 node-1 kernel: [    0.491397] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 12 18:39:35 node-1 kernel: [    0.491426] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 12 18:39:35 node-1 kernel: [    0.491455] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 12 18:39:35 node-1 kernel: [    0.491485] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 12 18:39:35 node-1 kernel: [    0.491515] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 12 18:39:35 node-1 kernel: [    0.491544] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 12 18:39:35 node-1 kernel: [    0.491629] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 12 18:39:35 node-1 kernel: [    0.491633] ACPI: \_SB_.UNC1: notify handler is installed
Oct 12 18:39:35 node-1 kernel: [    0.491635] ACPI: \_SB_.UNC0: notify handler is installed
Oct 12 18:39:35 node-1 kernel: [    0.491650] ACPI: \_SB_.PCI0: notify handler is installed
Oct 12 18:39:35 node-1 kernel: [    0.491703] ACPI: \_SB_.PCI1: notify handler is installed
Oct 12 18:39:35 node-1 kernel: [    0.491782] Found 4 acpi root devices
Oct 12 18:39:35 node-1 kernel: [    0.491889] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 12 18:39:35 node-1 kernel: [    0.491891] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 12 18:39:35 node-1 kernel: [    0.491893] vgaarb: loaded
Oct 12 18:39:35 node-1 kernel: [    0.491894] vgaarb: bridge control possible 0000:0c:00.0
Oct 12 18:39:35 node-1 kernel: [    0.492005] SCSI subsystem initialized
Oct 12 18:39:35 node-1 kernel: [    0.492069] libata version 3.00 loaded.
Oct 12 18:39:35 node-1 kernel: [    0.492084] ACPI: bus type USB registered
Oct 12 18:39:35 node-1 kernel: [    0.492094] usbcore: registered new interface driver usbfs
Oct 12 18:39:35 node-1 kernel: [    0.492099] usbcore: registered new interface driver hub
Oct 12 18:39:35 node-1 kernel: [    0.492122] usbcore: registered new device driver usb
Oct 12 18:39:35 node-1 kernel: [    0.492291] PCI: Using ACPI for IRQ routing
Oct 12 18:39:35 node-1 kernel: [    0.495885] PCI: pci_cache_line_size set to 64 bytes
Oct 12 18:39:35 node-1 kernel: [    0.496091] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 12 18:39:35 node-1 kernel: [    0.496092] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 12 18:39:35 node-1 kernel: [    0.496093] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 12 18:39:35 node-1 kernel: [    0.496157] NetLabel: Initializing
Oct 12 18:39:35 node-1 kernel: [    0.496158] NetLabel:  domain hash size = 128
Oct 12 18:39:35 node-1 kernel: [    0.496159] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 12 18:39:35 node-1 kernel: [    0.496168] NetLabel:  unlabeled traffic allowed by default
Oct 12 18:39:35 node-1 kernel: [    0.496224] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 12 18:39:35 node-1 kernel: [    0.496228] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 12 18:39:35 node-1 kernel: [    0.498285] Switched to clocksource hpet
Oct 12 18:39:35 node-1 kernel: [    0.502154] AppArmor: AppArmor Filesystem Enabled
Oct 12 18:39:35 node-1 kernel: [    0.502168] pnp: PnP ACPI init
Oct 12 18:39:35 node-1 kernel: [    0.502174] ACPI: bus type PNP registered
Oct 12 18:39:35 node-1 kernel: [    0.502301] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502309] pnp 00:01: [dma 4]
Oct 12 18:39:35 node-1 kernel: [    0.502320] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502348] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502368] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502386] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502419] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502472] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502474] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 12 18:39:35 node-1 kernel: [    0.502476] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502477] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502479] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502483] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502485] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 12 18:39:35 node-1 kernel: [    0.502487] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502489] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502490] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502492] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502493] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502494] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 12 18:39:35 node-1 kernel: [    0.502497] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502580] pnp 00:07: [dma 0 disabled]
Oct 12 18:39:35 node-1 kernel: [    0.502609] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502684] pnp 00:08: [dma 0 disabled]
Oct 12 18:39:35 node-1 kernel: [    0.502715] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 12 18:39:35 node-1 kernel: [    0.502766] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 12 18:39:35 node-1 kernel: [    0.503117] pnp: PnP ACPI: found 10 devices
Oct 12 18:39:35 node-1 kernel: [    0.503118] ACPI: bus type PNP unregistered
Oct 12 18:39:35 node-1 kernel: [    0.509334] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 12 18:39:35 node-1 kernel: [    0.509336] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 12 18:39:35 node-1 kernel: [    0.509339] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 12 18:39:35 node-1 kernel: [    0.509343] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 12 18:39:35 node-1 kernel: [    0.509345] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509363] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509393] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 12 18:39:35 node-1 kernel: [    0.509407] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509436] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 12 18:39:35 node-1 kernel: [    0.509451] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 12 18:39:35 node-1 kernel: [    0.509479] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 12 18:39:35 node-1 kernel: [    0.509494] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 12 18:39:35 node-1 kernel: [    0.509523] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 12 18:39:35 node-1 kernel: [    0.509525] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509539] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509568] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 12 18:39:35 node-1 kernel: [    0.509570] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509585] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509614] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 12 18:39:35 node-1 kernel: [    0.509615] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509618] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509622] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 12 18:39:35 node-1 kernel: [    0.509624] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509626] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509630] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 12 18:39:35 node-1 kernel: [    0.509635] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 12 18:39:35 node-1 kernel: [    0.509643] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 12 18:39:35 node-1 kernel: [    0.509646] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 12 18:39:35 node-1 kernel: [    0.509652] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 12 18:39:35 node-1 kernel: [    0.509653] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 12 18:39:35 node-1 kernel: [    0.509654] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 12 18:39:35 node-1 kernel: [    0.509655] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 12 18:39:35 node-1 kernel: [    0.509656] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 12 18:39:35 node-1 kernel: [    0.509657] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 12 18:39:35 node-1 kernel: [    0.509658] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 12 18:39:35 node-1 kernel: [    0.509659] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 12 18:39:35 node-1 kernel: [    0.509660] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509661] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509662] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509662] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509663] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509664] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509665] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509666] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509667] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 12 18:39:35 node-1 kernel: [    0.509668] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509669] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 12 18:39:35 node-1 kernel: [    0.509670] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 12 18:39:35 node-1 kernel: [    0.509671] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 12 18:39:35 node-1 kernel: [    0.509672] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 12 18:39:35 node-1 kernel: [    0.509674] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 12 18:39:35 node-1 kernel: [    0.509675] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 12 18:39:35 node-1 kernel: [    0.509716] NET: Registered protocol family 2
Oct 12 18:39:35 node-1 kernel: [    0.509972] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.510311] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.510456] TCP: Hash tables configured (established 262144 bind 65536)
Oct 12 18:39:35 node-1 kernel: [    0.510494] TCP: reno registered
Oct 12 18:39:35 node-1 kernel: [    0.510523] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.510619] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.510763] NET: Registered protocol family 1
Oct 12 18:39:35 node-1 kernel: [    0.550387] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 12 18:39:35 node-1 kernel: [    0.550402] PCI: CLS 64 bytes, default 64
Oct 12 18:39:35 node-1 kernel: [    0.550479] Trying to unpack rootfs image as initramfs...
Oct 12 18:39:35 node-1 kernel: [    0.769507] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct 12 18:39:35 node-1 kernel: [    0.769554] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 12 18:39:35 node-1 kernel: [    0.769556] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 12 18:39:35 node-1 kernel: [    0.769959] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.769965] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.769969] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.769975] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.769984] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.769995] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770004] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770013] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770021] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770029] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770035] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770041] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770050] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770067] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770082] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770095] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 12 18:39:35 node-1 kernel: [    0.770201] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 12 18:39:35 node-1 kernel: [    0.770207] Scanning for low memory corruption every 60 seconds
Oct 12 18:39:35 node-1 kernel: [    0.770692] Initialise system trusted keyring
Oct 12 18:39:35 node-1 kernel: [    0.770745] audit: initializing netlink socket (disabled)
Oct 12 18:39:35 node-1 kernel: [    0.770761] type=2000 audit(1476297539.724:1): initialized
Oct 12 18:39:35 node-1 kernel: [    0.788526] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 12 18:39:35 node-1 kernel: [    0.790047] zbud: loaded
Oct 12 18:39:35 node-1 kernel: [    0.790174] VFS: Disk quotas dquot_6.5.2
Oct 12 18:39:35 node-1 kernel: [    0.790209] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 12 18:39:35 node-1 kernel: [    0.790595] fuse init (API version 7.22)
Oct 12 18:39:35 node-1 kernel: [    0.790658] msgmni has been set to 32768
Oct 12 18:39:35 node-1 kernel: [    0.790707] Key type big_key registered
Oct 12 18:39:35 node-1 kernel: [    0.791218] Key type asymmetric registered
Oct 12 18:39:35 node-1 kernel: [    0.791219] Asymmetric key parser 'x509' registered
Oct 12 18:39:35 node-1 kernel: [    0.791241] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 12 18:39:35 node-1 kernel: [    0.791308] io scheduler noop registered
Oct 12 18:39:35 node-1 kernel: [    0.791309] io scheduler deadline registered (default)
Oct 12 18:39:35 node-1 kernel: [    0.791331] io scheduler cfq registered
Oct 12 18:39:35 node-1 kernel: [    0.791833] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    0.792012] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    0.792129] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    0.792241] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    0.792356] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    0.792454] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    0.792874] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 12 18:39:35 node-1 kernel: [    0.792928] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 12 18:39:35 node-1 kernel: [    0.792944] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 12 18:39:35 node-1 kernel: [    0.792954] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792956] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792959] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 12 18:39:35 node-1 kernel: [    0.792964] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792965] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792967] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792968] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792969] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792971] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792972] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792974] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792975] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792977] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792978] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792979] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792982] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 12 18:39:35 node-1 kernel: [    0.792987] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.792989] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 12 18:39:35 node-1 kernel: [    0.793004] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.793007] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 12 18:39:35 node-1 kernel: [    0.793018] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.793020] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 12 18:39:35 node-1 kernel: [    0.793023] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 12 18:39:35 node-1 kernel: [    0.793059] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 12 18:39:35 node-1 kernel: [    0.793065] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 12 18:39:35 node-1 kernel: [    0.793070] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 12 18:39:35 node-1 kernel: [    0.793080] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 12 18:39:35 node-1 kernel: [    0.793120] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 12 18:39:35 node-1 kernel: [    0.793122] vesafb: scrolling: redraw
Oct 12 18:39:35 node-1 kernel: [    0.793124] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 12 18:39:35 node-1 kernel: [    0.813888] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 12 18:39:35 node-1 kernel: [    0.822470] Console: switching to colour frame buffer device 80x30
Oct 12 18:39:35 node-1 kernel: [    0.831257] fb0: VESA VGA frame buffer device
Oct 12 18:39:35 node-1 kernel: [    0.831455] intel_idle: MWAIT substates: 0x2120
Oct 12 18:39:35 node-1 kernel: [    0.831456] intel_idle: v0.4 model 0x3F
Oct 12 18:39:35 node-1 kernel: [    0.831457] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 12 18:39:35 node-1 kernel: [    0.831685] ipmi message handler version 39.2
Oct 12 18:39:35 node-1 kernel: [    0.831960] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 12 18:39:35 node-1 kernel: [    0.832391] ACPI: AC Adapter [P111] (on-line)
Oct 12 18:39:35 node-1 kernel: [    0.837641] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 12 18:39:35 node-1 kernel: [    0.848662] ACPI: Power Button [PWRB]
Oct 12 18:39:35 node-1 kernel: [    0.854419] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 12 18:39:35 node-1 kernel: [    0.866038] ACPI: Power Button [PWRF]
Oct 12 18:39:35 node-1 kernel: [    0.883775] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 12 18:39:35 node-1 kernel: [    0.895445] pstore: Registered erst as persistent store backend
Oct 12 18:39:35 node-1 kernel: [    0.901634] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 12 18:39:35 node-1 kernel: [    0.913596] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 12 18:39:35 node-1 kernel: [    0.940339] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 12 18:39:35 node-1 kernel: [    0.973645] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 12 18:39:35 node-1 kernel: [    0.987701] Linux agpgart interface v0.103
Oct 12 18:39:35 node-1 kernel: [    0.995328] brd: module loaded
Oct 12 18:39:35 node-1 kernel: [    1.002369] loop: module loaded
Oct 12 18:39:35 node-1 kernel: [    1.009094] libphy: Fixed MDIO Bus: probed
Oct 12 18:39:35 node-1 kernel: [    1.015550] tun: Universal TUN/TAP device driver, 1.6
Oct 12 18:39:35 node-1 kernel: [    1.022025] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 12 18:39:35 node-1 kernel: [    1.028549] PPP generic driver version 2.4.2
Oct 12 18:39:35 node-1 kernel: [    1.034943] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 12 18:39:35 node-1 kernel: [    1.041384] ehci-pci: EHCI PCI platform driver
Oct 12 18:39:35 node-1 kernel: [    1.047894] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 12 18:39:35 node-1 kernel: [    1.054304] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 12 18:39:35 node-1 kernel: [    1.066818] ehci-pci 0000:00:1a.0: debug port 2
Oct 12 18:39:35 node-1 kernel: [    1.077027] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 12 18:39:35 node-1 kernel: [    1.077046] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 12 18:39:35 node-1 kernel: [    1.093784] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 12 18:39:35 node-1 kernel: [    1.099859] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 12 18:39:35 node-1 kernel: [    1.106042] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 12 18:39:35 node-1 kernel: [    1.118102] usb usb1: Product: EHCI Host Controller
Oct 12 18:39:35 node-1 kernel: [    1.124213] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct 12 18:39:35 node-1 kernel: [    1.130282] usb usb1: SerialNumber: 0000:00:1a.0
Oct 12 18:39:35 node-1 kernel: [    1.136234] hub 1-0:1.0: USB hub found
Oct 12 18:39:35 node-1 kernel: [    1.142013] hub 1-0:1.0: 2 ports detected
Oct 12 18:39:35 node-1 kernel: [    1.147809] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 12 18:39:35 node-1 kernel: [    1.153392] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 12 18:39:35 node-1 kernel: [    1.164289] ehci-pci 0000:00:1d.0: debug port 2
Oct 12 18:39:35 node-1 kernel: [    1.173590] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 12 18:39:35 node-1 kernel: [    1.173593] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 12 18:39:35 node-1 kernel: [    1.189703] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 12 18:39:35 node-1 kernel: [    1.194909] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 12 18:39:35 node-1 kernel: [    1.200213] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 12 18:39:35 node-1 kernel: [    1.210788] usb usb2: Product: EHCI Host Controller
Oct 12 18:39:35 node-1 kernel: [    1.216258] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct 12 18:39:35 node-1 kernel: [    1.221797] usb usb2: SerialNumber: 0000:00:1d.0
Oct 12 18:39:35 node-1 kernel: [    1.227315] hub 2-0:1.0: USB hub found
Oct 12 18:39:35 node-1 kernel: [    1.232656] hub 2-0:1.0: 2 ports detected
Oct 12 18:39:35 node-1 kernel: [    1.237960] ehci-platform: EHCI generic platform driver
Oct 12 18:39:35 node-1 kernel: [    1.243194] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 12 18:39:35 node-1 kernel: [    1.248505] ohci-pci: OHCI PCI platform driver
Oct 12 18:39:35 node-1 kernel: [    1.253812] ohci-platform: OHCI generic platform driver
Oct 12 18:39:35 node-1 kernel: [    1.259009] uhci_hcd: USB Universal Host Controller Interface driver
Oct 12 18:39:35 node-1 kernel: [    1.264369] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 12 18:39:35 node-1 kernel: [    1.457482] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 12 18:39:35 node-1 kernel: [    1.765228] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 12 18:39:35 node-1 kernel: [    1.781565] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 12 18:39:35 node-1 kernel: [    1.787178] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 12 18:39:35 node-1 kernel: [    1.792958] hub 1-1:1.0: USB hub found
Oct 12 18:39:35 node-1 kernel: [    1.798552] hub 1-1:1.0: 6 ports detected
Oct 12 18:39:35 node-1 kernel: [    1.917110] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 12 18:39:35 node-1 kernel: [    2.303370] i8042: No controller found
Oct 12 18:39:35 node-1 kernel: [    2.308903] mousedev: PS/2 mouse device common for all mice
Oct 12 18:39:35 node-1 kernel: [    2.314611] rtc_cmos 00:02: RTC can wake from S4
Oct 12 18:39:35 node-1 kernel: [    2.320311] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 12 18:39:35 node-1 kernel: [    2.321555] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 12 18:39:35 node-1 kernel: [    2.321556] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 12 18:39:35 node-1 kernel: [    2.322185] hub 2-1:1.0: USB hub found
Oct 12 18:39:35 node-1 kernel: [    2.322423] hub 2-1:1.0: 8 ports detected
Oct 12 18:39:35 node-1 kernel: [    2.348455] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 12 18:39:35 node-1 kernel: [    2.359706] device-mapper: uevent: version 1.0.3
Oct 12 18:39:35 node-1 kernel: [    2.365385] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 12 18:39:35 node-1 kernel: [    2.376709] ledtrig-cpu: registered to indicate activity on CPUs
Oct 12 18:39:35 node-1 kernel: [    2.382659] TCP: cubic registered
Oct 12 18:39:35 node-1 kernel: [    2.388492] NET: Registered protocol family 10
Oct 12 18:39:35 node-1 kernel: [    2.394503] NET: Registered protocol family 17
Oct 12 18:39:35 node-1 kernel: [    2.400252] Key type dns_resolver registered
Oct 12 18:39:35 node-1 kernel: [    2.406359] Loading compiled-in X.509 certificates
Oct 12 18:39:35 node-1 kernel: [    2.412616] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct 12 18:39:35 node-1 kernel: [    2.424260] registered taskstats version 1
Oct 12 18:39:35 node-1 kernel: [    2.432295] Key type trusted registered
Oct 12 18:39:35 node-1 kernel: [    2.439918] Key type encrypted registered
Oct 12 18:39:35 node-1 kernel: [    2.445388] AppArmor: AppArmor sha1 policy hashing enabled
Oct 12 18:39:35 node-1 kernel: [    2.450902] IMA: No TPM chip found, activating TPM-bypass!
Oct 12 18:39:35 node-1 kernel: [    2.457015] regulator-dummy: disabling
Oct 12 18:39:35 node-1 kernel: [    2.462504]   Magic number: 4:967:695
Oct 12 18:39:35 node-1 kernel: [    2.468040] pci 0000:00:00.0: hash matches
Oct 12 18:39:35 node-1 kernel: [    2.473611] acpi LNXCPU:36: hash matches
Oct 12 18:39:35 node-1 kernel: [    2.479083] rtc_cmos 00:02: setting system clock to 2016-10-12 18:39:02 UTC (1476297542)
Oct 12 18:39:35 node-1 kernel: [    2.491452] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 12 18:39:35 node-1 kernel: [    2.497040] EDD information not available.
Oct 12 18:39:35 node-1 kernel: [    2.502538] PM: Hibernation image not present or could not be loaded.
Oct 12 18:39:35 node-1 kernel: [    2.503407] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 12 18:39:35 node-1 kernel: [    2.514580] Write protecting the kernel read-only data: 12288k
Oct 12 18:39:35 node-1 kernel: [    2.520915] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 12 18:39:35 node-1 kernel: [    2.533551] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct 12 18:39:35 node-1 kernel: [    2.566188] device-mapper: multipath: version 1.6.0 loaded
Oct 12 18:39:35 node-1 kernel: [    2.573898] systemd-udevd[216]: starting version 204
Oct 12 18:39:35 node-1 kernel: [    2.596517] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 12 18:39:35 node-1 kernel: [    2.608657] md: linear personality registered for level -1
Oct 12 18:39:35 node-1 kernel: [    2.617781] md: multipath personality registered for level -4
Oct 12 18:39:35 node-1 kernel: [    2.625689] md: raid0 personality registered for level 0
Oct 12 18:39:35 node-1 kernel: [    2.633807] md: raid1 personality registered for level 1
Oct 12 18:39:35 node-1 kernel: [    2.644984] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 12 18:39:35 node-1 kernel: [    2.651076] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 12 18:39:35 node-1 kernel: [    2.657191] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 12 18:39:35 node-1 kernel: [    2.659651] megasas: FW now in Ready state
Oct 12 18:39:35 node-1 kernel: [    2.660103] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.660209] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.660331] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.660631] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.660760] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.660864] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.660963] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661075] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661175] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661298] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661451] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661596] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661676] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661815] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.661935] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.662068] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.662723] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 12 18:39:35 node-1 kernel: [    2.689995] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct 12 18:39:35 node-1 kernel: [    2.703111] 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 12 18:39:35 node-1 kernel: [    2.708483] raid6: sse2x1   11518 MB/s
Oct 12 18:39:35 node-1 kernel: [    2.723426] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 12 18:39:35 node-1 kernel: [    2.730253] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.730257] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.730261] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.730264] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.730301] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.746123] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 12 18:39:35 node-1 kernel: [    2.752774] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 12 18:39:35 node-1 kernel: [    2.757738] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct 12 18:39:35 node-1 kernel: [    2.757739] 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 12 18:39:35 node-1 kernel: [    2.757739] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 12 18:39:35 node-1 kernel: [    2.758160] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.758307] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.758379] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.758468] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.758606] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.758721] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.759068] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 12 18:39:35 node-1 kernel: [    2.776584] raid6: sse2x2   13632 MB/s
Oct 12 18:39:35 node-1 kernel: [    2.818167] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 12 18:39:35 node-1 kernel: [    2.824652] usb 2-1.4: Manufacturer: Avocent
Oct 12 18:39:35 node-1 kernel: [    2.831040] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 12 18:39:35 node-1 kernel: [    2.844308] raid6: sse2x4    9575 MB/s
Oct 12 18:39:35 node-1 kernel: [    2.916258] raid6: avx2x1   14944 MB/s
Oct 12 18:39:35 node-1 kernel: [    2.988187] raid6: avx2x2   18856 MB/s
Oct 12 18:39:35 node-1 kernel: [    3.060125] raid6: avx2x4   21396 MB/s
Oct 12 18:39:35 node-1 kernel: [    3.066128] raid6: using algorithm avx2x4 (21396 MB/s)
Oct 12 18:39:35 node-1 kernel: [    3.072158] raid6: using avx2x2 recovery algorithm
Oct 12 18:39:35 node-1 kernel: [    3.078055] megasas:IOC Init cmd success
Oct 12 18:39:35 node-1 kernel: [    3.078057] Switched to clocksource tsc
Oct 12 18:39:35 node-1 kernel: [    3.090174] xor: automatically using best checksumming function:
Oct 12 18:39:35 node-1 kernel: [    3.090343] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct 12 18:39:35 node-1 kernel: [    3.090344] 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 12 18:39:35 node-1 kernel: [    3.090345] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 12 18:39:35 node-1 kernel: [    3.090411] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.090433] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.090470] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.090505] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.090578] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.102495] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct 12 18:39:35 node-1 kernel: [    3.102497] 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 12 18:39:35 node-1 kernel: [    3.102498] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 12 18:39:35 node-1 kernel: [    3.102574] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.102608] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.102650] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.102685] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.102763] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 12 18:39:35 node-1 kernel: [    3.112141] megasas: INIT adapter done
Oct 12 18:39:35 node-1 kernel: [    3.181045] hidraw: raw HID events driver (C) Jiri Kosina
Oct 12 18:39:35 node-1 kernel: [    3.184180] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 12 18:39:35 node-1 kernel: [    3.185686] scsi0 : LSI SAS based MegaRAID driver
Oct 12 18:39:35 node-1 kernel: [    3.200902] usbcore: registered new interface driver usbhid
Oct 12 18:39:35 node-1 kernel: [    3.206550] usbhid: USB HID core driver
Oct 12 18:39:35 node-1 kernel: [    3.206683] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 12 18:39:35 node-1 kernel: [    3.219969]    avx       : 36455.000 MB/sec
Oct 12 18:39:35 node-1 kernel: [    3.230233] async_tx: api initialized (async)
Oct 12 18:39:35 node-1 kernel: [    3.236345] 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 12 18:39:35 node-1 kernel: [    3.248929] 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 12 18:39:35 node-1 kernel: [    3.250758] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 12 18:39:35 node-1 kernel: [    3.255006] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 12 18:39:35 node-1 kernel: [    3.255348] sd 0:2:0:0: [sda] Write Protect is off
Oct 12 18:39:35 node-1 kernel: [    3.255349] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 12 18:39:35 node-1 kernel: [    3.255549] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 12 18:39:35 node-1 kernel: [    3.255555] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 12 18:39:35 node-1 kernel: [    3.285978]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 12 18:39:35 node-1 kernel: [    3.287976] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 12 18:39:35 node-1 kernel: [    3.328026] 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 12 18:39:35 node-1 kernel: [    3.341083] 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 12 18:39:35 node-1 kernel: [    3.354497] 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 12 18:39:35 node-1 kernel: [    3.368315] 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 12 18:39:35 node-1 kernel: [    3.382711] md: raid6 personality registered for level 6
Oct 12 18:39:35 node-1 kernel: [    3.389909] md: raid5 personality registered for level 5
Oct 12 18:39:35 node-1 kernel: [    3.396900] md: raid4 personality registered for level 4
Oct 12 18:39:35 node-1 kernel: [    3.406936] md: raid10 personality registered for level 10
Oct 12 18:39:35 node-1 kernel: [    3.456417] random: lvm urandom read with 31 bits of entropy available
Oct 12 18:39:35 node-1 kernel: [    3.470789] multipathd (363): /proc/363/oom_adj is deprecated, please use /proc/363/oom_score_adj instead.
Oct 12 18:39:35 node-1 kernel: [    3.608666] bio: create slab <bio-1> at 1
Oct 12 18:39:35 node-1 kernel: [    4.430983] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 12 18:39:35 node-1 kernel: [    4.955304] random: nonblocking pool is initialized
Oct 12 18:39:35 node-1 kernel: [    4.978757] init: plymouth-upstart-bridge main process (550) terminated with status 1
Oct 12 18:39:35 node-1 kernel: [    4.991299] init: plymouth-upstart-bridge main process ended, respawning
Oct 12 18:39:35 node-1 kernel: [    5.116354] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 12 18:39:35 node-1 kernel: [    5.148587] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 12 18:39:35 node-1 kernel: [    5.214344] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 12 18:39:35 node-1 kernel: [    5.280200] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 12 18:39:35 node-1 kernel: [    5.385848] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 12 18:39:35 node-1 kernel: [    5.582023] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 12 18:39:35 node-1 kernel: [    5.636775] XFS (dm-0): Mounting Filesystem
Oct 12 18:39:35 node-1 kernel: [    5.788403] XFS (dm-0): Ending clean mount
Oct 12 18:39:35 node-1 kernel: [    5.902020] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 12 18:39:35 node-1 kernel: [    5.932385] XFS (dm-1): Mounting Filesystem
Oct 12 18:39:35 node-1 kernel: [    6.035524] XFS (dm-1): Ending clean mount
Oct 12 18:39:35 node-1 kernel: [    7.910997] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 12 18:39:35 node-1 kernel: [    7.925935] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 12 18:39:35 node-1 kernel: [    8.060694] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 12 18:39:35 node-1 kernel: [    8.060699] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct 12 18:39:35 node-1 kernel: [    8.060703] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct 12 18:39:35 node-1 kernel: [    8.060707] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct 12 18:39:35 node-1 kernel: [    8.086914] systemd-udevd[774]: starting version 204
Oct 12 18:39:35 node-1 kernel: [    8.283960] wmi: Mapper loaded
Oct 12 18:39:35 node-1 kernel: [    8.288679] power_meter ACPI000D:00: Found ACPI power meter.
Oct 12 18:39:35 node-1 kernel: [    8.288722] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 12 18:39:35 node-1 kernel: [    8.325711] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 12 18:39:35 node-1 kernel: [    8.340139] IPMI System Interface driver.
Oct 12 18:39:35 node-1 kernel: [    8.340178] ipmi_si: probing via ACPI
Oct 12 18:39:35 node-1 kernel: [    8.340189] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 12 18:39:35 node-1 kernel: [    8.340190] ipmi_si: Adding ACPI-specified kcs state machine
Oct 12 18:39:35 node-1 kernel: [    8.340199] ipmi_si: probing via SMBIOS
Oct 12 18:39:35 node-1 kernel: [    8.340200] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 12 18:39:35 node-1 kernel: [    8.340201] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 12 18:39:35 node-1 kernel: [    8.340202] ipmi_si: probing via SPMI
Oct 12 18:39:35 node-1 kernel: [    8.340203] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 12 18:39:35 node-1 kernel: [    8.340204] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 12 18:39:35 node-1 kernel: [    8.340205] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 12 18:39:35 node-1 kernel: [    8.346079] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 12 18:39:35 node-1 kernel: [    8.346083] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 12 18:39:35 node-1 kernel: [    8.346086] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 12 18:39:35 node-1 kernel: [    8.346087] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 12 18:39:35 node-1 kernel: [    8.346099] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 12 18:39:35 node-1 kernel: [    8.384103] systemd-udevd[818]: renamed network interface eth3 to enp9s0
Oct 12 18:39:35 node-1 kernel: [    8.407961] systemd-udevd[807]: renamed network interface eth2 to enp8s0
Oct 12 18:39:35 node-1 kernel: [    8.431969] systemd-udevd[823]: renamed network interface eth1 to enp7s0
Oct 12 18:39:35 node-1 kernel: [    8.467909] systemd-udevd[815]: renamed network interface eth0 to enp6s0
Oct 12 18:39:35 node-1 kernel: [    8.476381] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 12 18:39:35 node-1 kernel: [    8.476388] ipmi_si 00:09: IPMI kcs interface initialized
Oct 12 18:39:35 node-1 kernel: [    8.825737] type=1400 audit(1476297548.847:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.825895] type=1400 audit(1476297548.847:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1050 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.826023] type=1400 audit(1476297548.847:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1050 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.835741] type=1400 audit(1476297548.859:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.835882] type=1400 audit(1476297548.859:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1055 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.836002] type=1400 audit(1476297548.859:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1055 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.845882] type=1400 audit(1476297548.867:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1056 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.846040] type=1400 audit(1476297548.867:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1056 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.846163] type=1400 audit(1476297548.867:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1056 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    8.846607] type=1400 audit(1476297548.867:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1045 comm="apparmor_parser"
Oct 12 18:39:35 node-1 kernel: [    9.364930] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 12 18:39:35 node-1 kernel: [    9.379726] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 12 18:39:35 node-1 kernel: [    9.535234] enic 0000:06:00.0 enp6s0: Link UP
Oct 12 18:39:35 node-1 kernel: [    9.535654] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 12 18:39:35 node-1 kernel: [    9.535663] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 12 18:39:35 node-1 kernel: [   18.528797] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 12 18:39:36 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 12 18:39:36 node-1 kernel: [   36.977650] init: failsafe main process (8408) killed by TERM signal
Oct 12 18:39:37 node-1 dbus[8458]: [system] AppArmor D-Bus mediation is enabled
Oct 12 18:39:37 node-1 kernel: [   37.183755] audit_printk_skb: 30 callbacks suppressed
Oct 12 18:39:37 node-1 kernel: [   37.183757] type=1400 audit(1476297577.196:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8535 comm="apparmor_parser"
Oct 12 18:39:37 node-1 kernel: [   37.184024] type=1400 audit(1476297577.196:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8534 comm="apparmor_parser"
Oct 12 18:39:37 node-1 kernel: [   37.184029] type=1400 audit(1476297577.196:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Oct 12 18:39:37 node-1 kernel: [   37.184032] type=1400 audit(1476297577.196:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Oct 12 18:39:37 node-1 kernel: [   37.184255] type=1400 audit(1476297577.196:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Oct 12 18:39:37 node-1 kernel: [   37.184257] type=1400 audit(1476297577.196:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Oct 12 18:39:37 node-1 kernel: [   37.184373] type=1400 audit(1476297577.196:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Oct 12 18:39:37 node-1 kernel: [   37.269398] type=1400 audit(1476297577.280:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8537 comm="apparmor_parser"
Oct 12 18:39:37 node-1 cron[8566]: (CRON) INFO (pidfile fd = 3)
Oct 12 18:39:37 node-1 anacron[8588]: Anacron 2.3 started on 2016-10-12
Oct 12 18:39:37 node-1 cron[8603]: (CRON) STARTUP (fork ok)
Oct 12 18:39:37 node-1 anacron[8588]: Will run job `cron.daily' in 5 min.
Oct 12 18:39:37 node-1 anacron[8588]: Will run job `cron.weekly' in 10 min.
Oct 12 18:39:37 node-1 anacron[8588]: Will run job `cron.monthly' in 15 min.
Oct 12 18:39:37 node-1 anacron[8588]: Jobs will be executed sequentially
Oct 12 18:39:37 node-1 cron[8603]: (CRON) INFO (Running @reboot jobs)
Oct 12 18:39:37 node-1 multipathd: path checkers start up
Oct 12 18:39:37 node-1 postfix/master[8746]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 12 18:39:41 node-1 puppet-agent[8932]: Reopening log files
Oct 12 18:39:42 node-1 puppet-agent[8932]: Could not request certificate: Connection refused - connect(2)
Oct 12 18:39:57 node-1 puppet-user[9140]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 12 18:39:57 node-1 puppet-user[9140]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 12 18:39:58 node-1 puppet-user[9140]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 12 18:39:58 node-1 puppet-user[9140]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 12 18:39:58 node-1 puppet-user[9140]: Finished catalog run in 1.20 seconds
Oct 12 18:40:00 node-1 multipathd: uevent trigger error
Oct 12 18:40:00 node-1 puppet-user[9760]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 12 18:40:00 node-1 puppet-user[9760]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 12 18:40:00 node-1 puppet-user[9760]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 12 18:40:00 node-1 puppet-user[9760]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 12 18:40:00 node-1 puppet-user[9760]: (/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 12 18:40:00 node-1 puppet-user[9760]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 12 18:40:00 node-1 puppet-user[9760]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 12 18:40:00 node-1 puppet-user[9760]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 12 18:40:00 node-1 puppet-user[9760]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 12 18:40:00 node-1 puppet-user[9760]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 12 18:40:00 node-1 puppet-user[9760]: Finished catalog run in 0.06 seconds
Oct 12 18:40:01 node-1 CRON[10250]: (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 12 18:40:02 node-1 puppet-user[10217]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 12 18:40:02 node-1 puppet-user[10217]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 12 18:40:02 node-1 puppet-user[10217]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 12 18:40:02 node-1 puppet-user[10217]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 12 18:40:02 node-1 puppet-user[10217]: Finished catalog run in 0.03 seconds
Oct 12 18:40:03 node-1 puppet-user[10691]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 12 18:40:03 node-1 puppet-user[10691]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 12 18:40:04 node-1 puppet-user[10691]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 12 18:40:04 node-1 puppet-user[10691]: Finished catalog run in 0.03 seconds
Oct 12 18:40:05 node-1 puppet-user[11148]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 12 18:40:05 node-1 puppet-user[11148]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Oct 12 18:40:05 node-1 puppet-user[11148]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 12 18:40:05 node-1 puppet-user[11148]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Oct 12 18:40:05 node-1 puppet-user[11148]: Finished catalog run in 0.42 seconds
Oct 12 18:40:07 node-1 puppet-user[11618]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 12 18:40:07 node-1 puppet-user[11618]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Oct 12 18:40:07 node-1 puppet-user[11618]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 12 18:40:07 node-1 puppet-user[11618]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 12 18:40:07 node-1 puppet-user[11618]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Oct 12 18:40:07 node-1 puppet-user[11618]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 12 18:40:07 node-1 puppet-user[11618]: Finished catalog run in 0.23 seconds
Oct 12 18:40:09 node-1 puppet-user[12096]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 12 18:40:09 node-1 puppet-user[12096]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Oct 12 18:40:09 node-1 puppet-user[12096]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 12 18:40:09 node-1 kernel: [   69.353856] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 12 18:40:09 node-1 kernel: [   69.353908] 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 12 18:40:09 node-1 puppet-user[12096]: (/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 12 18:40:09 node-1 puppet-user[12096]: Finished catalog run in 0.05 seconds
Oct 12 18:40:11 node-1 puppet-user[12558]: (Scope(Class[main])) MODULAR: sync_time
Oct 12 18:40:11 node-1 puppet-user[12558]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 12 18:40:11 node-1 kernel: [   71.170854] init: plymouth-upstart-bridge main process ended, respawning
Oct 12 18:40:11 node-1 ntpdate[13101]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 12 18:40:11 node-1 puppet-agent[8932]: Could not run: SIGTERM
Oct 12 18:40:11 node-1 kernel: [   71.439428] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 12 18:40:11 node-1 ec2: 
Oct 12 18:40:11 node-1 ec2: #############################################################
Oct 12 18:40:11 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 12 18:40:11 node-1 ec2: 1024 c6:45:34:75:bf:8f:1e:ac:89:02:35:95:9f:e4:1c:b7  root@node-1.domain.tld (DSA)
Oct 12 18:40:11 node-1 ec2: 256 8a:bc:e3:a2:04:29:09:47:49:82:48:58:a5:92:c9:5b  root@node-1.domain.tld (ECDSA)
Oct 12 18:40:11 node-1 ec2: 256 d5:0b:b0:c9:e4:c8:96:cd:37:c7:22:0a:76:87:1a:f2  root@node-1.domain.tld (ED25519)
Oct 12 18:40:11 node-1 ec2: 2048 98:a5:43:4d:b7:d0:ca:15:94:30:51:94:1b:cc:8d:39  root@node-1.domain.tld (RSA)
Oct 12 18:40:11 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 12 18:40:11 node-1 ec2: #############################################################
Oct 12 18:40:17 node-1 ntpdate[13101]: adjust time server 10.20.0.2 offset 0.019895 sec
Oct 12 18:40:17 node-1 puppet-user[12558]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 12 18:40:17 node-1 puppet-user[12558]: Finished catalog run in 6.18 seconds
Oct 12 18:40:22 node-1 puppet-user[13341]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 12 18:40:22 node-1 puppet-user[13341]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 12 18:40:22 node-1 puppet-user[13341]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 12 18:40:22 node-1 puppet-user[13341]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Oct 12 18:40:22 node-1 puppet-user[13341]: Finished catalog run in 0.07 seconds
Oct 12 18:40:23 node-1 puppet-user[13799]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 12 18:40:24 node-1 puppet-user[13799]: Compiled catalog for node-1.domain.tld in environment production in 0.53 seconds
Oct 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:24 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:24 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:24 node-1 puppet-user[13799]: (/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 12 18:40:25 node-1 puppet-user[13799]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 12 18:40:25 node-1 puppet-user[13799]: Finished catalog run in 0.80 seconds
Oct 12 18:40:25 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 12 18:40:25 node-1 nailgun-agent: D, [2016-10-12T18:40:01.648454 #10253] DEBUG -- : Sleep for 24 seconds before sending request
Oct 12 18:40:25 node-1 nailgun-agent: I, [2016-10-12T18:40:25.663268 #10253]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 12 18:40:26 node-1 nailgun-agent: D, [2016-10-12T18:40:26.108966 #10253] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 12 18:40:26 node-1 puppet-user[14416]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 12 18:40:26 node-1 puppet-user[14416]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct 12 18:40:29 node-1 puppet-user[14416]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.306726 #10253] DEBUG -- : Trying to find block devices
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.306993 #10253] DEBUG -- : Found block device: sda
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.307107 #10253] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.307176 #10253] DEBUG -- : Trying to get list of physical devices
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.307651 #10253] DEBUG -- : Getting udev properties for device: sda
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.311545 #10253] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Oct 12 18:40:38 node-1 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"44179", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.311624 #10253] DEBUG -- : Trying to find out if device sda is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.311740 #10253] DEBUG -- : Device sda removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.311783 #10253] DEBUG -- : Device sda seems to be appropriate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.312859 #10253] DEBUG -- : Getting udev properties for device: dm-0
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.316811 #10253] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-VXz8u1MpUnJPBn9PebotaYQE1kLzQTcqXp1erwhCPKRV4GGfsppN63clGeP8Ob3l /dev/disk/by-uuid/280a9f91-211f-48c3-91b1-1d2888beda7d /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-VXz8u1MpUnJPBn9PebotaYQE1kLzQTcqXp1erwhCPKRV4GGfsppN63clGeP8Ob3l", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"280a9f91-211f-48c3-91b1-1d2888beda7d", "ID_FS_UUID_ENC"=>"280a9f91-211f-48c3-91b1-1d2888beda7d", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64984", "nomdmonddf"=>"1", "nom
Oct 12 18:40:38 node-1 nailgun-agent: dmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.316932 #10253] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.317019 #10253] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.317061 #10253] DEBUG -- : Device dm-0 seems to be appropriate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.317106 #10253] DEBUG -- : Getting udev properties for device: dm-1
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.321260 #10253] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-wFVIOUeuFY12xcZWRIpGNTbdvyQVW7gIlacKTzXyoQxwIvUkjqyqa3j2OMVFeuxp /dev/disk/by-uuid/8b9707fd-e069-4a35-a87e-c30336deefd8 /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-wFVIOUeuFY12xcZWRIpGNTbdvyQVW7gIlacKTzXyoQxwIvUkjqyqa3j2OMVFeuxp", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8b9707fd-e069-4a35-a87e-c30336deefd8", "ID_FS_UUID_ENC"=>"8b9707fd-e069-4a35-a87e-c30336deefd8", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Oct 12 18:40:38 node-1 nailgun-agent: 179", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.321354 #10253] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.321455 #10253] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.321498 #10253] DEBUG -- : Device dm-1 seems to be appropriate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.321593 #10253] DEBUG -- : Getting udev properties for device: dm-2
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.325881 #10253] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-4C61tx25LFfnNHCHrmVGYHjoVTyTYMf24BALWN2LpJ0goaow3ehMAvXFNxr8VrVW /dev/disk/by-uuid/6cb93c66-ef5f-4301-96e6-90e326401b48 /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-4C61tx25LFfnNHCHrmVGYHjoVTyTYMf24BALWN2LpJ0goaow3ehMAvXFNxr8VrVW", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6cb93c66-ef5f-4301-96e6-90e326401b48", "ID_FS_UUID_ENC"=>"6cb93c66-ef5f-4301-96e6-90e326401b48", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6763", "nomdmond
Oct 12 18:40:38 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.325955 #10253] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.326041 #10253] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.326081 #10253] DEBUG -- : Device dm-2 seems to be appropriate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.326121 #10253] DEBUG -- : Getting udev properties for device: dm-3
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.330425 #10253] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-dOzsKzjoCVi0hFOE99hZrPdC2eZIEmY9eqks0n921awBfekW0Pfl6VMTzpf8k3ex /dev/disk/by-uuid/8228df13-90d4-4f5b-b187-cbe06eec2c5e /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-dOzsKzjoCVi0hFOE99hZrPdC2eZIEmY9eqks0n921awBfekW0Pfl6VMTzpf8k3ex", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8228df13-90d4-4f5b-b187-cbe06eec2c5e", "ID_FS_UUID_ENC"=>"8228df13-90d4-4f5b-b187-cbe06eec2c5e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14931", "nomdmonddf"=>"1",
Oct 12 18:40:38 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.330552 #10253] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.330640 #10253] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.330681 #10253] DEBUG -- : Device dm-3 seems to be appropriate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.330723 #10253] DEBUG -- : Getting udev properties for device: dm-4
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.334768 #10253] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-3yNnyioUE6mcX0q2gnJm2CVadlO9XHOMOwokFglTaD5QJqcYnQGXCtvpWX207L81 /dev/disk/by-uuid/9bbb3a6b-f513-41a5-b7a0-883993494d8b /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-3yNnyioUE6mcX0q2gnJm2CVadlO9XHOMOwokFglTaD5QJqcYnQGXCtvpWX207L81", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9bbb3a6b-f513-41a5-b7a0-883993494d8b", "ID_FS_UUID_ENC"=>"9bbb3a6b-f513-41a5-b7a0-883993494d8b", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14660", "nomdmonddf"=>"1", "nom
Oct 12 18:40:38 node-1 nailgun-agent: dmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.334840 #10253] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.335040 #10253] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.335086 #10253] DEBUG -- : Device dm-4 seems to be appropriate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.335130 #10253] DEBUG -- : Getting udev properties for device: dm-5
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.337709 #10253] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-3yNnyioUE6mcX0q2gnJm2CVadlO9XHOMB4Jt5ENYwwmdxybKmu4vx4HBWsnAcPj4 /dev/disk/by-uuid/3fdeedaf-f735-4705-9d13-8208ba2b6107 /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-3yNnyioUE6mcX0q2gnJm2CVadlO9XHOMB4Jt5ENYwwmdxybKmu4vx4HBWsnAcPj4", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"3fdeedaf-f735-4705-9d13-8208ba2b6107", "ID_FS_UUID_ENC"=>"3fdeedaf-f735-4705-9d13-8208ba2b6107", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15270", "nomdmonddf"=>"1", "nomdmonisw
Oct 12 18:40:38 node-1 nailgun-agent: "=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.337853 #10253] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.337930 #10253] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.337965 #10253] DEBUG -- : Device dm-5 seems to be appropriate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.337999 #10253] DEBUG -- : Getting udev properties for device: ram0
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.340258 #10253] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45753", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.340329 #10253] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.340462 #10253] DEBUG -- : Device ram0 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.340510 #10253] DEBUG -- : Getting udev properties for device: ram1
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.342659 #10253] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45764", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.342749 #10253] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.342837 #10253] DEBUG -- : Device ram1 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.342897 #10253] DEBUG -- : Getting udev properties for device: ram2
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.345031 #10253] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45863", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.345090 #10253] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.345182 #10253] DEBUG -- : Device ram2 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.345246 #10253] DEBUG -- : Getting udev properties for device: ram3
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.347401 #10253] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45880", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.347452 #10253] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.347526 #10253] DEBUG -- : Device ram3 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.347572 #10253] DEBUG -- : Getting udev properties for device: ram4
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.351075 #10253] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45897", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.351150 #10253] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.351243 #10253] DEBUG -- : Device ram4 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.351305 #10253] DEBUG -- : Getting udev properties for device: ram5
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.354978 #10253] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45913", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.355094 #10253] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.355181 #10253] DEBUG -- : Device ram5 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.355223 #10253] DEBUG -- : Getting udev properties for device: ram6
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.358527 #10253] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45927", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.358582 #10253] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.358684 #10253] DEBUG -- : Device ram6 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.358724 #10253] DEBUG -- : Getting udev properties for device: ram7
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.362309 #10253] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45938", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.362411 #10253] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.362505 #10253] DEBUG -- : Device ram7 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.362557 #10253] DEBUG -- : Getting udev properties for device: ram8
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.366370 #10253] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45948", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.366442 #10253] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.366597 #10253] DEBUG -- : Device ram8 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.366650 #10253] DEBUG -- : Getting udev properties for device: ram9
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.370534 #10253] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45956", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.370609 #10253] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.370719 #10253] DEBUG -- : Device ram9 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.370774 #10253] DEBUG -- : Getting udev properties for device: loop0
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.374608 #10253] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45652", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.374720 #10253] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.374818 #10253] DEBUG -- : Device loop0 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.374888 #10253] DEBUG -- : Getting udev properties for device: loop1
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.378679 #10253] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45665", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.378772 #10253] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.378865 #10253] DEBUG -- : Device loop1 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.378962 #10253] DEBUG -- : Getting udev properties for device: loop2
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.382687 #10253] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45679", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.382819 #10253] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.382942 #10253] DEBUG -- : Device loop2 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.383002 #10253] DEBUG -- : Getting udev properties for device: loop3
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.386848 #10253] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45689", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.386931 #10253] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.387070 #10253] DEBUG -- : Device loop3 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.387126 #10253] DEBUG -- : Getting udev properties for device: loop4
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.390965 #10253] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45699", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.391035 #10253] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.391130 #10253] DEBUG -- : Device loop4 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.391227 #10253] DEBUG -- : Getting udev properties for device: loop5
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.395084 #10253] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45711", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.395154 #10253] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.395249 #10253] DEBUG -- : Device loop5 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.395327 #10253] DEBUG -- : Getting udev properties for device: loop6
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.399137 #10253] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45722", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.399242 #10253] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.399340 #10253] DEBUG -- : Device loop6 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.399392 #10253] DEBUG -- : Getting udev properties for device: loop7
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.403218 #10253] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45741", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.403287 #10253] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.403397 #10253] DEBUG -- : Device loop7 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.403474 #10253] DEBUG -- : Getting udev properties for device: ram10
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.406325 #10253] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45777", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.406399 #10253] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.406571 #10253] DEBUG -- : Device ram10 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.406627 #10253] DEBUG -- : Getting udev properties for device: ram11
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.409421 #10253] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45793", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.409526 #10253] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.409611 #10253] DEBUG -- : Device ram11 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.409687 #10253] DEBUG -- : Getting udev properties for device: ram12
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.412627 #10253] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45807", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.412707 #10253] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.412796 #10253] DEBUG -- : Device ram12 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.412844 #10253] DEBUG -- : Getting udev properties for device: ram13
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.416107 #10253] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45821", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.416203 #10253] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.416283 #10253] DEBUG -- : Device ram13 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.416351 #10253] DEBUG -- : Getting udev properties for device: ram14
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.419625 #10253] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45835", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.419702 #10253] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.419810 #10253] DEBUG -- : Device ram14 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.419875 #10253] DEBUG -- : Getting udev properties for device: ram15
Oct 12 18:40:38 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.422603 #10253] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45851", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.422665 #10253] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430394 #10253] DEBUG -- : Device ram15 removable parameter: "0"
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430495 #10253] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430533 #10253] DEBUG -- : Block device seems to be physical data storage: sda
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430607 #10253] DEBUG -- : Found block device: dm-0
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430642 #10253] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430672 #10253] DEBUG -- : Found block device: dm-1
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430699 #10253] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430722 #10253] DEBUG -- : Found block device: dm-2
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430748 #10253] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430849 #10253] DEBUG -- : Found block device: dm-3
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430903 #10253] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430933 #10253] DEBUG -- : Found block device: dm-4
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430961 #10253] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.430992 #10253] DEBUG -- : Found block device: dm-5
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431005 #10253] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431015 #10253] DEBUG -- : Found block device: ram0
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431028 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431039 #10253] DEBUG -- : Found block device: ram1
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431051 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431113 #10253] DEBUG -- : Found block device: ram2
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431126 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431136 #10253] DEBUG -- : Found block device: ram3
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431147 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431156 #10253] DEBUG -- : Found block device: ram4
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431169 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431179 #10253] DEBUG -- : Found block device: ram5
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431191 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431201 #10253] DEBUG -- : Found block device: ram6
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431264 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431276 #10253] DEBUG -- : Found block device: ram7
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431287 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431296 #10253] DEBUG -- : Found block device: ram8
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431308 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431317 #10253] DEBUG -- : Found block device: ram9
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431328 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431337 #10253] DEBUG -- : Found block device: loop0
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431348 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431398 #10253] DEBUG -- : Found block device: loop1
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431412 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431422 #10253] DEBUG -- : Found block device: loop2
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431436 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431446 #10253] DEBUG -- : Found block device: loop3
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431458 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431467 #10253] DEBUG -- : Found block device: loop4
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431479 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431489 #10253] DEBUG -- : Found block device: loop5
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431500 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431551 #10253] DEBUG -- : Found block device: loop6
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431563 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431573 #10253] DEBUG -- : Found block device: loop7
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431584 #10253] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431594 #10253] DEBUG -- : Found block device: ram10
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431606 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431615 #10253] DEBUG -- : Found block device: ram11
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431628 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431637 #10253] DEBUG -- : Found block device: ram12
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431694 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431706 #10253] DEBUG -- : Found block device: ram13
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431718 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431728 #10253] DEBUG -- : Found block device: ram14
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431739 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431748 #10253] DEBUG -- : Found block device: ram15
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431760 #10253] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.431794 #10253] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct 12 18:40:38 node-1 nailgun-agent: D, [2016-10-12T18:40:38.645401 #10253] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 12 18:40:38 node-1 nailgun-agent: I, [2016-10-12T18:40:38.645779 #10253]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 12 18:40:56 node-1 puppet-user[14416]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 12 18:40:56 node-1 puppet-user[14416]: Finished catalog run in 29.73 seconds
Oct 12 18:40:58 node-1 puppet-user[17029]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 12 18:40:59 node-1 puppet-user[17029]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Oct 12 18:40:59 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 12 18:40:59 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 12 18:40:59 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 12 18:40:59 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 12 18:40:59 node-1 puppet-user[17029]: Finished catalog run in 0.09 seconds
Oct 12 18:41:01 node-1 puppet-user[17492]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 12 18:41:01 node-1 CRON[17905]: (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 12 18:41:02 node-1 puppet-user[17492]: Compiled catalog for node-1.domain.tld in environment production in 0.93 seconds
Oct 12 18:41:02 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 12 18:41:02 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 12 18:41:02 node-1 crontab[17940]: (root) LIST (root)
Oct 12 18:41:02 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 12 18:41:02 node-1 crontab[17941]: (root) REPLACE (root)
Oct 12 18:41:02 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 12 18:41:02 node-1 nailgun-agent: I, [2016-10-12T18:41:02.830151 #17908]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 12 18:41:03 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/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 12 18:41:04 node-1 puppet-user[17492]: (/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 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/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 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/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 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/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 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 12 18:41:04 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 12 18:41:05 node-1 puppet-user[17492]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 12 18:41:05 node-1 puppet-user[17492]: (/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 12 18:41:05 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8381" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 12 18:41:05 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 12 18:41:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:19 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:19 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:19 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:19 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:19 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:21 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:21 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:21 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:21 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:21 node-1 multipathd: uevent trigger error
<27>Oct 12 18:41:21 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:16 node-1 ntpdate[28823]: no servers can be used, exiting
<27>Oct 12 18:42:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:42:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:02 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:02 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:02 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:02 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:02 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:05 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:05 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:05 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:05 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:43:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:10 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 12 18:44:10 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 12 18:44:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 12 18:44:16 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 12 18:44:21 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 12 18:44:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 12 18:44:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 12 18:44:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:37 node-1 ntpdate[14279]: the NTP socket is in use, exiting
<27>Oct 12 18:44:37 node-1 ntpdate[14332]: the NTP socket is in use, exiting
<27>Oct 12 18:44:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:47 node-1 multipathd: uevent trigger error
<129>Oct 12 18:44:49 node-1 haproxy[16752]: 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 12 18:44:49 node-1 haproxy[16752]: Backup Server mysqld/node-3 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 12 18:44:50 node-1 haproxy[16760]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:44:50 node-1 haproxy[16760]: proxy mysqld has no server available!
<27>Oct 12 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:56 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:56 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:56 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:56 node-1 multipathd: uevent trigger error
<27>Oct 12 18:44:56 node-1 multipathd: uevent trigger error
<129>Oct 12 18:44:58 node-1 haproxy[19276]: 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 12 18:44:59 node-1 haproxy[19298]: Backup Server mysqld/node-3 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 12 18:44:59 node-1 haproxy[19298]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:44:59 node-1 haproxy[19298]: proxy mysqld has no server available!
<129>Oct 12 18:44:59 node-1 haproxy[19298]: 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 12 18:45:00 node-1 haproxy[19298]: Server object-storage/node-3 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 12 18:45:00 node-1 haproxy[19298]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:00 node-1 haproxy[19298]: proxy object-storage has no server available!
<27>Oct 12 18:45:01 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:01 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:01 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:01 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:01 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:03 node-1 haproxy[20651]: 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 12 18:45:04 node-1 haproxy[20655]: Server neutron/node-3 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 12 18:45:04 node-1 haproxy[20655]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:04 node-1 haproxy[20655]: proxy neutron has no server available!
<129>Oct 12 18:45:04 node-1 haproxy[20655]: 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 12 18:45:04 node-1 haproxy[20655]: Backup Server mysqld/node-3 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 12 18:45:05 node-1 haproxy[20655]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:05 node-1 haproxy[20655]: proxy mysqld has no server available!
<129>Oct 12 18:45:05 node-1 haproxy[20655]: 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 12 18:45:05 node-1 haproxy[20655]: Server object-storage/node-3 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 12 18:45:05 node-1 haproxy[20655]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:05 node-1 haproxy[20655]: proxy object-storage has no server available!
<27>Oct 12 18:45:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:07 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:09 node-1 haproxy[22167]: 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 12 18:45:09 node-1 haproxy[22167]: Server keystone-1/node-3 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 12 18:45:09 node-1 haproxy[22167]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:09 node-1 haproxy[22167]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:09 node-1 haproxy[22167]: 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 12 18:45:10 node-1 haproxy[22171]: Server keystone-2/node-3 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 12 18:45:10 node-1 haproxy[22171]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:10 node-1 haproxy[22171]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:10 node-1 haproxy[22171]: 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 12 18:45:10 node-1 haproxy[22171]: Server neutron/node-3 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 12 18:45:10 node-1 haproxy[22171]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:10 node-1 haproxy[22171]: proxy neutron has no server available!
<129>Oct 12 18:45:10 node-1 haproxy[22171]: 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 12 18:45:10 node-1 haproxy[22171]: Backup Server mysqld/node-3 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 12 18:45:11 node-1 haproxy[22171]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:11 node-1 haproxy[22171]: proxy mysqld has no server available!
<129>Oct 12 18:45:11 node-1 haproxy[22171]: 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 12 18:45:11 node-1 haproxy[22171]: Server object-storage/node-3 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 12 18:45:11 node-1 haproxy[22171]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:11 node-1 haproxy[22171]: proxy object-storage has no server available!
<27>Oct 12 18:45:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:12 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:14 node-1 haproxy[23496]: 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 12 18:45:14 node-1 haproxy[23496]: Server keystone-1/node-3 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 12 18:45:14 node-1 haproxy[23496]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:14 node-1 haproxy[23496]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:15 node-1 haproxy[23500]: 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 12 18:45:15 node-1 haproxy[23500]: Server keystone-2/node-3 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 12 18:45:15 node-1 haproxy[23500]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:15 node-1 haproxy[23500]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:15 node-1 haproxy[23500]: 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 12 18:45:15 node-1 haproxy[23500]: Server neutron/node-3 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 12 18:45:15 node-1 haproxy[23500]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:15 node-1 haproxy[23500]: proxy neutron has no server available!
<129>Oct 12 18:45:15 node-1 haproxy[23500]: 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 12 18:45:15 node-1 haproxy[23500]: Backup Server mysqld/node-3 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 12 18:45:15 node-1 haproxy[23500]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:15 node-1 haproxy[23500]: proxy mysqld has no server available!
<129>Oct 12 18:45:16 node-1 haproxy[23500]: 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 12 18:45:16 node-1 haproxy[23500]: Server object-storage/node-3 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 12 18:45:16 node-1 haproxy[23500]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:16 node-1 haproxy[23500]: proxy object-storage has no server available!
<129>Oct 12 18:45:16 node-1 haproxy[23500]: 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 12 18:45:16 node-1 haproxy[23500]: Server aodh/node-3 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 12 18:45:16 node-1 haproxy[23500]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:16 node-1 haproxy[23500]: proxy aodh has no server available!
<27>Oct 12 18:45:17 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:17 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:17 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:17 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:17 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:20 node-1 haproxy[25044]: 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 12 18:45:20 node-1 haproxy[25044]: Server keystone-1/node-3 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 12 18:45:20 node-1 haproxy[25044]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:20 node-1 haproxy[25044]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:20 node-1 haproxy[25044]: 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 12 18:45:20 node-1 haproxy[25044]: Server keystone-2/node-3 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 12 18:45:20 node-1 haproxy[25044]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:20 node-1 haproxy[25044]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:20 node-1 haproxy[25044]: 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 12 18:45:20 node-1 haproxy[25044]: Server neutron/node-3 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 12 18:45:20 node-1 haproxy[25044]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:20 node-1 haproxy[25044]: proxy neutron has no server available!
<129>Oct 12 18:45:21 node-1 haproxy[25048]: 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 12 18:45:21 node-1 haproxy[25048]: Backup Server mysqld/node-3 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 12 18:45:21 node-1 haproxy[25048]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:21 node-1 haproxy[25048]: proxy mysqld has no server available!
<129>Oct 12 18:45:21 node-1 haproxy[25048]: 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 12 18:45:21 node-1 haproxy[25048]: Server object-storage/node-3 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 12 18:45:21 node-1 haproxy[25048]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:21 node-1 haproxy[25048]: proxy object-storage has no server available!
<129>Oct 12 18:45:21 node-1 haproxy[25048]: 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 12 18:45:21 node-1 haproxy[25048]: Server aodh/node-3 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 12 18:45:21 node-1 haproxy[25048]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:21 node-1 haproxy[25048]: proxy aodh has no server available!
<129>Oct 12 18:45:21 node-1 haproxy[25048]: 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 12 18:45:21 node-1 haproxy[25048]: Server ceilometer/node-3 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 12 18:45:22 node-1 haproxy[25048]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:22 node-1 haproxy[25048]: proxy ceilometer has no server available!
<27>Oct 12 18:45:23 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:23 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:23 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:23 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:23 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:25 node-1 haproxy[26432]: 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 12 18:45:25 node-1 haproxy[26432]: Server keystone-1/node-3 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 12 18:45:26 node-1 haproxy[26438]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:26 node-1 haproxy[26438]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:26 node-1 haproxy[26438]: 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 12 18:45:26 node-1 haproxy[26438]: Server keystone-2/node-3 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 12 18:45:26 node-1 haproxy[26438]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:26 node-1 haproxy[26438]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:26 node-1 haproxy[26438]: 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 12 18:45:26 node-1 haproxy[26438]: Server neutron/node-3 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 12 18:45:26 node-1 haproxy[26438]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:26 node-1 haproxy[26438]: proxy neutron has no server available!
<129>Oct 12 18:45:26 node-1 haproxy[26438]: 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 12 18:45:26 node-1 haproxy[26438]: Backup Server mysqld/node-3 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 12 18:45:26 node-1 haproxy[26438]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:26 node-1 haproxy[26438]: proxy mysqld has no server available!
<129>Oct 12 18:45:27 node-1 haproxy[26438]: 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 12 18:45:27 node-1 haproxy[26438]: Server object-storage/node-3 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 12 18:45:27 node-1 haproxy[26438]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:27 node-1 haproxy[26438]: proxy object-storage has no server available!
<129>Oct 12 18:45:27 node-1 haproxy[26438]: 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 12 18:45:27 node-1 haproxy[26438]: Server aodh/node-3 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 12 18:45:27 node-1 haproxy[26438]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:27 node-1 haproxy[26438]: proxy aodh has no server available!
<129>Oct 12 18:45:27 node-1 haproxy[26438]: 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 12 18:45:27 node-1 haproxy[26438]: Server ceilometer/node-3 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 12 18:45:27 node-1 haproxy[26438]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:27 node-1 haproxy[26438]: proxy ceilometer has no server available!
<27>Oct 12 18:45:28 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:28 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:28 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:28 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:28 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:31 node-1 haproxy[27790]: 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 12 18:45:31 node-1 haproxy[27790]: Server horizon/node-3 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 12 18:45:31 node-1 haproxy[27790]: 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 12 18:45:31 node-1 haproxy[27790]: Server keystone-1/node-3 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 12 18:45:31 node-1 haproxy[27790]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:31 node-1 haproxy[27790]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:31 node-1 haproxy[27790]: 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 12 18:45:31 node-1 haproxy[27790]: Server keystone-2/node-3 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 12 18:45:31 node-1 haproxy[27790]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:31 node-1 haproxy[27790]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:31 node-1 haproxy[27790]: 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 12 18:45:31 node-1 haproxy[27790]: Server neutron/node-3 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 12 18:45:32 node-1 haproxy[27800]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:32 node-1 haproxy[27800]: proxy neutron has no server available!
<129>Oct 12 18:45:32 node-1 haproxy[27800]: 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 12 18:45:32 node-1 haproxy[27800]: Backup Server mysqld/node-3 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 12 18:45:32 node-1 haproxy[27800]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:32 node-1 haproxy[27800]: proxy mysqld has no server available!
<129>Oct 12 18:45:32 node-1 haproxy[27800]: 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 12 18:45:32 node-1 haproxy[27800]: Server object-storage/node-3 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 12 18:45:32 node-1 haproxy[27800]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:32 node-1 haproxy[27800]: proxy object-storage has no server available!
<129>Oct 12 18:45:32 node-1 haproxy[27800]: 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 12 18:45:32 node-1 haproxy[27800]: Server aodh/node-3 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 12 18:45:32 node-1 haproxy[27800]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:32 node-1 haproxy[27800]: proxy aodh has no server available!
<129>Oct 12 18:45:32 node-1 haproxy[27800]: 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 12 18:45:32 node-1 haproxy[27800]: Server ceilometer/node-3 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 12 18:45:33 node-1 haproxy[27800]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:33 node-1 haproxy[27800]: proxy ceilometer has no server available!
<27>Oct 12 18:45:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:34 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:34 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:37 node-1 haproxy[29180]: 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 12 18:45:37 node-1 haproxy[29180]: Server horizon/node-3 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 12 18:45:37 node-1 haproxy[29180]: 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 12 18:45:37 node-1 haproxy[29180]: Server keystone-1/node-3 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 12 18:45:37 node-1 haproxy[29180]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:37 node-1 haproxy[29180]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:37 node-1 haproxy[29180]: 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 12 18:45:37 node-1 haproxy[29180]: Server keystone-2/node-3 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 12 18:45:37 node-1 haproxy[29180]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:37 node-1 haproxy[29180]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:37 node-1 haproxy[29180]: 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 12 18:45:37 node-1 haproxy[29180]: Server glance-api/node-3 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 12 18:45:37 node-1 haproxy[29180]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:37 node-1 haproxy[29180]: proxy glance-api has no server available!
<129>Oct 12 18:45:37 node-1 haproxy[29180]: 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 12 18:45:37 node-1 haproxy[29180]: Server glance-glare/node-3 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 12 18:45:37 node-1 haproxy[29180]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:37 node-1 haproxy[29180]: proxy glance-glare has no server available!
<129>Oct 12 18:45:38 node-1 haproxy[29184]: 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 12 18:45:38 node-1 haproxy[29184]: Server neutron/node-3 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 12 18:45:38 node-1 haproxy[29184]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:38 node-1 haproxy[29184]: proxy neutron has no server available!
<129>Oct 12 18:45:38 node-1 haproxy[29184]: 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 12 18:45:38 node-1 haproxy[29184]: Server glance-registry/node-3 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 12 18:45:38 node-1 haproxy[29184]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:38 node-1 haproxy[29184]: proxy glance-registry has no server available!
<129>Oct 12 18:45:38 node-1 haproxy[29184]: 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 12 18:45:38 node-1 haproxy[29184]: Backup Server mysqld/node-3 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 12 18:45:38 node-1 haproxy[29184]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:38 node-1 haproxy[29184]: proxy mysqld has no server available!
<129>Oct 12 18:45:38 node-1 haproxy[29184]: 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 12 18:45:38 node-1 haproxy[29184]: Server object-storage/node-3 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 12 18:45:38 node-1 haproxy[29184]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:38 node-1 haproxy[29184]: proxy object-storage has no server available!
<129>Oct 12 18:45:38 node-1 haproxy[29184]: 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 12 18:45:38 node-1 haproxy[29184]: Server aodh/node-3 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 12 18:45:38 node-1 haproxy[29184]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:38 node-1 haproxy[29184]: proxy aodh has no server available!
<129>Oct 12 18:45:38 node-1 haproxy[29184]: 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 12 18:45:38 node-1 haproxy[29184]: Server ceilometer/node-3 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 12 18:45:39 node-1 haproxy[29184]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:39 node-1 haproxy[29184]: proxy ceilometer has no server available!
<27>Oct 12 18:45:40 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:40 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:40 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:40 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:40 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:42 node-1 haproxy[30582]: 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 12 18:45:43 node-1 haproxy[30586]: Server horizon/node-3 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 12 18:45:43 node-1 haproxy[30586]: 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 12 18:45:43 node-1 haproxy[30586]: Server keystone-1/node-3 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 12 18:45:43 node-1 haproxy[30586]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:43 node-1 haproxy[30586]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:43 node-1 haproxy[30586]: 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 12 18:45:43 node-1 haproxy[30586]: Server keystone-2/node-3 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 12 18:45:43 node-1 haproxy[30586]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:43 node-1 haproxy[30586]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:43 node-1 haproxy[30586]: 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 12 18:45:43 node-1 haproxy[30586]: Server nova-api/node-3 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 12 18:45:43 node-1 haproxy[30586]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:43 node-1 haproxy[30586]: proxy nova-api has no server available!
<129>Oct 12 18:45:43 node-1 haproxy[30586]: 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 12 18:45:43 node-1 haproxy[30586]: Server nova-metadata-api/node-3 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 12 18:45:43 node-1 haproxy[30586]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:43 node-1 haproxy[30586]: proxy nova-metadata-api has no server available!
<129>Oct 12 18:45:43 node-1 haproxy[30586]: 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 12 18:45:43 node-1 haproxy[30586]: Server glance-api/node-3 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 12 18:45:43 node-1 haproxy[30586]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:43 node-1 haproxy[30586]: proxy glance-api has no server available!
<129>Oct 12 18:45:43 node-1 haproxy[30586]: 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 12 18:45:43 node-1 haproxy[30586]: Server glance-glare/node-3 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 12 18:45:43 node-1 haproxy[30586]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:43 node-1 haproxy[30586]: proxy glance-glare has no server available!
<129>Oct 12 18:45:43 node-1 haproxy[30586]: 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 12 18:45:44 node-1 haproxy[30586]: Server neutron/node-3 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 12 18:45:44 node-1 haproxy[30586]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:44 node-1 haproxy[30586]: proxy neutron has no server available!
<129>Oct 12 18:45:44 node-1 haproxy[30586]: 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 12 18:45:44 node-1 haproxy[30586]: Server glance-registry/node-3 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 12 18:45:44 node-1 haproxy[30586]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:44 node-1 haproxy[30586]: proxy glance-registry has no server available!
<129>Oct 12 18:45:44 node-1 haproxy[30586]: 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 12 18:45:44 node-1 haproxy[30586]: Backup Server mysqld/node-3 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 12 18:45:44 node-1 haproxy[30586]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:44 node-1 haproxy[30586]: proxy mysqld has no server available!
<129>Oct 12 18:45:44 node-1 haproxy[30586]: 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 12 18:45:44 node-1 haproxy[30586]: Server object-storage/node-3 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 12 18:45:44 node-1 haproxy[30586]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:44 node-1 haproxy[30586]: proxy object-storage has no server available!
<129>Oct 12 18:45:44 node-1 haproxy[30586]: 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 12 18:45:44 node-1 haproxy[30586]: Server aodh/node-3 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 12 18:45:44 node-1 haproxy[30586]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:44 node-1 haproxy[30586]: proxy aodh has no server available!
<129>Oct 12 18:45:44 node-1 haproxy[30586]: 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 12 18:45:44 node-1 haproxy[30586]: Server ceilometer/node-3 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 12 18:45:44 node-1 haproxy[30586]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:44 node-1 haproxy[30586]: proxy ceilometer has no server available!
<129>Oct 12 18:45:44 node-1 haproxy[30586]: 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 12 18:45:44 node-1 haproxy[30586]: Server nova-novncproxy/node-3 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 12 18:45:44 node-1 haproxy[30586]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:44 node-1 haproxy[30586]: proxy nova-novncproxy has no server available!
<27>Oct 12 18:45:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:46 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:48 node-1 haproxy[31907]: 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 12 18:45:48 node-1 haproxy[31907]: Server horizon/node-3 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 12 18:45:48 node-1 haproxy[31907]: 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 12 18:45:48 node-1 haproxy[31907]: Server keystone-1/node-3 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 12 18:45:48 node-1 haproxy[31907]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:48 node-1 haproxy[31907]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:48 node-1 haproxy[31907]: 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 12 18:45:48 node-1 haproxy[31907]: Server keystone-2/node-3 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 12 18:45:48 node-1 haproxy[31907]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:48 node-1 haproxy[31907]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:48 node-1 haproxy[31907]: 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 12 18:45:48 node-1 haproxy[31907]: Server nova-api/node-3 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 12 18:45:48 node-1 haproxy[31907]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:48 node-1 haproxy[31907]: proxy nova-api has no server available!
<129>Oct 12 18:45:48 node-1 haproxy[31907]: 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 12 18:45:49 node-1 haproxy[31911]: Server nova-metadata-api/node-3 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 12 18:45:49 node-1 haproxy[31911]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:49 node-1 haproxy[31911]: proxy nova-metadata-api has no server available!
<129>Oct 12 18:45:49 node-1 haproxy[31911]: 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 12 18:45:49 node-1 haproxy[31911]: Backup Server cinder-api/node-3 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 12 18:45:49 node-1 haproxy[31911]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:49 node-1 haproxy[31911]: proxy cinder-api has no server available!
<129>Oct 12 18:45:49 node-1 haproxy[31911]: 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 12 18:45:49 node-1 haproxy[31911]: Server glance-api/node-3 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 12 18:45:49 node-1 haproxy[31911]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:49 node-1 haproxy[31911]: proxy glance-api has no server available!
<129>Oct 12 18:45:49 node-1 haproxy[31911]: 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 12 18:45:49 node-1 haproxy[31911]: Server glance-glare/node-3 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 12 18:45:49 node-1 haproxy[31911]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:49 node-1 haproxy[31911]: proxy glance-glare has no server available!
<129>Oct 12 18:45:49 node-1 haproxy[31911]: 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 12 18:45:49 node-1 haproxy[31911]: Server neutron/node-3 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 12 18:45:49 node-1 haproxy[31911]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:49 node-1 haproxy[31911]: proxy neutron has no server available!
<129>Oct 12 18:45:49 node-1 haproxy[31911]: 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 12 18:45:49 node-1 haproxy[31911]: Server glance-registry/node-3 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 12 18:45:49 node-1 haproxy[31911]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:49 node-1 haproxy[31911]: proxy glance-registry has no server available!
<129>Oct 12 18:45:49 node-1 haproxy[31911]: 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 12 18:45:49 node-1 haproxy[31911]: Backup Server mysqld/node-3 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 12 18:45:49 node-1 haproxy[31911]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:49 node-1 haproxy[31911]: proxy mysqld has no server available!
<129>Oct 12 18:45:49 node-1 haproxy[31911]: 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 12 18:45:49 node-1 haproxy[31911]: Server object-storage/node-3 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 12 18:45:50 node-1 haproxy[31911]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:50 node-1 haproxy[31911]: proxy object-storage has no server available!
<129>Oct 12 18:45:50 node-1 haproxy[31911]: 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 12 18:45:50 node-1 haproxy[31911]: Server aodh/node-3 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 12 18:45:50 node-1 haproxy[31911]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:50 node-1 haproxy[31911]: proxy aodh has no server available!
<129>Oct 12 18:45:50 node-1 haproxy[31911]: 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 12 18:45:50 node-1 haproxy[31911]: Server ceilometer/node-3 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 12 18:45:50 node-1 haproxy[31911]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:50 node-1 haproxy[31911]: proxy ceilometer has no server available!
<129>Oct 12 18:45:50 node-1 haproxy[31911]: 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 12 18:45:50 node-1 haproxy[31911]: Server nova-novncproxy/node-3 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 12 18:45:50 node-1 haproxy[31911]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:50 node-1 haproxy[31911]: proxy nova-novncproxy has no server available!
<27>Oct 12 18:45:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:51 node-1 multipathd: uevent trigger error
<129>Oct 12 18:45:54 node-1 haproxy[848]: 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 12 18:45:54 node-1 haproxy[848]: Server horizon/node-3 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 12 18:45:54 node-1 haproxy[848]: 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 12 18:45:54 node-1 haproxy[848]: Server keystone-1/node-3 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 12 18:45:54 node-1 haproxy[848]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:54 node-1 haproxy[848]: proxy keystone-1 has no server available!
<129>Oct 12 18:45:54 node-1 haproxy[848]: 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 12 18:45:54 node-1 haproxy[848]: Server keystone-2/node-3 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 12 18:45:54 node-1 haproxy[848]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:54 node-1 haproxy[848]: proxy keystone-2 has no server available!
<129>Oct 12 18:45:54 node-1 haproxy[848]: 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 12 18:45:54 node-1 haproxy[848]: Server nova-api/node-3 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 12 18:45:54 node-1 haproxy[848]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:54 node-1 haproxy[848]: proxy nova-api has no server available!
<129>Oct 12 18:45:54 node-1 haproxy[848]: 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 12 18:45:54 node-1 haproxy[848]: Server nova-metadata-api/node-3 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 12 18:45:54 node-1 haproxy[848]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:54 node-1 haproxy[848]: proxy nova-metadata-api has no server available!
<129>Oct 12 18:45:54 node-1 haproxy[848]: 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 12 18:45:54 node-1 haproxy[848]: Backup Server cinder-api/node-3 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 12 18:45:54 node-1 haproxy[848]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:54 node-1 haproxy[848]: proxy cinder-api has no server available!
<129>Oct 12 18:45:54 node-1 haproxy[848]: 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 12 18:45:54 node-1 haproxy[848]: Server glance-api/node-3 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 12 18:45:55 node-1 haproxy[855]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy glance-api has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server glance-glare/node-3 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 12 18:45:55 node-1 haproxy[855]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy glance-glare has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server neutron/node-3 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 12 18:45:55 node-1 haproxy[855]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy neutron has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server glance-registry/node-3 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 12 18:45:55 node-1 haproxy[855]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy glance-registry has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Backup Server mysqld/node-3 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 12 18:45:55 node-1 haproxy[855]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy mysqld has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server object-storage/node-3 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 12 18:45:55 node-1 haproxy[855]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy object-storage has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server aodh/node-3 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 12 18:45:55 node-1 haproxy[855]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy aodh has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server ceilometer/node-3 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 12 18:45:55 node-1 haproxy[855]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy ceilometer has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server heat-api/node-3 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 12 18:45:55 node-1 haproxy[855]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:55 node-1 haproxy[855]: proxy heat-api has no server available!
<129>Oct 12 18:45:55 node-1 haproxy[855]: 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 12 18:45:55 node-1 haproxy[855]: Server heat-api-cfn/node-3 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 12 18:45:56 node-1 haproxy[855]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:56 node-1 haproxy[855]: proxy heat-api-cfn has no server available!
<129>Oct 12 18:45:56 node-1 haproxy[855]: 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 12 18:45:56 node-1 haproxy[855]: Server heat-api-cloudwatch/node-3 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 12 18:45:56 node-1 haproxy[855]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:56 node-1 haproxy[855]: proxy heat-api-cloudwatch has no server available!
<129>Oct 12 18:45:56 node-1 haproxy[855]: 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 12 18:45:56 node-1 haproxy[855]: Server nova-novncproxy/node-3 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 12 18:45:56 node-1 haproxy[855]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 12 18:45:56 node-1 haproxy[855]: proxy nova-novncproxy has no server available!
<27>Oct 12 18:45:57 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:57 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:57 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:57 node-1 multipathd: uevent trigger error
<27>Oct 12 18:45:57 node-1 multipathd: uevent trigger error
<27>Oct 12 18:46:00 node-1 multipathd: uevent trigger error
<27>Oct 12 18:46:00 node-1 multipathd: uevent trigger error
<27>Oct 12 18:46:00 node-1 multipathd: uevent trigger error
<27>Oct 12 18:46:00 node-1 multipathd: uevent trigger error
<27>Oct 12 18:46:00 node-1 multipathd: uevent trigger error
<27>Oct 12 18:46:08 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 12 18:46:32 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 12 18:46:34 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 12 18:47:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 18:47:04 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 12 18:47:25 node-1 multipathd: uevent trigger error
<27>Oct 12 18:47:25 node-1 multipathd: uevent trigger error
<27>Oct 12 18:47:25 node-1 multipathd: uevent trigger error
<27>Oct 12 18:47:25 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:43 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:43 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:43 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:43 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:43 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:49:48 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 12 18:50:06 node-1 apache2_error [Wed Oct 12 18:50:00.016125 2016] [mpm_event:notice] [pid 8818:tid 139683077560192] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 12 18:50:06 node-1 apache2_error [Wed Oct 12 18:50:00.016208 2016] [core:notice] [pid 8818:tid 139683077560192] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 12 18:50:06 node-1 apache2_error [Wed Oct 12 18:50:01.910703 2016] [mpm_event:notice] [pid 8818:tid 139683077560192] AH00491: caught SIGTERM, shutting down
<43>Oct 12 18:50:06 node-1 apache2_error [Wed Oct 12 18:50:03.022783 2016] [mpm_worker:notice] [pid 10431:tid 139628843562880] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 12 18:50:06 node-1 apache2_error [Wed Oct 12 18:50:03.022848 2016] [core:notice] [pid 10431:tid 139628843562880] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 12 18:50:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:07 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:15 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:15 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:15 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:15 node-1 multipathd: uevent trigger error
<27>Oct 12 18:50:15 node-1 multipathd: uevent trigger error
<43>Oct 12 18:51:26 node-1 apache2_error [Wed Oct 12 18:51:17.764811 2016] [mpm_worker:notice] [pid 10431:tid 139628843562880] AH00295: caught SIGTERM, shutting down
<43>Oct 12 18:51:26 node-1 apache2_error [Wed Oct 12 18:51:18.524867 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 12 18:51:26 node-1 apache2_error [Wed Oct 12 18:51:18.524910 2016] [core:notice] [pid 23330:tid 140175599155072] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 12 18:52:06 node-1 apache2_error [Wed Oct 12 18:52:02.494170 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 12 18:52:06 node-1 apache2_error [Wed Oct 12 18:52:02.690155 2016] [mpm_worker:warn] [pid 23330:tid 140175599155072] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 12 18:52:06 node-1 apache2_error [Wed Oct 12 18:52:02.693056 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 12 18:52:06 node-1 apache2_error [Wed Oct 12 18:52:02.693074 2016] [core:notice] [pid 23330:tid 140175599155072] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 12 18:52:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:46 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:52:51 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:06 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:06 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:06 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:06 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:06 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 18:53:24 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:24 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:24 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:24 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:25 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:29 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:29 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:29 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:29 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:29 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:53:47 node-1 multipathd: uevent trigger error
<27>Oct 12 18:54:36 node-1 multipathd: uevent trigger error
<27>Oct 12 18:54:36 node-1 multipathd: uevent trigger error
<27>Oct 12 18:54:36 node-1 multipathd: uevent trigger error
<27>Oct 12 18:54:36 node-1 multipathd: uevent trigger error
<27>Oct 12 18:54:36 node-1 multipathd: uevent trigger error
<27>Oct 12 18:55:49 node-1 multipathd: uevent trigger error
<27>Oct 12 18:55:49 node-1 multipathd: uevent trigger error
<27>Oct 12 18:55:49 node-1 multipathd: uevent trigger error
<27>Oct 12 18:55:49 node-1 multipathd: uevent trigger error
<27>Oct 12 18:55:49 node-1 multipathd: uevent trigger error
<27>Oct 12 18:56:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 18:56:45 node-1 multipathd: uevent trigger error
<27>Oct 12 18:56:45 node-1 multipathd: uevent trigger error
<27>Oct 12 18:56:45 node-1 multipathd: uevent trigger error
<27>Oct 12 18:56:45 node-1 multipathd: uevent trigger error
<27>Oct 12 18:56:45 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:12 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:18 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:18 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:18 node-1 multipathd: uevent trigger error
<27>Oct 12 18:57:18 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 18:59:38 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:38 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:38 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:38 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:38 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:53 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:53 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:53 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:53 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:53 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:53 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:58 node-1 multipathd: uevent trigger error
<27>Oct 12 18:59:58 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:00:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:06 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:06 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:06 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:06 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:06 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:52 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:52 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:53 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:53 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:53 node-1 multipathd: uevent trigger error
<27>Oct 12 19:01:59 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct 12 19:01:59 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct 12 19:02:00 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct 12 19:02:00 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct 12 19:02:01 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct 12 19:02:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:02 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:02 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:14 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:14 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:14 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:14 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:14 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 19:02:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:02:45 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 19:05:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:40 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:40 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:40 node-1 multipathd: uevent trigger error
<27>Oct 12 19:05:40 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:12 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:12 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:12 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:12 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:28 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:32 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:32 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:32 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:32 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:32 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:06:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:07:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:07:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:07:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:07:24 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 19:08:33 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:33 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:33 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:33 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:33 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:49 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:49 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:49 node-1 multipathd: uevent trigger error
<27>Oct 12 19:08:49 node-1 multipathd: uevent trigger error
<11>Oct 12 19:09:02 node-1 liberasurecode[8924]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:02 node-1 liberasurecode[8924]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:02 node-1 liberasurecode[8924]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:02 node-1 liberasurecode[8924]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:02 node-1 liberasurecode[8951]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:02 node-1 liberasurecode[8951]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:02 node-1 liberasurecode[8951]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:02 node-1 liberasurecode[8951]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:04 node-1 liberasurecode[9545]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:04 node-1 liberasurecode[9545]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:04 node-1 liberasurecode[9545]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:04 node-1 liberasurecode[9545]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11458]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11458]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11458]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11458]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11516]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11516]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11516]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11516]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11580]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11580]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11580]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:08 node-1 liberasurecode[11580]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11658]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11658]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11658]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11658]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11672]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11672]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11672]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11672]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11684]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11684]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11684]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11684]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11701]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11701]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11701]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:09 node-1 liberasurecode[11701]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:26 node-1 liberasurecode[12757]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:26 node-1 liberasurecode[12757]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:26 node-1 liberasurecode[12757]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:09:26 node-1 liberasurecode[12757]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 12 19:09:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:09:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:09:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:09:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:09:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:09:34 node-1 multipathd: uevent trigger error
<11>Oct 12 19:10:02 node-1 liberasurecode[18115]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:10:02 node-1 liberasurecode[18115]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:10:02 node-1 liberasurecode[18115]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:10:02 node-1 liberasurecode[18115]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Oct 12 19:10:27 node-1 apache2_error [Wed Oct 12 19:10:20.167819 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 12 19:10:27 node-1 apache2_error [Wed Oct 12 19:10:20.551141 2016] [mpm_worker:warn] [pid 23330:tid 140175599155072] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 12 19:10:27 node-1 apache2_error [Wed Oct 12 19:10:20.555925 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 12 19:10:27 node-1 apache2_error [Wed Oct 12 19:10:20.555957 2016] [core:notice] [pid 23330:tid 140175599155072] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 12 19:10:57 node-1 apache2_error [Wed Oct 12 19:10:57.550057 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 12 19:10:57 node-1 apache2_error [Wed Oct 12 19:10:57.746309 2016] [mpm_worker:warn] [pid 23330:tid 140175599155072] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 12 19:10:57 node-1 apache2_error [Wed Oct 12 19:10:57.754442 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 12 19:10:57 node-1 apache2_error [Wed Oct 12 19:10:57.754468 2016] [core:notice] [pid 23330:tid 140175599155072] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 12 19:11:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:01 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:09 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:09 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:09 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:09 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:09 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 12 19:11:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:47 node-1 multipathd: uevent trigger error
<43>Oct 12 19:11:47 node-1 apache2_error [Wed Oct 12 19:11:43.675646 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 12 19:11:47 node-1 apache2_error [Wed Oct 12 19:11:43.870379 2016] [mpm_worker:warn] [pid 23330:tid 140175599155072] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 12 19:11:47 node-1 apache2_error [Wed Oct 12 19:11:43.877381 2016] [mpm_worker:notice] [pid 23330:tid 140175599155072] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 12 19:11:47 node-1 apache2_error [Wed Oct 12 19:11:43.877401 2016] [core:notice] [pid 23330:tid 140175599155072] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 12 19:11:53 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:54 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:54 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:54 node-1 multipathd: uevent trigger error
<27>Oct 12 19:11:59 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:00 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:00 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:00 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:00 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:19 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:19 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:19 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:19 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:19 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:40 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:47 node-1 multipathd: uevent trigger error
<27>Oct 12 19:12:54 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 12 19:13:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:03 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:08 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:08 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:08 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:08 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:08 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:13 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:13 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:13 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:13 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:13 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:25 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:25 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:25 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:25 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:25 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:25 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 12 19:13:30 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:30 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:30 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:30 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:30 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:57 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:57 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:57 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:57 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:57 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:57 node-1 multipathd: uevent trigger error
<27>Oct 12 19:13:57 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:10 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:10 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:10 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:10 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:10 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:17 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:17 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:17 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:17 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:17 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:22 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:22 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:22 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:22 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:22 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:34 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:38 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:38 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:39 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:43 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:43 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:43 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:43 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:43 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:48 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:48 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:48 node-1 multipathd: uevent trigger error
<27>Oct 12 19:14:48 node-1 multipathd: uevent trigger error
<11>Oct 12 19:15:02 node-1 liberasurecode[26753]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:15:02 node-1 liberasurecode[26753]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:15:02 node-1 liberasurecode[26753]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 12 19:15:02 node-1 liberasurecode[26753]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
