Oct 28 04:41:35 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8394" x-info="http://www.rsyslog.com"] start
Oct 28 04:41:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 28 04:41:35 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 28 04:41:35 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 28 04:41:35 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 28 04:41:35 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 28 04:41:35 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 28 04:41:35 node-1 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Oct 28 04:41:35 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=9e56509e-8d69-44d2-9eb3-e13f64a57a07 nomdmonddf nomdmonisw
Oct 28 04:41:35 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 28 04:41:35 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 28 04:41:35 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 28 04:41:35 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 28 04:41:35 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 28 04:41:35 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 28 04:41:35 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 28 04:41: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 28 04:41:35 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 28 04:41:35 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 04:41:35 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 28 04:41:35 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 28 04:41:35 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 28 04:41:35 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 28 04:41:35 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 28 04:41:35 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 28 04:41:35 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 28 04:41:35 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 28 04:41:35 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 28 04:41:35 node-1 kernel: [    0.000000]   2 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000]   3 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000]   4 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000]   5 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000]   6 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000]   7 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000]   8 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000]   9 disabled
Oct 28 04:41:35 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 28 04:41:35 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 28 04:41:35 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 28 04:41:35 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 28 04:41:35 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 28 04:41:35 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 28 04:41:35 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 28 04:41:35 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 28 04:41:35 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 28 04:41:35 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 28 04:41:35 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 28 04:41:35 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 28 04:41:35 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 28 04:41:35 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 28 04:41:35 node-1 kernel: [    0.000000] Zone ranges:
Oct 28 04:41:35 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 28 04:41:35 node-1 kernel: [    0.000000] Early memory node ranges
Oct 28 04:41:35 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 28 04:41:35 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 28 04:41:35 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 28 04:41:35 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 28 04:41:35 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 28 04:41:35 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 28 04:41:35 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 28 04:41:35 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 28 04:41:35 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 28 04:41:35 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 28 04:41:35 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 28 04:41:35 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 28 04:41:35 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 28 04:41:35 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 28 04:41:35 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 28 04:41:35 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 28 04:41:35 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 28 04:41:35 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 28 04:41:35 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 28 04:41:35 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 28 04:41:35 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 28 04:41:35 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 28 04:41:35 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 28 04:41: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 28 04:41:35 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 28 04:41:35 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 28 04:41:35 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=9e56509e-8d69-44d2-9eb3-e13f64a57a07 nomdmonddf nomdmonisw
Oct 28 04:41:35 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 28 04:41:35 node-1 kernel: [    0.000000] Checking aperture...
Oct 28 04:41:35 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 04:41:35 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 28 04:41:35 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 28 04:41:35 node-1 kernel: [    0.000000] Memory: 32653312K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct 28 04:41:35 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 28 04:41:35 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 28 04:41:35 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 28 04:41:35 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 28 04:41:35 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 28 04:41:35 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 28 04:41:35 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 28 04:41:35 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 28 04:41:35 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 28 04:41:35 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 28 04:41:35 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 28 04:41:35 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 28 04:41:35 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 28 04:41:35 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 28 04:41:35 node-1 kernel: [    0.004000] tsc: Detected 3491.833 MHz processor
Oct 28 04:41:35 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.66 BogoMIPS (lpj=13967332)
Oct 28 04:41:35 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 28 04:41:35 node-1 kernel: [    0.000043] Security Framework initialized
Oct 28 04:41:35 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Oct 28 04:41:35 node-1 kernel: [    0.000062] Yama: becoming mindful.
Oct 28 04:41:35 node-1 kernel: [    0.001460] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.006323] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.008248] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.008277] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.008568] Initializing cgroup subsys memory
Oct 28 04:41:35 node-1 kernel: [    0.008576] Initializing cgroup subsys devices
Oct 28 04:41:35 node-1 kernel: [    0.008578] Initializing cgroup subsys freezer
Oct 28 04:41:35 node-1 kernel: [    0.008580] Initializing cgroup subsys blkio
Oct 28 04:41:35 node-1 kernel: [    0.008581] Initializing cgroup subsys perf_event
Oct 28 04:41:35 node-1 kernel: [    0.008584] Initializing cgroup subsys hugetlb
Oct 28 04:41:35 node-1 kernel: [    0.008603] CPU: Physical Processor ID: 0
Oct 28 04:41:35 node-1 kernel: [    0.008604] CPU: Processor Core ID: 0
Oct 28 04:41:35 node-1 kernel: [    0.008608] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 28 04:41:35 node-1 kernel: [    0.008608] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 28 04:41:35 node-1 kernel: [    0.009302] mce: CPU supports 22 MCE banks
Oct 28 04:41:35 node-1 kernel: [    0.009330] CPU0: Thermal monitoring enabled (TM1)
Oct 28 04:41:35 node-1 kernel: [    0.009351] process: using mwait in idle threads
Oct 28 04:41:35 node-1 kernel: [    0.009354] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 28 04:41:35 node-1 kernel: [    0.009354] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 28 04:41:35 node-1 kernel: [    0.009354] tlb_flushall_shift: 6
Oct 28 04:41:35 node-1 kernel: [    0.009442] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 28 04:41:35 node-1 kernel: [    0.010166] ACPI: Core revision 20131115
Oct 28 04:41:35 node-1 kernel: [    0.022999] ACPI: All ACPI Tables successfully acquired
Oct 28 04:41:35 node-1 kernel: [    0.023164] ftrace: allocating 28622 entries in 112 pages
Oct 28 04:41:35 node-1 kernel: [    0.031903] dmar: Host address width 46
Oct 28 04:41:35 node-1 kernel: [    0.031905] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 28 04:41:35 node-1 kernel: [    0.031911] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 04:41:35 node-1 kernel: [    0.031913] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 28 04:41:35 node-1 kernel: [    0.031917] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 04:41:35 node-1 kernel: [    0.031919] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 28 04:41:35 node-1 kernel: [    0.031920] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 28 04:41:35 node-1 kernel: [    0.031921] dmar: ATSR flags: 0x0
Oct 28 04:41:35 node-1 kernel: [    0.031922] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 28 04:41:35 node-1 kernel: [    0.031923] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 28 04:41:35 node-1 kernel: [    0.032039] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 28 04:41:35 node-1 kernel: [    0.032040] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 04:41:35 node-1 kernel: [    0.032042] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 04:41:35 node-1 kernel: [    0.032043] HPET id 0 under DRHD base 0xc7ffc000
Oct 28 04:41:35 node-1 kernel: [    0.032044] Your BIOS is broken and requested that x2apic be disabled.
Oct 28 04:41:35 node-1 kernel: [    0.032044] This will slightly decrease performance.
Oct 28 04:41:35 node-1 kernel: [    0.032044] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 28 04:41:35 node-1 kernel: [    0.032475] Enabled IRQ remapping in xapic mode
Oct 28 04:41:35 node-1 kernel: [    0.032476] x2apic not enabled, IRQ remapping is in xapic mode
Oct 28 04:41:35 node-1 kernel: [    0.032480] Switched APIC routing to physical flat.
Oct 28 04:41:35 node-1 kernel: [    0.033098] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 28 04:41:35 node-1 kernel: [    0.072747] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 28 04:41:35 node-1 kernel: [    0.072752] TSC deadline timer enabled
Oct 28 04:41:35 node-1 kernel: [    0.072760] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 28 04:41:35 node-1 kernel: [    0.072766] ... version:                3
Oct 28 04:41:35 node-1 kernel: [    0.072767] ... bit width:              48
Oct 28 04:41:35 node-1 kernel: [    0.072768] ... generic registers:      4
Oct 28 04:41:35 node-1 kernel: [    0.072769] ... value mask:             0000ffffffffffff
Oct 28 04:41:35 node-1 kernel: [    0.072770] ... max period:             0000ffffffffffff
Oct 28 04:41:35 node-1 kernel: [    0.072771] ... fixed-purpose events:   3
Oct 28 04:41:35 node-1 kernel: [    0.072772] ... event mask:             000000070000000f
Oct 28 04:41:35 node-1 kernel: [    0.074170] x86: Booting SMP configuration:
Oct 28 04:41:35 node-1 kernel: [    0.088296] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 28 04:41:35 node-1 kernel: [    0.074172] .... node  #0, CPUs:        #1  #2  #3
Oct 28 04:41:35 node-1 kernel: [    0.116214] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 28 04:41:35 node-1 kernel: [    0.270351] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 28 04:41:35 node-1 kernel: [    0.325866] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 28 04:41:35 node-1 kernel: [    0.382726] x86: Booted up 2 nodes, 16 CPUs
Oct 28 04:41:35 node-1 kernel: [    0.382729] smpboot: Total of 16 processors activated (111750.82 BogoMIPS)
Oct 28 04:41:35 node-1 kernel: [    0.407355] devtmpfs: initialized
Oct 28 04:41:35 node-1 kernel: [    0.409837] EVM: security.selinux
Oct 28 04:41:35 node-1 kernel: [    0.409839] EVM: security.SMACK64
Oct 28 04:41:35 node-1 kernel: [    0.409840] EVM: security.ima
Oct 28 04:41:35 node-1 kernel: [    0.409840] EVM: security.capability
Oct 28 04:41:35 node-1 kernel: [    0.409891] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.410544] pinctrl core: initialized pinctrl subsystem
Oct 28 04:41:35 node-1 kernel: [    0.410606] regulator-dummy: no parameters
Oct 28 04:41:35 node-1 kernel: [    0.410637] RTC time:  4:40:59, date: 10/28/16
Oct 28 04:41:35 node-1 kernel: [    0.410671] NET: Registered protocol family 16
Oct 28 04:41:35 node-1 kernel: [    0.410754] cpuidle: using governor ladder
Oct 28 04:41:35 node-1 kernel: [    0.410755] cpuidle: using governor menu
Oct 28 04:41:35 node-1 kernel: [    0.410790] ACPI: bus type PCI registered
Oct 28 04:41:35 node-1 kernel: [    0.410792] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 28 04:41:35 node-1 kernel: [    0.410850] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 28 04:41:35 node-1 kernel: [    0.410852] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 28 04:41:35 node-1 kernel: [    0.424581] PCI: Using configuration type 1 for base access
Oct 28 04:41:35 node-1 kernel: [    0.425584] bio: create slab <bio-0> at 0
Oct 28 04:41:35 node-1 kernel: [    0.425871] ACPI: Added _OSI(Module Device)
Oct 28 04:41:35 node-1 kernel: [    0.425872] ACPI: Added _OSI(Processor Device)
Oct 28 04:41:35 node-1 kernel: [    0.425873] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 28 04:41:35 node-1 kernel: [    0.425874] ACPI: Added _OSI(Processor Aggregator Device)
Oct 28 04:41:35 node-1 kernel: [    0.438609] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 28 04:41:35 node-1 kernel: [    0.449069] ACPI: Interpreter enabled
Oct 28 04:41:35 node-1 kernel: [    0.449075] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 28 04:41:35 node-1 kernel: [    0.449079] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 28 04:41:35 node-1 kernel: [    0.449081] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 28 04:41:35 node-1 kernel: [    0.449088] ACPI: (supports S0 S4 S5)
Oct 28 04:41:35 node-1 kernel: [    0.449090] ACPI: Using IOAPIC for interrupt routing
Oct 28 04:41:35 node-1 kernel: [    0.449132] HEST: Table parsing has been initialized.
Oct 28 04:41:35 node-1 kernel: [    0.449135] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 28 04:41:35 node-1 kernel: [    0.449706] ACPI: No dock devices found.
Oct 28 04:41:35 node-1 kernel: [    0.461733] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 28 04:41:35 node-1 kernel: [    0.461737] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 04:41:35 node-1 kernel: [    0.461741] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 04:41:35 node-1 kernel: [    0.461767] PCI host bridge to bus 0000:ff
Oct 28 04:41:35 node-1 kernel: [    0.461769] pci_bus 0000:ff: root bus resource [bus ff]
Oct 28 04:41:35 node-1 kernel: [    0.461777] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.461815] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.461845] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.461880] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.461909] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.461938] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.461968] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462000] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462028] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462057] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462083] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462109] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462138] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462164] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462190] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462217] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462245] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462273] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462299] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.462327] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462353] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.462380] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462408] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462438] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.462473] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462504] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462534] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462565] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462595] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462628] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462660] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462691] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462721] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462754] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462786] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462819] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462852] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462882] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462909] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462940] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.462972] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463009] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463044] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463076] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463106] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463137] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463167] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463196] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463229] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463260] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463292] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463321] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463351] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463381] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463416] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463447] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463478] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463536] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 28 04:41:35 node-1 kernel: [    0.463538] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 04:41:35 node-1 kernel: [    0.463541] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 04:41:35 node-1 kernel: [    0.463559] PCI host bridge to bus 0000:7f
Oct 28 04:41:35 node-1 kernel: [    0.463561] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 28 04:41:35 node-1 kernel: [    0.463566] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463595] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.463625] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463657] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463680] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.463707] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.463734] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463762] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463787] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463811] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463835] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463859] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463884] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463908] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463935] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463965] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.463988] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464014] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464038] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.464064] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464088] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.464111] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464135] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464163] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 04:41:35 node-1 kernel: [    0.464198] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464226] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464256] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464287] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464314] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464342] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464371] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464404] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464433] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464463] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464493] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464522] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464552] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464578] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464604] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464634] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464660] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464689] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464721] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464750] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464776] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464802] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464830] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464858] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464886] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464914] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464946] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464973] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.464997] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 04:41: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 28 04:41:35 node-1 kernel: [    0.465025] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.465052] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.465083] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.465111] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.466390] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 28 04:41:35 node-1 kernel: [    0.466394] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 04:41:35 node-1 kernel: [    0.467588] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 04:41:35 node-1 kernel: [    0.468103] PCI host bridge to bus 0000:00
Oct 28 04:41:35 node-1 kernel: [    0.468105] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 28 04:41:35 node-1 kernel: [    0.468107] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 28 04:41:35 node-1 kernel: [    0.468108] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 28 04:41:35 node-1 kernel: [    0.468109] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 28 04:41:35 node-1 kernel: [    0.468111] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 28 04:41:35 node-1 kernel: [    0.468112] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 28 04:41:35 node-1 kernel: [    0.468114] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 28 04:41:35 node-1 kernel: [    0.468119] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 28 04:41:35 node-1 kernel: [    0.468201] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.468232] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.468274] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 28 04:41:35 node-1 kernel: [    0.468293] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.468322] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.468362] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 28 04:41:35 node-1 kernel: [    0.468381] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.468410] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.468450] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 28 04:41:35 node-1 kernel: [    0.468467] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.468537] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.468614] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.468688] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 04:41:35 node-1 kernel: [    0.468692] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 28 04:41:35 node-1 kernel: [    0.468777] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 28 04:41:35 node-1 kernel: [    0.468925] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 28 04:41:35 node-1 kernel: [    0.468942] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 28 04:41:35 node-1 kernel: [    0.469020] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.469073] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 28 04:41:35 node-1 kernel: [    0.469095] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.469150] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.469194] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 28 04:41:35 node-1 kernel: [    0.469220] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.469276] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.469319] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 28 04:41:35 node-1 kernel: [    0.469343] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 28 04:41:35 node-1 kernel: [    0.469360] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 28 04:41:35 node-1 kernel: [    0.469438] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.469488] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 28 04:41:35 node-1 kernel: [    0.469512] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 28 04:41:35 node-1 kernel: [    0.469760] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 28 04:41:35 node-1 kernel: [    0.469765] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 28 04:41:35 node-1 kernel: [    0.469771] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.469778] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.469785] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 28 04:41:35 node-1 kernel: [    0.469815] pci 0000:01:00.0: supports D1 D2
Oct 28 04:41:35 node-1 kernel: [    0.479402] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 04:41:35 node-1 kernel: [    0.479409] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 04:41:35 node-1 kernel: [    0.479413] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 04:41:35 node-1 kernel: [    0.479590] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.479624] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 28 04:41:35 node-1 kernel: [    0.491397] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 04:41:35 node-1 kernel: [    0.491403] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.491407] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 04:41:35 node-1 kernel: [    0.491492] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.491565] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.491665] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.491711] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 04:41:35 node-1 kernel: [    0.491714] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.491716] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 04:41:35 node-1 kernel: [    0.491769] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.491891] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.491945] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 04:41:35 node-1 kernel: [    0.491948] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.491950] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.491999] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.492122] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.492172] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.492292] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.492331] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.492450] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.492489] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 28 04:41:35 node-1 kernel: [    0.492607] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 28 04:41:35 node-1 kernel: [    0.492651] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 04:41:35 node-1 kernel: [    0.492654] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.492656] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.492714] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 28 04:41:35 node-1 kernel: [    0.492777] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.492829] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.492871] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 28 04:41:35 node-1 kernel: [    0.492953] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 28 04:41:35 node-1 kernel: [    0.493060] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 04:41:35 node-1 kernel: [    0.493062] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.493064] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.493120] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 28 04:41:35 node-1 kernel: [    0.493198] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.493247] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.493457] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 04:41:35 node-1 kernel: [    0.493461] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 04:41:35 node-1 kernel: [    0.493524] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 28 04:41:35 node-1 kernel: [    0.493581] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.493629] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.493838] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 04:41:35 node-1 kernel: [    0.493842] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 04:41:35 node-1 kernel: [    0.493901] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 28 04:41:35 node-1 kernel: [    0.493961] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.494013] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 28 04:41:35 node-1 kernel: [    0.494258] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 04:41:35 node-1 kernel: [    0.494261] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 04:41:35 node-1 kernel: [    0.494436] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 04:41:35 node-1 kernel: [    0.494475] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 04:41:35 node-1 kernel: [    0.494553] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 28 04:41:35 node-1 kernel: [    0.494572] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 28 04:41:35 node-1 kernel: [    0.494585] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 28 04:41:35 node-1 kernel: [    0.494599] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 28 04:41:35 node-1 kernel: [    0.494649] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 28 04:41:35 node-1 kernel: [    0.499400] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 04:41:35 node-1 kernel: [    0.499404] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 04:41:35 node-1 kernel: [    0.499436] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 28 04:41:35 node-1 kernel: [    0.499925] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 28 04:41:35 node-1 kernel: [    0.499928] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 04:41:35 node-1 kernel: [    0.500049] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 04:41:35 node-1 kernel: [    0.500158] PCI host bridge to bus 0000:80
Oct 28 04:41:35 node-1 kernel: [    0.500160] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 28 04:41:35 node-1 kernel: [    0.500161] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 28 04:41:35 node-1 kernel: [    0.500163] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 28 04:41:35 node-1 kernel: [    0.500171] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.500234] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.500303] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 04:41:35 node-1 kernel: [    0.500365] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 04:41:35 node-1 kernel: [    0.500370] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 28 04:41:35 node-1 kernel: [    0.500443] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 28 04:41:35 node-1 kernel: [    0.500740] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 28 04:41:35 node-1 kernel: [    0.500772] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 28 04:41:35 node-1 kernel: [    0.500802] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 28 04:41:35 node-1 kernel: [    0.500831] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 28 04:41:35 node-1 kernel: [    0.500860] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 04:41:35 node-1 kernel: [    0.500890] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 04:41:35 node-1 kernel: [    0.500920] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 04:41:35 node-1 kernel: [    0.500950] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 04:41:35 node-1 kernel: [    0.501038] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 28 04:41:35 node-1 kernel: [    0.501043] ACPI: \_SB_.UNC1: notify handler is installed
Oct 28 04:41:35 node-1 kernel: [    0.501044] ACPI: \_SB_.UNC0: notify handler is installed
Oct 28 04:41:35 node-1 kernel: [    0.501059] ACPI: \_SB_.PCI0: notify handler is installed
Oct 28 04:41:35 node-1 kernel: [    0.501112] ACPI: \_SB_.PCI1: notify handler is installed
Oct 28 04:41:35 node-1 kernel: [    0.501191] Found 4 acpi root devices
Oct 28 04:41:35 node-1 kernel: [    0.501301] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 28 04:41:35 node-1 kernel: [    0.501303] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 28 04:41:35 node-1 kernel: [    0.501305] vgaarb: loaded
Oct 28 04:41:35 node-1 kernel: [    0.501306] vgaarb: bridge control possible 0000:0c:00.0
Oct 28 04:41:35 node-1 kernel: [    0.501426] SCSI subsystem initialized
Oct 28 04:41:35 node-1 kernel: [    0.501490] libata version 3.00 loaded.
Oct 28 04:41:35 node-1 kernel: [    0.501505] ACPI: bus type USB registered
Oct 28 04:41:35 node-1 kernel: [    0.501516] usbcore: registered new interface driver usbfs
Oct 28 04:41:35 node-1 kernel: [    0.501521] usbcore: registered new interface driver hub
Oct 28 04:41:35 node-1 kernel: [    0.501544] usbcore: registered new device driver usb
Oct 28 04:41:35 node-1 kernel: [    0.501720] PCI: Using ACPI for IRQ routing
Oct 28 04:41:35 node-1 kernel: [    0.505333] PCI: pci_cache_line_size set to 64 bytes
Oct 28 04:41:35 node-1 kernel: [    0.505545] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 28 04:41:35 node-1 kernel: [    0.505546] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 28 04:41:35 node-1 kernel: [    0.505547] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 28 04:41:35 node-1 kernel: [    0.505610] NetLabel: Initializing
Oct 28 04:41:35 node-1 kernel: [    0.505611] NetLabel:  domain hash size = 128
Oct 28 04:41:35 node-1 kernel: [    0.505612] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 28 04:41:35 node-1 kernel: [    0.505622] NetLabel:  unlabeled traffic allowed by default
Oct 28 04:41:35 node-1 kernel: [    0.505677] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 28 04:41:35 node-1 kernel: [    0.505681] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 28 04:41:35 node-1 kernel: [    0.507742] Switched to clocksource hpet
Oct 28 04:41:35 node-1 kernel: [    0.511767] AppArmor: AppArmor Filesystem Enabled
Oct 28 04:41:35 node-1 kernel: [    0.511781] pnp: PnP ACPI init
Oct 28 04:41:35 node-1 kernel: [    0.511788] ACPI: bus type PNP registered
Oct 28 04:41:35 node-1 kernel: [    0.511898] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 28 04:41:35 node-1 kernel: [    0.511906] pnp 00:01: [dma 4]
Oct 28 04:41:35 node-1 kernel: [    0.511918] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 28 04:41:35 node-1 kernel: [    0.511944] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 28 04:41:35 node-1 kernel: [    0.511964] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 28 04:41:35 node-1 kernel: [    0.511982] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 28 04:41:35 node-1 kernel: [    0.512015] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 28 04:41:35 node-1 kernel: [    0.512068] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512071] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 28 04:41:35 node-1 kernel: [    0.512072] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512074] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512075] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512080] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512082] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 28 04:41:35 node-1 kernel: [    0.512084] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512085] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512087] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512088] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512090] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512091] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 28 04:41:35 node-1 kernel: [    0.512093] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 28 04:41:35 node-1 kernel: [    0.512176] pnp 00:07: [dma 0 disabled]
Oct 28 04:41:35 node-1 kernel: [    0.512204] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 04:41:35 node-1 kernel: [    0.512279] pnp 00:08: [dma 0 disabled]
Oct 28 04:41:35 node-1 kernel: [    0.512311] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 04:41:35 node-1 kernel: [    0.512362] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 28 04:41:35 node-1 kernel: [    0.512708] pnp: PnP ACPI: found 10 devices
Oct 28 04:41:35 node-1 kernel: [    0.512710] ACPI: bus type PNP unregistered
Oct 28 04:41:35 node-1 kernel: [    0.518982] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 04:41:35 node-1 kernel: [    0.518985] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 04:41:35 node-1 kernel: [    0.518988] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 04:41:35 node-1 kernel: [    0.518992] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 04:41:35 node-1 kernel: [    0.518994] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519008] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519038] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 04:41:35 node-1 kernel: [    0.519052] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519081] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 04:41:35 node-1 kernel: [    0.519095] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 04:41:35 node-1 kernel: [    0.519124] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 04:41:35 node-1 kernel: [    0.519152] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 04:41:35 node-1 kernel: [    0.519184] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 04:41:35 node-1 kernel: [    0.519186] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519201] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519230] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 04:41:35 node-1 kernel: [    0.519232] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519247] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519275] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 04:41:35 node-1 kernel: [    0.519277] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519280] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519284] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 04:41:35 node-1 kernel: [    0.519285] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519288] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519292] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 04:41:35 node-1 kernel: [    0.519296] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 04:41:35 node-1 kernel: [    0.519304] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 04:41:35 node-1 kernel: [    0.519308] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 04:41:35 node-1 kernel: [    0.519314] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 28 04:41:35 node-1 kernel: [    0.519315] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 28 04:41:35 node-1 kernel: [    0.519316] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 28 04:41:35 node-1 kernel: [    0.519317] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 28 04:41:35 node-1 kernel: [    0.519318] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 28 04:41:35 node-1 kernel: [    0.519319] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 28 04:41:35 node-1 kernel: [    0.519320] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 28 04:41:35 node-1 kernel: [    0.519320] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 28 04:41:35 node-1 kernel: [    0.519321] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519322] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519323] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519324] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519325] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519326] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519327] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519328] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519329] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 28 04:41:35 node-1 kernel: [    0.519330] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519331] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 28 04:41:35 node-1 kernel: [    0.519332] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 28 04:41:35 node-1 kernel: [    0.519333] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 28 04:41:35 node-1 kernel: [    0.519334] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 28 04:41:35 node-1 kernel: [    0.519336] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 28 04:41:35 node-1 kernel: [    0.519337] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 28 04:41:35 node-1 kernel: [    0.519375] NET: Registered protocol family 2
Oct 28 04:41:35 node-1 kernel: [    0.519635] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.519972] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.520117] TCP: Hash tables configured (established 262144 bind 65536)
Oct 28 04:41:35 node-1 kernel: [    0.520153] TCP: reno registered
Oct 28 04:41:35 node-1 kernel: [    0.520183] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.520278] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.520430] NET: Registered protocol family 1
Oct 28 04:41:35 node-1 kernel: [    0.559841] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 28 04:41:35 node-1 kernel: [    0.559847] PCI: CLS 64 bytes, default 64
Oct 28 04:41:35 node-1 kernel: [    0.559890] Trying to unpack rootfs image as initramfs...
Oct 28 04:41:35 node-1 kernel: [    0.779477] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct 28 04:41:35 node-1 kernel: [    0.779522] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 28 04:41:35 node-1 kernel: [    0.779525] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 28 04:41:35 node-1 kernel: [    0.779946] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.779952] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.779957] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.779962] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.779972] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.779983] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.779992] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780001] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780009] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780017] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780032] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780038] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780047] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780069] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780076] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780083] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 04:41:35 node-1 kernel: [    0.780157] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 28 04:41:35 node-1 kernel: [    0.780160] Scanning for low memory corruption every 60 seconds
Oct 28 04:41:35 node-1 kernel: [    0.780529] Initialise system trusted keyring
Oct 28 04:41:35 node-1 kernel: [    0.780582] audit: initializing netlink socket (disabled)
Oct 28 04:41:35 node-1 kernel: [    0.780598] type=2000 audit(1477629658.732:1): initialized
Oct 28 04:41:35 node-1 kernel: [    0.798365] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 28 04:41:35 node-1 kernel: [    0.799894] zbud: loaded
Oct 28 04:41:35 node-1 kernel: [    0.800021] VFS: Disk quotas dquot_6.5.2
Oct 28 04:41:35 node-1 kernel: [    0.800056] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 28 04:41:35 node-1 kernel: [    0.800431] fuse init (API version 7.22)
Oct 28 04:41:35 node-1 kernel: [    0.800493] msgmni has been set to 32768
Oct 28 04:41:35 node-1 kernel: [    0.800540] Key type big_key registered
Oct 28 04:41:35 node-1 kernel: [    0.801046] Key type asymmetric registered
Oct 28 04:41:35 node-1 kernel: [    0.801048] Asymmetric key parser 'x509' registered
Oct 28 04:41:35 node-1 kernel: [    0.801070] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 28 04:41:35 node-1 kernel: [    0.801138] io scheduler noop registered
Oct 28 04:41:35 node-1 kernel: [    0.801140] io scheduler deadline registered (default)
Oct 28 04:41:35 node-1 kernel: [    0.801160] io scheduler cfq registered
Oct 28 04:41:35 node-1 kernel: [    0.801716] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    0.801885] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    0.802000] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    0.802109] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    0.802235] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    0.802326] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    0.802736] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 28 04:41:35 node-1 kernel: [    0.802761] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 28 04:41:35 node-1 kernel: [    0.802778] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 28 04:41:35 node-1 kernel: [    0.802786] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802789] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802792] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 28 04:41:35 node-1 kernel: [    0.802797] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802798] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802800] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802801] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802803] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802804] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802806] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802807] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802809] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802810] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802811] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802813] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802815] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 28 04:41:35 node-1 kernel: [    0.802820] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802823] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 28 04:41:35 node-1 kernel: [    0.802838] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802841] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 28 04:41:35 node-1 kernel: [    0.802851] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802853] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 28 04:41:35 node-1 kernel: [    0.802856] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 28 04:41:35 node-1 kernel: [    0.802920] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 28 04:41:35 node-1 kernel: [    0.802926] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 28 04:41:35 node-1 kernel: [    0.802930] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 28 04:41:35 node-1 kernel: [    0.802940] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 28 04:41:35 node-1 kernel: [    0.802980] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 28 04:41:35 node-1 kernel: [    0.802981] vesafb: scrolling: redraw
Oct 28 04:41:35 node-1 kernel: [    0.802983] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 28 04:41:35 node-1 kernel: [    0.823617] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 28 04:41:35 node-1 kernel: [    0.832127] Console: switching to colour frame buffer device 80x30
Oct 28 04:41:35 node-1 kernel: [    0.840790] fb0: VESA VGA frame buffer device
Oct 28 04:41:35 node-1 kernel: [    0.840987] intel_idle: MWAIT substates: 0x2120
Oct 28 04:41:35 node-1 kernel: [    0.840988] intel_idle: v0.4 model 0x3F
Oct 28 04:41:35 node-1 kernel: [    0.840988] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 28 04:41:35 node-1 kernel: [    0.841233] ipmi message handler version 39.2
Oct 28 04:41:35 node-1 kernel: [    0.841504] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 28 04:41:35 node-1 kernel: [    0.841936] ACPI: AC Adapter [P111] (on-line)
Oct 28 04:41:35 node-1 kernel: [    0.847151] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 28 04:41:35 node-1 kernel: [    0.858141] ACPI: Power Button [PWRB]
Oct 28 04:41:35 node-1 kernel: [    0.863899] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 28 04:41:35 node-1 kernel: [    0.875514] ACPI: Power Button [PWRF]
Oct 28 04:41:35 node-1 kernel: [    0.901283] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 28 04:41:35 node-1 kernel: [    0.913007] pstore: Registered erst as persistent store backend
Oct 28 04:41:35 node-1 kernel: [    0.919236] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 28 04:41:35 node-1 kernel: [    0.931243] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 28 04:41:35 node-1 kernel: [    0.958006] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 28 04:41:35 node-1 kernel: [    0.991354] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 28 04:41:35 node-1 kernel: [    1.005506] Linux agpgart interface v0.103
Oct 28 04:41:35 node-1 kernel: [    1.013231] brd: module loaded
Oct 28 04:41:35 node-1 kernel: [    1.020330] loop: module loaded
Oct 28 04:41:35 node-1 kernel: [    1.027069] libphy: Fixed MDIO Bus: probed
Oct 28 04:41:35 node-1 kernel: [    1.033545] tun: Universal TUN/TAP device driver, 1.6
Oct 28 04:41:35 node-1 kernel: [    1.040067] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 28 04:41:35 node-1 kernel: [    1.046598] PPP generic driver version 2.4.2
Oct 28 04:41:35 node-1 kernel: [    1.052979] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 28 04:41:35 node-1 kernel: [    1.059424] ehci-pci: EHCI PCI platform driver
Oct 28 04:41:35 node-1 kernel: [    1.065943] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 28 04:41:35 node-1 kernel: [    1.072360] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 28 04:41:35 node-1 kernel: [    1.084897] ehci-pci 0000:00:1a.0: debug port 2
Oct 28 04:41:35 node-1 kernel: [    1.095095] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 28 04:41:35 node-1 kernel: [    1.095113] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 28 04:41:35 node-1 kernel: [    1.111231] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 28 04:41:35 node-1 kernel: [    1.117311] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 04:41:35 node-1 kernel: [    1.123490] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 04:41:35 node-1 kernel: [    1.135397] usb usb1: Product: EHCI Host Controller
Oct 28 04:41:35 node-1 kernel: [    1.141422] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 04:41:35 node-1 kernel: [    1.147466] usb usb1: SerialNumber: 0000:00:1a.0
Oct 28 04:41:35 node-1 kernel: [    1.153412] hub 1-0:1.0: USB hub found
Oct 28 04:41:35 node-1 kernel: [    1.159190] hub 1-0:1.0: 2 ports detected
Oct 28 04:41:35 node-1 kernel: [    1.164967] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 28 04:41:35 node-1 kernel: [    1.170622] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 28 04:41:35 node-1 kernel: [    1.181651] ehci-pci 0000:00:1d.0: debug port 2
Oct 28 04:41:35 node-1 kernel: [    1.190959] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 28 04:41:35 node-1 kernel: [    1.190962] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 28 04:41:35 node-1 kernel: [    1.207150] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 28 04:41:35 node-1 kernel: [    1.212361] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 04:41:35 node-1 kernel: [    1.217670] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 04:41:35 node-1 kernel: [    1.228276] usb usb2: Product: EHCI Host Controller
Oct 28 04:41:35 node-1 kernel: [    1.233764] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 04:41:35 node-1 kernel: [    1.239333] usb usb2: SerialNumber: 0000:00:1d.0
Oct 28 04:41:35 node-1 kernel: [    1.244871] hub 2-0:1.0: USB hub found
Oct 28 04:41:35 node-1 kernel: [    1.250245] hub 2-0:1.0: 2 ports detected
Oct 28 04:41:35 node-1 kernel: [    1.255578] ehci-platform: EHCI generic platform driver
Oct 28 04:41:35 node-1 kernel: [    1.260835] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 28 04:41:35 node-1 kernel: [    1.266198] ohci-pci: OHCI PCI platform driver
Oct 28 04:41:35 node-1 kernel: [    1.271572] ohci-platform: OHCI generic platform driver
Oct 28 04:41:35 node-1 kernel: [    1.276786] uhci_hcd: USB Universal Host Controller Interface driver
Oct 28 04:41:35 node-1 kernel: [    1.282150] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 28 04:41:35 node-1 kernel: [    1.482912] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 28 04:41:35 node-1 kernel: [    1.778674] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 28 04:41:35 node-1 kernel: [    1.795014] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 28 04:41:35 node-1 kernel: [    1.800802] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 04:41:35 node-1 kernel: [    1.806659] hub 1-1:1.0: USB hub found
Oct 28 04:41:35 node-1 kernel: [    1.812376] hub 1-1:1.0: 6 ports detected
Oct 28 04:41:35 node-1 kernel: [    1.930535] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 28 04:41:35 node-1 kernel: [    2.321037] i8042: No controller found
Oct 28 04:41:35 node-1 kernel: [    2.326607] mousedev: PS/2 mouse device common for all mice
Oct 28 04:41:35 node-1 kernel: [    2.332348] rtc_cmos 00:02: RTC can wake from S4
Oct 28 04:41:35 node-1 kernel: [    2.334995] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 28 04:41:35 node-1 kernel: [    2.334996] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 04:41:35 node-1 kernel: [    2.335629] hub 2-1:1.0: USB hub found
Oct 28 04:41:35 node-1 kernel: [    2.335863] hub 2-1:1.0: 8 ports detected
Oct 28 04:41:35 node-1 kernel: [    2.360697] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 28 04:41:35 node-1 kernel: [    2.366465] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 28 04:41:35 node-1 kernel: [    2.377788] device-mapper: uevent: version 1.0.3
Oct 28 04:41:35 node-1 kernel: [    2.383501] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 28 04:41:35 node-1 kernel: [    2.394891] ledtrig-cpu: registered to indicate activity on CPUs
Oct 28 04:41:35 node-1 kernel: [    2.400874] TCP: cubic registered
Oct 28 04:41:35 node-1 kernel: [    2.406751] NET: Registered protocol family 10
Oct 28 04:41:35 node-1 kernel: [    2.412818] NET: Registered protocol family 17
Oct 28 04:41:35 node-1 kernel: [    2.418593] Key type dns_resolver registered
Oct 28 04:41:35 node-1 kernel: [    2.424669] Loading compiled-in X.509 certificates
Oct 28 04:41:35 node-1 kernel: [    2.430899] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 28 04:41:35 node-1 kernel: [    2.442522] registered taskstats version 1
Oct 28 04:41:35 node-1 kernel: [    2.450572] Key type trusted registered
Oct 28 04:41:35 node-1 kernel: [    2.458203] Key type encrypted registered
Oct 28 04:41:35 node-1 kernel: [    2.463696] AppArmor: AppArmor sha1 policy hashing enabled
Oct 28 04:41:35 node-1 kernel: [    2.469210] IMA: No TPM chip found, activating TPM-bypass!
Oct 28 04:41:35 node-1 kernel: [    2.475297] regulator-dummy: disabling
Oct 28 04:41:35 node-1 kernel: [    2.480797]   Magic number: 4:683:667
Oct 28 04:41:35 node-1 kernel: [    2.486414] acpi LNXCPU:16: hash matches
Oct 28 04:41:35 node-1 kernel: [    2.491901] rtc_cmos 00:02: setting system clock to 2016-10-28 04:41:01 UTC (1477629661)
Oct 28 04:41:35 node-1 kernel: [    2.504181] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 28 04:41:35 node-1 kernel: [    2.509780] EDD information not available.
Oct 28 04:41:35 node-1 kernel: [    2.515313] PM: Hibernation image not present or could not be loaded.
Oct 28 04:41:35 node-1 kernel: [    2.516176] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 28 04:41:35 node-1 kernel: [    2.527365] Write protecting the kernel read-only data: 12288k
Oct 28 04:41:35 node-1 kernel: [    2.533740] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 28 04:41:35 node-1 kernel: [    2.546634] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 28 04:41:35 node-1 kernel: [    2.578623] device-mapper: multipath: version 1.6.0 loaded
Oct 28 04:41:35 node-1 kernel: [    2.586532] systemd-udevd[215]: starting version 204
Oct 28 04:41:35 node-1 kernel: [    2.609964] md: linear personality registered for level -1
Oct 28 04:41:35 node-1 kernel: [    2.618027] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 28 04:41:35 node-1 kernel: [    2.629724] md: multipath personality registered for level -4
Oct 28 04:41:35 node-1 kernel: [    2.638042] md: raid0 personality registered for level 0
Oct 28 04:41:35 node-1 kernel: [    2.646195] md: raid1 personality registered for level 1
Oct 28 04:41:35 node-1 kernel: [    2.654524] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 28 04:41:35 node-1 kernel: [    2.660755] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 28 04:41:35 node-1 kernel: [    2.661103] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 28 04:41:35 node-1 kernel: [    2.673297] megasas: FW now in Ready state
Oct 28 04:41:35 node-1 kernel: [    2.679616] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679620] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679624] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679629] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679633] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679637] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679644] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679648] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679652] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679656] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679660] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679664] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679668] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679672] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679676] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679681] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.679723] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 28 04:41:35 node-1 kernel: [    2.700897] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct 28 04:41:35 node-1 kernel: [    2.714060] 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 28 04:41:35 node-1 kernel: [    2.721960] raid6: sse2x1    5722 MB/s
Oct 28 04:41:35 node-1 kernel: [    2.734639] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 04:41:35 node-1 kernel: [    2.741573] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.741581] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.741585] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.741589] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.741631] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 04:41:35 node-1 kernel: [    2.765330] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct 28 04:41:35 node-1 kernel: [    2.778652] 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 28 04:41:35 node-1 kernel: [    2.790057] raid6: sse2x2   13250 MB/s
Oct 28 04:41:35 node-1 kernel: [    2.798841] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 28 04:41:35 node-1 kernel: [    2.857770] raid6: sse2x4   10017 MB/s
Oct 28 04:41:35 node-1 kernel: [    2.929699] raid6: avx2x1   14940 MB/s
Oct 28 04:41:35 node-1 kernel: [    3.001638] raid6: avx2x2   18868 MB/s
Oct 28 04:41:35 node-1 kernel: [    3.073577] raid6: avx2x4   21335 MB/s
Oct 28 04:41:35 node-1 kernel: [    3.079821] raid6: using algorithm avx2x4 (21335 MB/s)
Oct 28 04:41:35 node-1 kernel: [    3.085966] raid6: using avx2x2 recovery algorithm
Oct 28 04:41:35 node-1 kernel: [    3.091966] megasas:IOC Init cmd success
Oct 28 04:41:35 node-1 kernel: [    3.091969] Switched to clocksource tsc
Oct 28 04:41:35 node-1 kernel: [    3.092127] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.092163] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.092200] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.092237] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.092275] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.092306] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.092427] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.101533] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct 28 04:41:35 node-1 kernel: [    3.101535] 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 28 04:41:35 node-1 kernel: [    3.101536] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 04:41:35 node-1 kernel: [    3.101592] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.101625] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.101662] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.101694] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.101781] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.106444] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 28 04:41:35 node-1 kernel: [    3.106445] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 28 04:41:35 node-1 kernel: [    3.106446] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 28 04:41:35 node-1 kernel: [    3.106447] usb 2-1.4: Manufacturer: Avocent
Oct 28 04:41:35 node-1 kernel: [    3.106447] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 28 04:41:35 node-1 kernel: [    3.112224] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct 28 04:41:35 node-1 kernel: [    3.112225] 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 28 04:41:35 node-1 kernel: [    3.112226] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 04:41:35 node-1 kernel: [    3.112287] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.112326] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.112361] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.112391] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.112470] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 04:41:35 node-1 kernel: [    3.117594] megasas: INIT adapter done
Oct 28 04:41:35 node-1 kernel: [    3.177347] xor: automatically using best checksumming function:
Oct 28 04:41:35 node-1 kernel: [    3.207445] hidraw: raw HID events driver (C) Jiri Kosina
Oct 28 04:41:35 node-1 kernel: [    3.209515] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 28 04:41:35 node-1 kernel: [    3.209983] scsi0 : LSI SAS based MegaRAID driver
Oct 28 04:41:35 node-1 kernel: [    3.217100] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 04:41:35 node-1 kernel: [    3.225435]    avx       : 52740.000 MB/sec
Oct 28 04:41:35 node-1 kernel: [    3.228468] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 04:41:35 node-1 kernel: [    3.232792] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 28 04:41:35 node-1 kernel: [    3.232927] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 28 04:41:35 node-1 kernel: [    3.233108] sd 0:2:0:0: [sda] Write Protect is off
Oct 28 04:41:35 node-1 kernel: [    3.233109] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 28 04:41:35 node-1 kernel: [    3.233181] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 28 04:41:35 node-1 kernel: [    3.260277]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 28 04:41:35 node-1 kernel: [    3.262202] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 28 04:41:35 node-1 kernel: [    3.317931] async_tx: api initialized (async)
Oct 28 04:41:35 node-1 kernel: [    3.327080] usbcore: registered new interface driver usbhid
Oct 28 04:41:35 node-1 kernel: [    3.327080] usbhid: USB HID core driver
Oct 28 04:41:35 node-1 kernel: [    3.367066] 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 28 04:41:35 node-1 kernel: [    3.379698] 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 28 04:41:35 node-1 kernel: [    3.392483] 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 28 04:41:35 node-1 kernel: [    3.405262] md: raid6 personality registered for level 6
Oct 28 04:41:35 node-1 kernel: [    3.405267] 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 28 04:41:35 node-1 kernel: [    3.405342] 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 28 04:41:35 node-1 kernel: [    3.405706] 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 28 04:41:35 node-1 kernel: [    3.428701] random: lvm urandom read with 30 bits of entropy available
Oct 28 04:41:35 node-1 kernel: [    3.459418] md: raid5 personality registered for level 5
Oct 28 04:41:35 node-1 kernel: [    3.466433] md: raid4 personality registered for level 4
Oct 28 04:41:35 node-1 kernel: [    3.476575] md: raid10 personality registered for level 10
Oct 28 04:41:35 node-1 kernel: [    3.533603] multipathd (372): /proc/372/oom_adj is deprecated, please use /proc/372/oom_score_adj instead.
Oct 28 04:41:35 node-1 kernel: [    3.557540] bio: create slab <bio-1> at 1
Oct 28 04:41:35 node-1 kernel: [    4.343148] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 04:41:35 node-1 kernel: [    5.098408] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 28 04:41:35 node-1 kernel: [    5.120985] random: nonblocking pool is initialized
Oct 28 04:41:35 node-1 kernel: [    5.129189] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 28 04:41:35 node-1 kernel: [    5.323987] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 28 04:41:35 node-1 kernel: [    5.365893] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 28 04:41:35 node-1 kernel: [    5.418097] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 04:41:35 node-1 kernel: [    5.592847] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 28 04:41:35 node-1 kernel: [    5.627308] XFS (dm-0): Mounting Filesystem
Oct 28 04:41:35 node-1 kernel: [    5.905491] XFS (dm-0): Ending clean mount
Oct 28 04:41:35 node-1 kernel: [    5.978729] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 04:41:35 node-1 kernel: [    6.013240] XFS (dm-1): Mounting Filesystem
Oct 28 04:41:35 node-1 kernel: [    6.125766] XFS (dm-1): Ending clean mount
Oct 28 04:41:35 node-1 kernel: [    8.006990] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 28 04:41:35 node-1 kernel: [    8.035494] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 28 04:41:35 node-1 kernel: [    8.225886] systemd-udevd[778]: starting version 204
Oct 28 04:41:35 node-1 kernel: [    8.482852] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 28 04:41:35 node-1 kernel: [    8.482859] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 04:41:35 node-1 kernel: [    8.482863] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 28 04:41:35 node-1 kernel: [    8.482865] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 04:41:35 node-1 kernel: [    8.482899] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 28 04:41:35 node-1 kernel: [    8.503617] power_meter ACPI000D:00: Found ACPI power meter.
Oct 28 04:41:35 node-1 kernel: [    8.503664] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 28 04:41:35 node-1 kernel: [    8.510452] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 28 04:41:35 node-1 kernel: [    8.510653] wmi: Mapper loaded
Oct 28 04:41:35 node-1 kernel: [    8.513591] IPMI System Interface driver.
Oct 28 04:41:35 node-1 kernel: [    8.513627] ipmi_si: probing via ACPI
Oct 28 04:41:35 node-1 kernel: [    8.513643] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 28 04:41:35 node-1 kernel: [    8.513644] ipmi_si: Adding ACPI-specified kcs state machine
Oct 28 04:41:35 node-1 kernel: [    8.513657] ipmi_si: probing via SMBIOS
Oct 28 04:41:35 node-1 kernel: [    8.513658] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 04:41:35 node-1 kernel: [    8.513659] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 28 04:41:35 node-1 kernel: [    8.513661] ipmi_si: probing via SPMI
Oct 28 04:41:35 node-1 kernel: [    8.513662] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 04:41:35 node-1 kernel: [    8.513663] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 28 04:41:35 node-1 kernel: [    8.513665] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 28 04:41:35 node-1 kernel: [    8.593399] systemd-udevd[813]: renamed network interface eth1 to enp7s0
Oct 28 04:41:35 node-1 kernel: [    8.621308] systemd-udevd[811]: renamed network interface eth0 to enp6s0
Oct 28 04:41:35 node-1 kernel: [    8.666358] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 28 04:41:35 node-1 kernel: [    8.666364] ipmi_si 00:09: IPMI kcs interface initialized
Oct 28 04:41:35 node-1 kernel: [    8.677289] systemd-udevd[796]: renamed network interface eth2 to enp8s0
Oct 28 04:41:35 node-1 kernel: [    8.709471] systemd-udevd[797]: renamed network interface eth3 to enp9s0
Oct 28 04:41:35 node-1 kernel: [    8.969736] type=1400 audit(1477629667.978:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1008 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.969746] type=1400 audit(1477629667.978:3): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1007 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.969985] type=1400 audit(1477629667.978:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1008 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.969991] type=1400 audit(1477629667.978:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1007 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.970221] type=1400 audit(1477629667.978:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1008 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.970227] type=1400 audit(1477629667.978:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1007 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.972105] type=1400 audit(1477629667.978:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1005 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.972249] type=1400 audit(1477629667.978:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1005 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.972374] type=1400 audit(1477629667.978:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1005 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    8.974345] type=1400 audit(1477629667.982:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Oct 28 04:41:35 node-1 kernel: [    9.510690] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 28 04:41:35 node-1 kernel: [    9.513200] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 28 04:41:35 node-1 kernel: [    9.818324] enic 0000:06:00.0 enp6s0: Link UP
Oct 28 04:41:35 node-1 kernel: [    9.818745] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 28 04:41:35 node-1 kernel: [    9.818763] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 28 04:41:35 node-1 kernel: [   19.746398] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 28 04:41:37 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 28 04:41:37 node-1 kernel: [   38.052252] init: failsafe main process (8421) killed by TERM signal
Oct 28 04:41:37 node-1 dbus[8488]: [system] AppArmor D-Bus mediation is enabled
Oct 28 04:41:37 node-1 kernel: [   38.217498] audit_printk_skb: 30 callbacks suppressed
Oct 28 04:41:37 node-1 kernel: [   38.217499] type=1400 audit(1477629697.324:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8538 comm="apparmor_parser"
Oct 28 04:41:37 node-1 kernel: [   38.217503] type=1400 audit(1477629697.324:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Oct 28 04:41:37 node-1 kernel: [   38.217505] type=1400 audit(1477629697.324:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Oct 28 04:41:37 node-1 kernel: [   38.217752] type=1400 audit(1477629697.324:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Oct 28 04:41:37 node-1 kernel: [   38.217754] type=1400 audit(1477629697.324:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Oct 28 04:41:37 node-1 kernel: [   38.217867] type=1400 audit(1477629697.324:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Oct 28 04:41:37 node-1 kernel: [   38.220531] type=1400 audit(1477629697.328:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8539 comm="apparmor_parser"
Oct 28 04:41:37 node-1 kernel: [   38.286353] type=1400 audit(1477629697.392:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8541 comm="apparmor_parser"
Oct 28 04:41:37 node-1 cron[8579]: (CRON) INFO (pidfile fd = 3)
Oct 28 04:41:37 node-1 anacron[8614]: Anacron 2.3 started on 2016-10-28
Oct 28 04:41:37 node-1 cron[8620]: (CRON) STARTUP (fork ok)
Oct 28 04:41:37 node-1 anacron[8614]: Will run job `cron.daily' in 5 min.
Oct 28 04:41:37 node-1 anacron[8614]: Will run job `cron.weekly' in 10 min.
Oct 28 04:41:37 node-1 anacron[8614]: Will run job `cron.monthly' in 15 min.
Oct 28 04:41:37 node-1 anacron[8614]: Jobs will be executed sequentially
Oct 28 04:41:37 node-1 multipathd: path checkers start up
Oct 28 04:41:37 node-1 cron[8620]: (CRON) INFO (Running @reboot jobs)
Oct 28 04:41:38 node-1 postfix/master[8758]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 28 04:41:41 node-1 puppet-agent[8942]: Reopening log files
Oct 28 04:41:42 node-1 puppet-agent[8942]: Could not request certificate: Connection refused - connect(2)
Oct 28 04:41:54 node-1 puppet-user[9150]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 28 04:41:54 node-1 puppet-user[9150]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Oct 28 04:41:55 node-1 puppet-user[9150]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 28 04:41:55 node-1 puppet-user[9150]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 28 04:41:55 node-1 puppet-user[9150]: Finished catalog run in 1.12 seconds
Oct 28 04:41:56 node-1 multipathd: uevent trigger error
Oct 28 04:41:57 node-1 puppet-user[9580]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 04:41:57 node-1 puppet-user[9580]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 28 04:41:57 node-1 puppet-user[9580]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 28 04:41:57 node-1 puppet-user[9580]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 28 04:41:57 node-1 puppet-user[9580]: (/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 28 04:41:57 node-1 puppet-user[9580]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 28 04:41:57 node-1 puppet-user[9580]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 28 04:41:57 node-1 puppet-user[9580]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 28 04:41:57 node-1 puppet-user[9580]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 28 04:41:57 node-1 puppet-user[9580]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 28 04:41:57 node-1 puppet-user[9580]: Finished catalog run in 0.05 seconds
Oct 28 04:41:58 node-1 puppet-user[10036]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 28 04:41:58 node-1 puppet-user[10036]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 28 04:41:58 node-1 puppet-user[10036]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 28 04:41:58 node-1 puppet-user[10036]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 28 04:41:58 node-1 puppet-user[10036]: Finished catalog run in 0.03 seconds
Oct 28 04:42:00 node-1 puppet-user[10494]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 28 04:42:00 node-1 puppet-user[10494]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 04:42:00 node-1 puppet-user[10494]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 28 04:42:00 node-1 puppet-user[10494]: Finished catalog run in 0.03 seconds
Oct 28 04:42:01 node-1 puppet-user[10946]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 28 04:42:01 node-1 CRON[11527]: (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 28 04:42:01 node-1 puppet-user[10946]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Oct 28 04:42:01 node-1 puppet-user[10946]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 28 04:42:02 node-1 puppet-user[10946]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Oct 28 04:42:02 node-1 puppet-user[10946]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Oct 28 04:42:02 node-1 puppet-user[10946]: Finished catalog run in 0.84 seconds
Oct 28 04:42:03 node-1 puppet-user[11634]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 28 04:42:04 node-1 puppet-user[11634]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Oct 28 04:42:04 node-1 puppet-user[11634]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Oct 28 04:42:04 node-1 puppet-user[11634]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 28 04:42:04 node-1 puppet-user[11634]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 28 04:42:04 node-1 puppet-user[11634]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Oct 28 04:42:04 node-1 puppet-user[11634]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 28 04:42:04 node-1 puppet-user[11634]: Finished catalog run in 0.31 seconds
Oct 28 04:42:05 node-1 puppet-user[12112]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 28 04:42:06 node-1 puppet-user[12112]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Oct 28 04:42:06 node-1 puppet-user[12112]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 28 04:42:06 node-1 kernel: [   67.058739] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 28 04:42:06 node-1 kernel: [   67.058788] 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 28 04:42:06 node-1 puppet-user[12112]: (/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 28 04:42:06 node-1 puppet-user[12112]: Finished catalog run in 0.05 seconds
Oct 28 04:42:07 node-1 puppet-user[12569]: (Scope(Class[main])) MODULAR: sync_time
Oct 28 04:42:07 node-1 puppet-user[12569]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 04:42:07 node-1 ntpdate[12984]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 28 04:42:13 node-1 kernel: [   74.129893] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 04:42:13 node-1 puppet-agent[8942]: Could not run: SIGTERM
Oct 28 04:42:13 node-1 kernel: [   74.394644] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 28 04:42:13 node-1 ec2: 
Oct 28 04:42:13 node-1 ec2: #############################################################
Oct 28 04:42:13 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 28 04:42:13 node-1 ec2: 1024 13:d2:4e:b7:9a:2e:d3:df:e8:43:75:2c:b0:03:83:bb  root@node-1.domain.tld (DSA)
Oct 28 04:42:13 node-1 ec2: 256 d0:d7:23:72:69:36:07:36:51:a4:f1:2b:51:bd:04:15  root@node-1.domain.tld (ECDSA)
Oct 28 04:42:13 node-1 ec2: 256 e3:93:3c:82:da:2c:a1:6e:c8:4a:6b:c9:9a:f7:82:a9  root@node-1.domain.tld (ED25519)
Oct 28 04:42:13 node-1 ec2: 2048 ce:29:6d:9d:fe:cf:6b:a5:2a:eb:a2:2d:c7:b9:a5:9c  root@node-1.domain.tld (RSA)
Oct 28 04:42:13 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 28 04:42:13 node-1 ec2: #############################################################
Oct 28 04:42:14 node-1 ntpdate[12984]: adjust time server 10.20.0.2 offset -0.029743 sec
Oct 28 04:42:14 node-1 puppet-user[12569]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 28 04:42:14 node-1 puppet-user[12569]: Finished catalog run in 6.16 seconds
Oct 28 04:42:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 04:42:18 node-1 nailgun-agent: D, [2016-10-28T04:42:01.806063 #11530] DEBUG -- : Sleep for 17 seconds before sending request
Oct 28 04:42:18 node-1 nailgun-agent: I, [2016-10-28T04:42:18.819320 #11530]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 28 04:42:19 node-1 nailgun-agent: D, [2016-10-28T04:42:19.198102 #11530] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 28 04:42:19 node-1 puppet-user[13362]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 04:42:19 node-1 puppet-user[13362]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 28 04:42:19 node-1 puppet-user[13362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 28 04:42:19 node-1 puppet-user[13362]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Oct 28 04:42:19 node-1 puppet-user[13362]: Finished catalog run in 0.06 seconds
Oct 28 04:42:20 node-1 puppet-user[13944]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 28 04:42:21 node-1 puppet-user[13944]: Compiled catalog for node-1.domain.tld in environment production in 0.39 seconds
Oct 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:21 node-1 puppet-user[13944]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:21 node-1 puppet-user[13944]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:21 node-1 puppet-user[13944]: (/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 28 04:42:22 node-1 puppet-user[13944]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 28 04:42:22 node-1 puppet-user[13944]: Finished catalog run in 0.84 seconds
Oct 28 04:42:23 node-1 puppet-user[14448]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 28 04:42:23 node-1 puppet-user[14448]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct 28 04:42:26 node-1 puppet-user[14448]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.253043 #11530] DEBUG -- : Trying to find block devices
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.253111 #11530] DEBUG -- : Found block device: sda
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.253155 #11530] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.253179 #11530] DEBUG -- : Trying to get list of physical devices
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.253367 #11530] DEBUG -- : Getting udev properties for device: sda
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.255524 #11530] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Oct 28 04:42:31 node-1 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16362", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.255570 #11530] DEBUG -- : Trying to find out if device sda is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.255625 #11530] DEBUG -- : Device sda removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.255645 #11530] DEBUG -- : Device sda seems to be appropriate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.256125 #11530] DEBUG -- : Getting udev properties for device: dm-0
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.257899 #11530] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-MxWDu5V67BCI4CYEF1Qztii8mjWxknT4fimsvPq636kVojdkKHkUWM1JRpxBQ112 /dev/disk/by-uuid/4040729a-948f-4bde-86a3-c5849f50c167 /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-MxWDu5V67BCI4CYEF1Qztii8mjWxknT4fimsvPq636kVojdkKHkUWM1JRpxBQ112", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4040729a-948f-4bde-86a3-c5849f50c167", "ID_FS_UUID_ENC"=>"4040729a-948f-4bde-86a3-c5849f50c167", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12294", "nomdmonddf"=>"1", "nom
Oct 28 04:42:31 node-1 nailgun-agent: dmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.257942 #11530] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.257977 #11530] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.258011 #11530] DEBUG -- : Device dm-0 seems to be appropriate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.258029 #11530] DEBUG -- : Getting udev properties for device: dm-1
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.260372 #11530] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-eV35Cx3ZSWiMrBTpPWJS5XNSUFhZinjxm648IAn128KOV1l15mqU8Hy1JaYiVclx /dev/disk/by-uuid/71e59bff-a565-49bd-9cca-4ee271159887 /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-eV35Cx3ZSWiMrBTpPWJS5XNSUFhZinjxm648IAn128KOV1l15mqU8Hy1JaYiVclx", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"71e59bff-a565-49bd-9cca-4ee271159887", "ID_FS_UUID_ENC"=>"71e59bff-a565-49bd-9cca-4ee271159887", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4
Oct 28 04:42:31 node-1 nailgun-agent: 9108", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.260452 #11530] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.260489 #11530] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.260504 #11530] DEBUG -- : Device dm-1 seems to be appropriate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.260521 #11530] DEBUG -- : Getting udev properties for device: dm-2
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.262695 #11530] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-ZO0JydsqB7fAoef6a2MPnu3sjFAyYgTDd737syYQM29sKhHVx423Wqu5dQvy6mQ0 /dev/disk/by-uuid/ce66623e-4412-49a4-bf8f-6c75eb77f7c9 /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-ZO0JydsqB7fAoef6a2MPnu3sjFAyYgTDd737syYQM29sKhHVx423Wqu5dQvy6mQ0", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ce66623e-4412-49a4-bf8f-6c75eb77f7c9", "ID_FS_UUID_ENC"=>"ce66623e-4412-49a4-bf8f-6c75eb77f7c9", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56535", "nomdmon
Oct 28 04:42:31 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.262729 #11530] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.262767 #11530] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.262783 #11530] DEBUG -- : Device dm-2 seems to be appropriate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.262824 #11530] DEBUG -- : Getting udev properties for device: dm-3
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.264958 #11530] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-M6mPFa4pGA5cSmXreNlpXodFWYpoXLSBYOKb6yEM3syrKcNS646RCl53DBDtAfb7 /dev/disk/by-uuid/ae4299d9-648b-4f06-ad00-6d95f3618c2c /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-M6mPFa4pGA5cSmXreNlpXodFWYpoXLSBYOKb6yEM3syrKcNS646RCl53DBDtAfb7", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ae4299d9-648b-4f06-ad00-6d95f3618c2c", "ID_FS_UUID_ENC"=>"ae4299d9-648b-4f06-ad00-6d95f3618c2c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60579", "nomdmonddf"=>"1",
Oct 28 04:42:31 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.264991 #11530] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.265027 #11530] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.265042 #11530] DEBUG -- : Device dm-3 seems to be appropriate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.265059 #11530] DEBUG -- : Getting udev properties for device: dm-4
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.266816 #11530] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-yfWKMxU0iFtnVmGgXGTTgGll1MYqT5eAojwL7G4HPbYqFIkXaMX2MwlVXBrfLM2T /dev/disk/by-uuid/9e56509e-8d69-44d2-9eb3-e13f64a57a07 /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-yfWKMxU0iFtnVmGgXGTTgGll1MYqT5eAojwL7G4HPbYqFIkXaMX2MwlVXBrfLM2T", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9e56509e-8d69-44d2-9eb3-e13f64a57a07", "ID_FS_UUID_ENC"=>"9e56509e-8d69-44d2-9eb3-e13f64a57a07", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62412", "nomdmonddf"=>"1", "nom
Oct 28 04:42:31 node-1 nailgun-agent: dmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.266843 #11530] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.266889 #11530] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.266903 #11530] DEBUG -- : Device dm-4 seems to be appropriate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.266919 #11530] DEBUG -- : Getting udev properties for device: dm-5
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.268715 #11530] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-yfWKMxU0iFtnVmGgXGTTgGll1MYqT5eAe2cdP8vssRjC3DsLkkPGnfmU6vfAWJof /dev/disk/by-uuid/fae5ca7b-5cea-488b-b937-6015432a5259 /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-yfWKMxU0iFtnVmGgXGTTgGll1MYqT5eAe2cdP8vssRjC3DsLkkPGnfmU6vfAWJof", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"fae5ca7b-5cea-488b-b937-6015432a5259", "ID_FS_UUID_ENC"=>"fae5ca7b-5cea-488b-b937-6015432a5259", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62731", "nomdmonddf"=>"1", "nomdmonisw
Oct 28 04:42:31 node-1 nailgun-agent: "=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.268742 #11530] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.268773 #11530] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.268789 #11530] DEBUG -- : Device dm-5 seems to be appropriate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.268842 #11530] DEBUG -- : Getting udev properties for device: ram0
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.270348 #11530] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51419", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.270389 #11530] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.270433 #11530] DEBUG -- : Device ram0 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.270452 #11530] DEBUG -- : Getting udev properties for device: ram1
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.272077 #11530] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51443", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.272103 #11530] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.272160 #11530] DEBUG -- : Device ram1 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.272181 #11530] DEBUG -- : Getting udev properties for device: ram2
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.273894 #11530] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51583", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.273920 #11530] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.273958 #11530] DEBUG -- : Device ram2 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.273978 #11530] DEBUG -- : Getting udev properties for device: ram3
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.275836 #11530] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51610", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.275862 #11530] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.275925 #11530] DEBUG -- : Device ram3 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.275945 #11530] DEBUG -- : Getting udev properties for device: ram4
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.277832 #11530] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51633", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.277857 #11530] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.277892 #11530] DEBUG -- : Device ram4 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.277912 #11530] DEBUG -- : Getting udev properties for device: ram5
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.279500 #11530] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51652", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.279544 #11530] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.279578 #11530] DEBUG -- : Device ram5 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.279611 #11530] DEBUG -- : Getting udev properties for device: ram6
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.281236 #11530] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51674", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.281261 #11530] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.281311 #11530] DEBUG -- : Device ram6 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.281331 #11530] DEBUG -- : Getting udev properties for device: ram7
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.282785 #11530] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51694", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.282818 #11530] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.282854 #11530] DEBUG -- : Device ram7 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.282883 #11530] DEBUG -- : Getting udev properties for device: ram8
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.284401 #11530] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51713", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.284425 #11530] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.284455 #11530] DEBUG -- : Device ram8 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.284475 #11530] DEBUG -- : Getting udev properties for device: ram9
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.286137 #11530] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51732", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.286161 #11530] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.286228 #11530] DEBUG -- : Device ram9 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.286247 #11530] DEBUG -- : Getting udev properties for device: loop0
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.287818 #11530] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51130", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.287848 #11530] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.287885 #11530] DEBUG -- : Device loop0 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.287917 #11530] DEBUG -- : Getting udev properties for device: loop1
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.289327 #11530] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51144", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.289351 #11530] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.289410 #11530] DEBUG -- : Device loop1 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.289431 #11530] DEBUG -- : Getting udev properties for device: loop2
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.290905 #11530] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51156", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.290936 #11530] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.290968 #11530] DEBUG -- : Device loop2 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.290993 #11530] DEBUG -- : Getting udev properties for device: loop3
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.292516 #11530] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51170", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.292541 #11530] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.292576 #11530] DEBUG -- : Device loop3 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.292605 #11530] DEBUG -- : Getting udev properties for device: loop4
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.294260 #11530] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51182", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.294292 #11530] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.294359 #11530] DEBUG -- : Device loop4 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.294378 #11530] DEBUG -- : Getting udev properties for device: loop5
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.295946 #11530] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51196", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.295982 #11530] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.296015 #11530] DEBUG -- : Device loop5 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.296046 #11530] DEBUG -- : Getting udev properties for device: loop6
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.297644 #11530] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51381", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.297671 #11530] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.297729 #11530] DEBUG -- : Device loop6 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.297747 #11530] DEBUG -- : Getting udev properties for device: loop7
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.299194 #11530] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51402", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.299236 #11530] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.299266 #11530] DEBUG -- : Device loop7 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.299285 #11530] DEBUG -- : Getting udev properties for device: ram10
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.305059 #11530] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51464", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.305089 #11530] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.305133 #11530] DEBUG -- : Device ram10 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.305151 #11530] DEBUG -- : Getting udev properties for device: ram11
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.306958 #11530] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51485", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.306982 #11530] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.307023 #11530] DEBUG -- : Device ram11 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.307042 #11530] DEBUG -- : Getting udev properties for device: ram12
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.308824 #11530] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51504", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.308897 #11530] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.308940 #11530] DEBUG -- : Device ram12 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.308959 #11530] DEBUG -- : Getting udev properties for device: ram13
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.310611 #11530] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51519", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.310669 #11530] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.310708 #11530] DEBUG -- : Device ram13 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.310728 #11530] DEBUG -- : Getting udev properties for device: ram14
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.312462 #11530] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51536", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.312498 #11530] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.312530 #11530] DEBUG -- : Device ram14 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.312583 #11530] DEBUG -- : Getting udev properties for device: ram15
Oct 28 04:42:31 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314291 #11530] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51559", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314316 #11530] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314348 #11530] DEBUG -- : Device ram15 removable parameter: "0"
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314384 #11530] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314426 #11530] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314460 #11530] DEBUG -- : Found block device: dm-0
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314473 #11530] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314486 #11530] DEBUG -- : Found block device: dm-1
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314496 #11530] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314506 #11530] DEBUG -- : Found block device: dm-2
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314516 #11530] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314524 #11530] DEBUG -- : Found block device: dm-3
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314533 #11530] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314541 #11530] DEBUG -- : Found block device: dm-4
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314551 #11530] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314593 #11530] DEBUG -- : Found block device: dm-5
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314604 #11530] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314624 #11530] DEBUG -- : Found block device: ram0
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314635 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314644 #11530] DEBUG -- : Found block device: ram1
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314655 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314664 #11530] DEBUG -- : Found block device: ram2
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314674 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314682 #11530] DEBUG -- : Found block device: ram3
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314693 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314736 #11530] DEBUG -- : Found block device: ram4
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314746 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314754 #11530] DEBUG -- : Found block device: ram5
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314764 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314772 #11530] DEBUG -- : Found block device: ram6
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314781 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314790 #11530] DEBUG -- : Found block device: ram7
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314799 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314807 #11530] DEBUG -- : Found block device: ram8
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314817 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314882 #11530] DEBUG -- : Found block device: ram9
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314892 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314901 #11530] DEBUG -- : Found block device: loop0
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314912 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314921 #11530] DEBUG -- : Found block device: loop1
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314930 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314938 #11530] DEBUG -- : Found block device: loop2
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314948 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.314957 #11530] DEBUG -- : Found block device: loop3
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315001 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315010 #11530] DEBUG -- : Found block device: loop4
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315019 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315028 #11530] DEBUG -- : Found block device: loop5
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315037 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315045 #11530] DEBUG -- : Found block device: loop6
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315055 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315063 #11530] DEBUG -- : Found block device: loop7
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315072 #11530] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315080 #11530] DEBUG -- : Found block device: ram10
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315126 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315135 #11530] DEBUG -- : Found block device: ram11
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315144 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315152 #11530] DEBUG -- : Found block device: ram12
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315162 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315169 #11530] DEBUG -- : Found block device: ram13
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315179 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315187 #11530] DEBUG -- : Found block device: ram14
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315196 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315245 #11530] DEBUG -- : Found block device: ram15
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315255 #11530] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.315283 #11530] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct 28 04:42:31 node-1 nailgun-agent: D, [2016-10-28T04:42:31.499383 #11530] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 28 04:42:31 node-1 nailgun-agent: I, [2016-10-28T04:42:31.499569 #11530]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 28 04:42:53 node-1 puppet-user[14448]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 28 04:42:53 node-1 puppet-user[14448]: Finished catalog run in 29.34 seconds
Oct 28 04:42:55 node-1 puppet-user[17010]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 28 04:42:55 node-1 puppet-user[17010]: Compiled catalog for node-1.domain.tld in environment production in 0.56 seconds
Oct 28 04:42:55 node-1 puppet-user[17010]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 28 04:42:55 node-1 puppet-user[17010]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 28 04:42:55 node-1 puppet-user[17010]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 28 04:42:55 node-1 puppet-user[17010]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 28 04:42:55 node-1 puppet-user[17010]: Finished catalog run in 0.08 seconds
Oct 28 04:42:57 node-1 puppet-user[17459]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 28 04:42:58 node-1 puppet-user[17459]: Compiled catalog for node-1.domain.tld in environment production in 0.96 seconds
Oct 28 04:42:58 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 28 04:42:58 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 28 04:42:58 node-1 crontab[17898]: (root) LIST (root)
Oct 28 04:42:58 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 28 04:42:58 node-1 crontab[17901]: (root) REPLACE (root)
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 28 04:43:00 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 28 04:43:01 node-1 CRON[18051]: (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 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 28 04:43:01 node-1 puppet-user[17459]: (/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 28 04:43:01 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8394" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 04:43:01 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 28 04:43:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:20 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:20 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:21 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:21 node-1 multipathd: uevent trigger error
<27>Oct 28 04:43:21 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:16 node-1 ntpdate[29095]: no servers can be used, exiting
<27>Oct 28 04:44:47 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:47 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:47 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:47 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:47 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:44:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:06 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:06 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:06 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:06 node-1 multipathd: uevent trigger error
<27>Oct 28 04:45:06 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:00 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:00 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:00 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:00 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:00 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:00 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:08 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:08 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:08 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:08 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:08 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:08 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:11 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 04:46:11 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 04:46:17 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 04:46:17 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 04:46:22 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 04:46:28 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 04:46:28 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 04:46:35 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:35 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:35 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:35 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:35 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:46:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:23 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:23 node-1 multipathd: uevent trigger error
<129>Oct 28 04:47:25 node-1 haproxy[23386]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 90ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 04:47:25 node-1 haproxy[23386]: proxy odl-neutron-endpoint has no server available!
<129>Oct 28 04:47:26 node-1 haproxy[23393]: Server odl-jetty/node-1 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 28 04:47:26 node-1 haproxy[23393]: proxy odl-jetty has no server available!
<27>Oct 28 04:47:49 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:49 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:49 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:49 node-1 multipathd: uevent trigger error
<129>Oct 28 04:47:51 node-1 haproxy[25809]: 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 28 04:47:51 node-1 haproxy[25809]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:47:52 node-1 haproxy[25813]: 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 28 04:47:52 node-1 haproxy[25813]: proxy mysqld has no server available!
<27>Oct 28 04:47:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:58 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:58 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:58 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:58 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:58 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:58 node-1 multipathd: uevent trigger error
<27>Oct 28 04:47:58 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:00 node-1 haproxy[28391]: 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 28 04:48:01 node-1 haproxy[28395]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:01 node-1 haproxy[28395]: 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 28 04:48:01 node-1 haproxy[28395]: proxy mysqld has no server available!
<129>Oct 28 04:48:01 node-1 haproxy[28395]: 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 28 04:48:01 node-1 haproxy[28395]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:02 node-1 haproxy[28395]: 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 28 04:48:02 node-1 haproxy[28395]: proxy object-storage has no server available!
<27>Oct 28 04:48:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:04 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:06 node-1 haproxy[29944]: 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 28 04:48:07 node-1 haproxy[29948]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:07 node-1 haproxy[29948]: 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 28 04:48:07 node-1 haproxy[29948]: proxy neutron has no server available!
<129>Oct 28 04:48:07 node-1 haproxy[29948]: 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 28 04:48:07 node-1 haproxy[29948]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:07 node-1 haproxy[29948]: 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 28 04:48:07 node-1 haproxy[29948]: proxy mysqld has no server available!
<129>Oct 28 04:48:08 node-1 haproxy[29948]: 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 28 04:48:08 node-1 haproxy[29948]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:08 node-1 haproxy[29948]: 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 28 04:48:08 node-1 haproxy[29948]: proxy object-storage has no server available!
<27>Oct 28 04:48:10 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:10 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:10 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:10 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:10 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:12 node-1 haproxy[31344]: 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 28 04:48:13 node-1 haproxy[31354]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:13 node-1 haproxy[31354]: Server keystone-1/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 28 04:48:13 node-1 haproxy[31354]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:13 node-1 haproxy[31354]: 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 28 04:48:13 node-1 haproxy[31354]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:13 node-1 haproxy[31354]: Server keystone-2/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 28 04:48:13 node-1 haproxy[31354]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:13 node-1 haproxy[31354]: 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 28 04:48:13 node-1 haproxy[31354]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:13 node-1 haproxy[31354]: 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 28 04:48:13 node-1 haproxy[31354]: proxy neutron has no server available!
<129>Oct 28 04:48:14 node-1 haproxy[31354]: 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 28 04:48:14 node-1 haproxy[31354]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:14 node-1 haproxy[31354]: 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 28 04:48:14 node-1 haproxy[31354]: proxy mysqld has no server available!
<129>Oct 28 04:48:14 node-1 haproxy[31354]: 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 28 04:48:14 node-1 haproxy[31354]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:14 node-1 haproxy[31354]: 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 28 04:48:14 node-1 haproxy[31354]: proxy object-storage has no server available!
<27>Oct 28 04:48:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:16 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:16 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:18 node-1 haproxy[32694]: 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 28 04:48:18 node-1 haproxy[32694]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:18 node-1 haproxy[32694]: Server keystone-1/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 28 04:48:18 node-1 haproxy[32694]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:18 node-1 haproxy[32694]: 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 28 04:48:18 node-1 haproxy[32694]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:18 node-1 haproxy[32694]: Server keystone-2/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 28 04:48:18 node-1 haproxy[32694]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:18 node-1 haproxy[32694]: 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 28 04:48:19 node-1 haproxy[32698]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:19 node-1 haproxy[32698]: 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 28 04:48:19 node-1 haproxy[32698]: proxy neutron has no server available!
<129>Oct 28 04:48:19 node-1 haproxy[32698]: 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 28 04:48:19 node-1 haproxy[32698]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:19 node-1 haproxy[32698]: 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 28 04:48:19 node-1 haproxy[32698]: proxy mysqld has no server available!
<129>Oct 28 04:48:19 node-1 haproxy[32698]: 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 28 04:48:19 node-1 haproxy[32698]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:19 node-1 haproxy[32698]: 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 28 04:48:19 node-1 haproxy[32698]: proxy object-storage has no server available!
<129>Oct 28 04:48:19 node-1 haproxy[32698]: 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 28 04:48:19 node-1 haproxy[32698]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:20 node-1 haproxy[32698]: 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 28 04:48:20 node-1 haproxy[32698]: proxy aodh has no server available!
<27>Oct 28 04:48:21 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:21 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:21 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:21 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:21 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:23 node-1 haproxy[1887]: 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 28 04:48:23 node-1 haproxy[1887]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:24 node-1 haproxy[1896]: Server keystone-1/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 28 04:48:24 node-1 haproxy[1896]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:24 node-1 haproxy[1896]: 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 28 04:48:24 node-1 haproxy[1896]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:24 node-1 haproxy[1896]: Server keystone-2/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 28 04:48:24 node-1 haproxy[1896]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:24 node-1 haproxy[1896]: 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 28 04:48:24 node-1 haproxy[1896]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:24 node-1 haproxy[1896]: 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 28 04:48:24 node-1 haproxy[1896]: proxy neutron has no server available!
<129>Oct 28 04:48:24 node-1 haproxy[1896]: 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 28 04:48:24 node-1 haproxy[1896]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:24 node-1 haproxy[1896]: 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 28 04:48:24 node-1 haproxy[1896]: proxy mysqld has no server available!
<129>Oct 28 04:48:24 node-1 haproxy[1896]: 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 28 04:48:25 node-1 haproxy[1896]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:25 node-1 haproxy[1896]: 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 28 04:48:25 node-1 haproxy[1896]: proxy object-storage has no server available!
<129>Oct 28 04:48:25 node-1 haproxy[1896]: 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 28 04:48:25 node-1 haproxy[1896]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:25 node-1 haproxy[1896]: 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 28 04:48:25 node-1 haproxy[1896]: proxy aodh has no server available!
<129>Oct 28 04:48:25 node-1 haproxy[1896]: 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 28 04:48:25 node-1 haproxy[1896]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:25 node-1 haproxy[1896]: 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 28 04:48:25 node-1 haproxy[1896]: proxy ceilometer has no server available!
<27>Oct 28 04:48:26 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:27 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:27 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:27 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:29 node-1 haproxy[3326]: 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 28 04:48:29 node-1 haproxy[3326]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:29 node-1 haproxy[3326]: Server keystone-1/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 28 04:48:29 node-1 haproxy[3326]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:29 node-1 haproxy[3326]: 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 28 04:48:29 node-1 haproxy[3326]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:29 node-1 haproxy[3326]: 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 28 04:48:29 node-1 haproxy[3326]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:29 node-1 haproxy[3326]: 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 28 04:48:29 node-1 haproxy[3326]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: proxy neutron has no server available!
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: proxy mysqld has no server available!
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: proxy object-storage has no server available!
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: proxy aodh has no server available!
<129>Oct 28 04:48:30 node-1 haproxy[3330]: 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 28 04:48:30 node-1 haproxy[3330]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:31 node-1 haproxy[3330]: 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 28 04:48:31 node-1 haproxy[3330]: proxy ceilometer has no server available!
<27>Oct 28 04:48:32 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:32 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:32 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:32 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:32 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:32 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:34 node-1 haproxy[4704]: 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 28 04:48:34 node-1 haproxy[4704]: 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 28 04:48:35 node-1 haproxy[4708]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: proxy neutron has no server available!
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: proxy mysqld has no server available!
<129>Oct 28 04:48:35 node-1 haproxy[4708]: 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 28 04:48:35 node-1 haproxy[4708]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:36 node-1 haproxy[4708]: 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 28 04:48:36 node-1 haproxy[4708]: proxy object-storage has no server available!
<129>Oct 28 04:48:36 node-1 haproxy[4708]: 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 28 04:48:36 node-1 haproxy[4708]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:36 node-1 haproxy[4708]: 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 28 04:48:36 node-1 haproxy[4708]: proxy aodh has no server available!
<129>Oct 28 04:48:36 node-1 haproxy[4708]: 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 28 04:48:36 node-1 haproxy[4708]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:36 node-1 haproxy[4708]: 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 28 04:48:36 node-1 haproxy[4708]: proxy ceilometer has no server available!
<27>Oct 28 04:48:37 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:37 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:37 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:37 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:40 node-1 haproxy[6204]: 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 28 04:48:40 node-1 haproxy[6204]: 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 28 04:48:40 node-1 haproxy[6204]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:40 node-1 haproxy[6204]: 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 28 04:48:40 node-1 haproxy[6204]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:40 node-1 haproxy[6204]: 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 28 04:48:41 node-1 haproxy[6213]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: proxy glance-api has no server available!
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: proxy glance-glare has no server available!
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: proxy neutron has no server available!
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: proxy glance-registry has no server available!
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:41 node-1 haproxy[6213]: 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 28 04:48:41 node-1 haproxy[6213]: proxy mysqld has no server available!
<129>Oct 28 04:48:42 node-1 haproxy[6213]: 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 28 04:48:42 node-1 haproxy[6213]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:42 node-1 haproxy[6213]: 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 28 04:48:42 node-1 haproxy[6213]: proxy object-storage has no server available!
<129>Oct 28 04:48:42 node-1 haproxy[6213]: 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 28 04:48:42 node-1 haproxy[6213]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:42 node-1 haproxy[6213]: 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 28 04:48:42 node-1 haproxy[6213]: proxy aodh has no server available!
<129>Oct 28 04:48:42 node-1 haproxy[6213]: 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 28 04:48:42 node-1 haproxy[6213]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:42 node-1 haproxy[6213]: 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 28 04:48:42 node-1 haproxy[6213]: proxy ceilometer has no server available!
<27>Oct 28 04:48:43 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:43 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:43 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:44 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:44 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Oct 28 04:48:46 node-1 haproxy[7734]: 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 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: proxy nova-api has no server available!
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: proxy nova-metadata-api has no server available!
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: proxy glance-api has no server available!
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: proxy glance-glare has no server available!
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:47 node-1 haproxy[7738]: proxy neutron has no server available!
<129>Oct 28 04:48:47 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: proxy glance-registry has no server available!
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: proxy mysqld has no server available!
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: proxy object-storage has no server available!
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: proxy aodh has no server available!
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: proxy ceilometer has no server available!
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:48 node-1 haproxy[7738]: 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 28 04:48:48 node-1 haproxy[7738]: proxy nova-novncproxy has no server available!
<27>Oct 28 04:48:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:50 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:50 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:52 node-1 haproxy[9176]: 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 28 04:48:52 node-1 haproxy[9176]: 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 28 04:48:52 node-1 haproxy[9176]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:52 node-1 haproxy[9176]: 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 28 04:48:52 node-1 haproxy[9176]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:52 node-1 haproxy[9176]: 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 28 04:48:52 node-1 haproxy[9176]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:52 node-1 haproxy[9176]: 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 28 04:48:52 node-1 haproxy[9176]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:52 node-1 haproxy[9176]: 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 28 04:48:52 node-1 haproxy[9176]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:52 node-1 haproxy[9176]: 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 28 04:48:52 node-1 haproxy[9176]: proxy nova-api has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: proxy nova-metadata-api has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: proxy cinder-api has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: proxy glance-api has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: proxy glance-glare has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: proxy neutron has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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.
<27>Oct 28 04:48:53 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<129>Oct 28 04:48:53 node-1 haproxy[9182]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: proxy glance-registry has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: proxy mysqld has no server available!
<129>Oct 28 04:48:53 node-1 haproxy[9182]: 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 28 04:48:53 node-1 haproxy[9182]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:54 node-1 haproxy[9182]: 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 28 04:48:54 node-1 haproxy[9182]: proxy object-storage has no server available!
<129>Oct 28 04:48:54 node-1 haproxy[9182]: 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 28 04:48:54 node-1 haproxy[9182]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:54 node-1 haproxy[9182]: 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 28 04:48:54 node-1 haproxy[9182]: proxy aodh has no server available!
<129>Oct 28 04:48:54 node-1 haproxy[9182]: 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 28 04:48:54 node-1 haproxy[9182]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:54 node-1 haproxy[9182]: 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 28 04:48:54 node-1 haproxy[9182]: proxy ceilometer has no server available!
<129>Oct 28 04:48:54 node-1 haproxy[9182]: 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 28 04:48:54 node-1 haproxy[9182]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:54 node-1 haproxy[9182]: 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 28 04:48:54 node-1 haproxy[9182]: proxy nova-novncproxy has no server available!
<27>Oct 28 04:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:48:55 node-1 multipathd: uevent trigger error
<129>Oct 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: proxy keystone-1 has no server available!
<129>Oct 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: proxy keystone-2 has no server available!
<129>Oct 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: proxy nova-api has no server available!
<129>Oct 28 04:48:58 node-1 haproxy[10821]: 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 28 04:48:58 node-1 haproxy[10821]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy nova-metadata-api has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy cinder-api has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy glance-api has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy glance-glare has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy neutron has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy glance-registry has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy mysqld has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy object-storage has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy aodh has no server available!
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:48:59 node-1 haproxy[10827]: 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 28 04:48:59 node-1 haproxy[10827]: proxy ceilometer has no server available!
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: proxy heat-api has no server available!
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: proxy heat-api-cfn has no server available!
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: proxy heat-api-cloudwatch has no server available!
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 04:49:00 node-1 haproxy[10827]: 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 28 04:49:00 node-1 haproxy[10827]: proxy nova-novncproxy has no server available!
<27>Oct 28 04:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:04 node-1 multipathd: uevent trigger error
<27>Oct 28 04:49:12 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 28 04:49:36 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 28 04:49:38 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 28 04:50:29 node-1 multipathd: uevent trigger error
<27>Oct 28 04:50:29 node-1 multipathd: uevent trigger error
<27>Oct 28 04:50:29 node-1 multipathd: uevent trigger error
<27>Oct 28 04:50:29 node-1 multipathd: uevent trigger error
<27>Oct 28 04:50:29 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 04:52:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:48 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:52:54 node-1 multipathd: uevent trigger error
<43>Oct 28 04:53:12 node-1 apache2_error [Fri Oct 28 04:53:05.835514 2016] [mpm_event:notice] [pid 20596:tid 140106835060608] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 04:53:12 node-1 apache2_error [Fri Oct 28 04:53:05.835645 2016] [core:notice] [pid 20596:tid 140106835060608] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 04:53:12 node-1 apache2_error [Fri Oct 28 04:53:09.237412 2016] [mpm_event:notice] [pid 20596:tid 140106835060608] AH00491: caught SIGTERM, shutting down
<43>Oct 28 04:53:12 node-1 apache2_error [Fri Oct 28 04:53:10.316655 2016] [mpm_worker:notice] [pid 21452:tid 140602100672384] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 04:53:12 node-1 apache2_error [Fri Oct 28 04:53:10.316675 2016] [core:notice] [pid 21452:tid 140602100672384] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 04:53:14 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:14 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:14 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:14 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:14 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:14 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:19 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:19 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:19 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:19 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:22 node-1 multipathd: uevent trigger error
<27>Oct 28 04:53:22 node-1 multipathd: uevent trigger error
<43>Oct 28 04:54:32 node-1 apache2_error [Fri Oct 28 04:54:24.919121 2016] [mpm_worker:notice] [pid 21452:tid 140602100672384] AH00295: caught SIGTERM, shutting down
<43>Oct 28 04:54:32 node-1 apache2_error [Fri Oct 28 04:54:25.665723 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 04:54:32 node-1 apache2_error [Fri Oct 28 04:54:25.665756 2016] [core:notice] [pid 1957:tid 140386045482880] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 04:55:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 28 04:55:12 node-1 apache2_error [Fri Oct 28 04:55:09.345190 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 04:55:12 node-1 apache2_error [Fri Oct 28 04:55:09.537506 2016] [mpm_worker:warn] [pid 1957:tid 140386045482880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 04:55:12 node-1 apache2_error [Fri Oct 28 04:55:09.539782 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 04:55:12 node-1 apache2_error [Fri Oct 28 04:55:09.539794 2016] [core:notice] [pid 1957:tid 140386045482880] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 04:55:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:55 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:55:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:15 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:15 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:15 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:15 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:15 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:36 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:36 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:36 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:36 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:36 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:41 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:41 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:41 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:41 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:41 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:56 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:56 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:56 node-1 multipathd: uevent trigger error
<27>Oct 28 04:56:56 node-1 multipathd: uevent trigger error
<27>Oct 28 04:57:51 node-1 multipathd: uevent trigger error
<27>Oct 28 04:57:51 node-1 multipathd: uevent trigger error
<27>Oct 28 04:57:51 node-1 multipathd: uevent trigger error
<27>Oct 28 04:57:51 node-1 multipathd: uevent trigger error
<27>Oct 28 04:57:51 node-1 multipathd: uevent trigger error
<27>Oct 28 04:58:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 04:58:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:58:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:58:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:58:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:58:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:58:59 node-1 multipathd: uevent trigger error
<27>Oct 28 04:59:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:59:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:59:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:59:54 node-1 multipathd: uevent trigger error
<27>Oct 28 04:59:54 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:00:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:01:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 05:02:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:02:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:02:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:02:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:02:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:02:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:02 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:02 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:02 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:03 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:03 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:03:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:04:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 05:04:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:04:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:04:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:04:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:04:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:04 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:04 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:04 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:05 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:05 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:05:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:07:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 05:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:13 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:18 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:18 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:18 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:18 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:18 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:59 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:59 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:59 node-1 multipathd: uevent trigger error
<27>Oct 28 05:08:59 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:03 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:03 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:03 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:03 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:03 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:07 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:07 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:07 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:07 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:07 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:25 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:25 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:25 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:25 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:57 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:57 node-1 multipathd: uevent trigger error
<27>Oct 28 05:09:57 node-1 multipathd: uevent trigger error
<27>Oct 28 05:10:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 05:10:59 node-1 multipathd: uevent trigger error
<27>Oct 28 05:10:59 node-1 multipathd: uevent trigger error
<27>Oct 28 05:10:59 node-1 multipathd: uevent trigger error
<27>Oct 28 05:11:00 node-1 multipathd: uevent trigger error
<27>Oct 28 05:11:00 node-1 multipathd: uevent trigger error
<27>Oct 28 05:11:15 node-1 multipathd: uevent trigger error
<27>Oct 28 05:11:15 node-1 multipathd: uevent trigger error
<27>Oct 28 05:11:15 node-1 multipathd: uevent trigger error
<27>Oct 28 05:11:15 node-1 multipathd: uevent trigger error
<27>Oct 28 05:11:16 node-1 multipathd: uevent trigger error
<11>Oct 28 05:11:28 node-1 liberasurecode[3064]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:28 node-1 liberasurecode[3064]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:28 node-1 liberasurecode[3064]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:28 node-1 liberasurecode[3064]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:28 node-1 liberasurecode[3088]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:28 node-1 liberasurecode[3088]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:28 node-1 liberasurecode[3088]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:28 node-1 liberasurecode[3088]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:30 node-1 liberasurecode[3656]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:30 node-1 liberasurecode[3656]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:30 node-1 liberasurecode[3656]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:30 node-1 liberasurecode[3656]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4256]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4256]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4256]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4256]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4297]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4297]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4297]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:34 node-1 liberasurecode[4297]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4340]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4340]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4340]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4340]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4398]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4398]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4412]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4412]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4412]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4412]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4442]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4442]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4442]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4442]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4454]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4454]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4454]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:35 node-1 liberasurecode[4454]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:52 node-1 liberasurecode[5392]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:52 node-1 liberasurecode[5392]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:52 node-1 liberasurecode[5392]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:11:52 node-1 liberasurecode[5392]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 05:12:00 node-1 multipathd: uevent trigger error
<27>Oct 28 05:12:00 node-1 multipathd: uevent trigger error
<27>Oct 28 05:12:00 node-1 multipathd: uevent trigger error
<27>Oct 28 05:12:00 node-1 multipathd: uevent trigger error
<27>Oct 28 05:12:00 node-1 multipathd: uevent trigger error
<43>Oct 28 05:12:54 node-1 apache2_error [Fri Oct 28 05:12:47.846275 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 05:12:54 node-1 apache2_error [Fri Oct 28 05:12:48.226925 2016] [mpm_worker:warn] [pid 1957:tid 140386045482880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 05:12:54 node-1 apache2_error [Fri Oct 28 05:12:48.230121 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 05:12:54 node-1 apache2_error [Fri Oct 28 05:12:48.230136 2016] [core:notice] [pid 1957:tid 140386045482880] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 05:13:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 05:13:29 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:29 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:29 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:29 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:29 node-1 multipathd: uevent trigger error
<43>Oct 28 05:13:34 node-1 apache2_error [Fri Oct 28 05:13:25.107018 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 05:13:34 node-1 apache2_error [Fri Oct 28 05:13:25.300146 2016] [mpm_worker:warn] [pid 1957:tid 140386045482880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 05:13:34 node-1 apache2_error [Fri Oct 28 05:13:25.305421 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 05:13:34 node-1 apache2_error [Fri Oct 28 05:13:25.305492 2016] [core:notice] [pid 1957:tid 140386045482880] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 05:13:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:13:36 node-1 multipathd: uevent trigger error
<43>Oct 28 05:14:14 node-1 apache2_error [Fri Oct 28 05:14:10.971313 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 05:14:14 node-1 apache2_error [Fri Oct 28 05:14:11.174326 2016] [mpm_worker:warn] [pid 1957:tid 140386045482880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 05:14:14 node-1 apache2_error [Fri Oct 28 05:14:11.178806 2016] [mpm_worker:notice] [pid 1957:tid 140386045482880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 05:14:14 node-1 apache2_error [Fri Oct 28 05:14:11.178824 2016] [core:notice] [pid 1957:tid 140386045482880] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 05:14:14 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:14 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:14 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:14 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:14 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:20 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:44 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:44 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:44 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:44 node-1 multipathd: uevent trigger error
<27>Oct 28 05:14:44 node-1 multipathd: uevent trigger error
<11>Oct 28 05:15:02 node-1 liberasurecode[9657]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:15:02 node-1 liberasurecode[9657]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:15:02 node-1 liberasurecode[9657]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:15:02 node-1 liberasurecode[9657]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 05:15:04 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:17 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 28 05:15:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:26 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:31 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:31 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:31 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:31 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:31 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:31 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:36 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:50 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:50 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:50 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:50 node-1 multipathd: uevent trigger error
<27>Oct 28 05:15:50 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 05:16:17 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:17 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:17 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:17 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:32 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:32 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:32 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:32 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:32 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:45 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:45 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:45 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:45 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:45 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:52 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:52 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:52 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:52 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:52 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:57 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:57 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:57 node-1 multipathd: uevent trigger error
<27>Oct 28 05:16:57 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:08 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:33 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:33 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:33 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:33 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:33 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:37 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:37 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:37 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:37 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:37 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:42 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:42 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:42 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:42 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:42 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:42 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:47 node-1 multipathd: uevent trigger error
<27>Oct 28 05:17:47 node-1 multipathd: uevent trigger error
<11>Oct 28 05:20:01 node-1 liberasurecode[3230]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:20:01 node-1 liberasurecode[3230]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:20:01 node-1 liberasurecode[3230]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 05:20:01 node-1 liberasurecode[3230]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
