Oct 28 08:38:48 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8385" x-info="http://www.rsyslog.com"] start
Oct 28 08:38:48 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 28 08:38:48 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 28 08:38:48 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 28 08:38:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 28 08:38:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 28 08:38:48 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 28 08:38:48 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 08:38:48 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=9957eeb5-4b7b-4799-b0f0-dd8b16903c91 nomdmonddf nomdmonisw
Oct 28 08:38:48 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 28 08:38:48 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 28 08:38:48 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 28 08:38:48 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 28 08:38:48 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 28 08:38:48 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 28 08:38:48 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 28 08:38:48 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 08:38:48 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 28 08:38:48 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 08:38:48 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 28 08:38:48 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 28 08:38:48 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 28 08:38:48 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 28 08:38:48 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 28 08:38:48 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 28 08:38:48 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 28 08:38:48 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 28 08:38:48 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 28 08:38:48 node-1 kernel: [    0.000000]   2 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000]   3 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000]   4 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000]   5 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000]   6 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000]   7 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000]   8 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000]   9 disabled
Oct 28 08:38:48 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 28 08:38:48 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 28 08:38:48 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 28 08:38:48 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 28 08:38:48 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 28 08:38:48 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 28 08:38:48 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 28 08:38:48 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 28 08:38:48 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 28 08:38:48 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 28 08:38:48 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 28 08:38:48 node-1 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 28 08:38:48 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 28 08:38:48 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 28 08:38:48 node-1 kernel: [    0.000000] Zone ranges:
Oct 28 08:38:48 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 28 08:38:48 node-1 kernel: [    0.000000] Early memory node ranges
Oct 28 08:38:48 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct 28 08:38:48 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 28 08:38:48 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 28 08:38:48 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 28 08:38:48 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct 28 08:38:48 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct 28 08:38:48 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 28 08:38:48 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 28 08:38:48 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 28 08:38:48 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 28 08:38:48 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 28 08:38:48 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 28 08:38:48 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 28 08:38:48 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 28 08:38:48 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 28 08:38:48 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 28 08:38:48 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 28 08:38:48 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 28 08:38:48 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 28 08:38:48 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 28 08:38:48 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 28 08:38:48 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 28 08:38:48 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 28 08:38:48 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 08:38:48 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct 28 08:38:48 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 28 08:38:48 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=9957eeb5-4b7b-4799-b0f0-dd8b16903c91 nomdmonddf nomdmonisw
Oct 28 08:38:48 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 28 08:38:48 node-1 kernel: [    0.000000] Checking aperture...
Oct 28 08:38:48 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 08:38:48 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 28 08:38:48 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 28 08:38:48 node-1 kernel: [    0.000000] Memory: 32653448K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627188K reserved)
Oct 28 08:38:48 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 28 08:38:48 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 28 08:38:48 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 28 08:38:48 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 28 08:38:48 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 28 08:38:48 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 28 08:38:48 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 28 08:38:48 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 28 08:38:48 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 28 08:38:48 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 28 08:38:48 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 28 08:38:48 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 28 08:38:48 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 28 08:38:48 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 28 08:38:48 node-1 kernel: [    0.004000] tsc: Detected 3491.853 MHz processor
Oct 28 08:38:48 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.70 BogoMIPS (lpj=13967412)
Oct 28 08:38:48 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 28 08:38:48 node-1 kernel: [    0.000042] Security Framework initialized
Oct 28 08:38:48 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Oct 28 08:38:48 node-1 kernel: [    0.000061] Yama: becoming mindful.
Oct 28 08:38:48 node-1 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.006353] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.008282] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.008310] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.008597] Initializing cgroup subsys memory
Oct 28 08:38:48 node-1 kernel: [    0.008607] Initializing cgroup subsys devices
Oct 28 08:38:48 node-1 kernel: [    0.008609] Initializing cgroup subsys freezer
Oct 28 08:38:48 node-1 kernel: [    0.008610] Initializing cgroup subsys blkio
Oct 28 08:38:48 node-1 kernel: [    0.008612] Initializing cgroup subsys perf_event
Oct 28 08:38:48 node-1 kernel: [    0.008614] Initializing cgroup subsys hugetlb
Oct 28 08:38:48 node-1 kernel: [    0.008634] CPU: Physical Processor ID: 0
Oct 28 08:38:48 node-1 kernel: [    0.008635] CPU: Processor Core ID: 0
Oct 28 08:38:48 node-1 kernel: [    0.008639] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 28 08:38:48 node-1 kernel: [    0.008639] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 28 08:38:48 node-1 kernel: [    0.009332] mce: CPU supports 22 MCE banks
Oct 28 08:38:48 node-1 kernel: [    0.009360] CPU0: Thermal monitoring enabled (TM1)
Oct 28 08:38:48 node-1 kernel: [    0.009380] process: using mwait in idle threads
Oct 28 08:38:48 node-1 kernel: [    0.009383] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 28 08:38:48 node-1 kernel: [    0.009383] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 28 08:38:48 node-1 kernel: [    0.009383] tlb_flushall_shift: 6
Oct 28 08:38:48 node-1 kernel: [    0.009471] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 28 08:38:48 node-1 kernel: [    0.010194] ACPI: Core revision 20131115
Oct 28 08:38:48 node-1 kernel: [    0.022994] ACPI: All ACPI Tables successfully acquired
Oct 28 08:38:48 node-1 kernel: [    0.023157] ftrace: allocating 28622 entries in 112 pages
Oct 28 08:38:48 node-1 kernel: [    0.031912] dmar: Host address width 46
Oct 28 08:38:48 node-1 kernel: [    0.031914] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 28 08:38:48 node-1 kernel: [    0.031920] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 08:38:48 node-1 kernel: [    0.031922] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 28 08:38:48 node-1 kernel: [    0.031926] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 08:38:48 node-1 kernel: [    0.031927] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 28 08:38:48 node-1 kernel: [    0.031929] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 28 08:38:48 node-1 kernel: [    0.031930] dmar: ATSR flags: 0x0
Oct 28 08:38:48 node-1 kernel: [    0.031931] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 28 08:38:48 node-1 kernel: [    0.031932] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 28 08:38:48 node-1 kernel: [    0.032047] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 28 08:38:48 node-1 kernel: [    0.032048] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 08:38:48 node-1 kernel: [    0.032049] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 08:38:48 node-1 kernel: [    0.032050] HPET id 0 under DRHD base 0xc7ffc000
Oct 28 08:38:48 node-1 kernel: [    0.032052] Your BIOS is broken and requested that x2apic be disabled.
Oct 28 08:38:48 node-1 kernel: [    0.032052] This will slightly decrease performance.
Oct 28 08:38:48 node-1 kernel: [    0.032052] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 28 08:38:48 node-1 kernel: [    0.032485] Enabled IRQ remapping in xapic mode
Oct 28 08:38:48 node-1 kernel: [    0.032486] x2apic not enabled, IRQ remapping is in xapic mode
Oct 28 08:38:48 node-1 kernel: [    0.032490] Switched APIC routing to physical flat.
Oct 28 08:38:48 node-1 kernel: [    0.033067] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 28 08:38:48 node-1 kernel: [    0.072716] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 28 08:38:48 node-1 kernel: [    0.072722] TSC deadline timer enabled
Oct 28 08:38:48 node-1 kernel: [    0.072729] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 28 08:38:48 node-1 kernel: [    0.072735] ... version:                3
Oct 28 08:38:48 node-1 kernel: [    0.072736] ... bit width:              48
Oct 28 08:38:48 node-1 kernel: [    0.072737] ... generic registers:      4
Oct 28 08:38:48 node-1 kernel: [    0.072738] ... value mask:             0000ffffffffffff
Oct 28 08:38:48 node-1 kernel: [    0.072739] ... max period:             0000ffffffffffff
Oct 28 08:38:48 node-1 kernel: [    0.072740] ... fixed-purpose events:   3
Oct 28 08:38:48 node-1 kernel: [    0.072741] ... event mask:             000000070000000f
Oct 28 08:38:48 node-1 kernel: [    0.074150] x86: Booting SMP configuration:
Oct 28 08:38:48 node-1 kernel: [    0.088254] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 28 08:38:48 node-1 kernel: [    0.074152] .... node  #0, CPUs:        #1  #2  #3
Oct 28 08:38:48 node-1 kernel: [    0.116164] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 28 08:38:48 node-1 kernel: [    0.270000] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 28 08:38:48 node-1 kernel: [    0.325613] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 28 08:38:48 node-1 kernel: [    0.382475] x86: Booted up 2 nodes, 16 CPUs
Oct 28 08:38:48 node-1 kernel: [    0.382478] smpboot: Total of 16 processors activated (111751.77 BogoMIPS)
Oct 28 08:38:48 node-1 kernel: [    0.406037] devtmpfs: initialized
Oct 28 08:38:48 node-1 kernel: [    0.408517] EVM: security.selinux
Oct 28 08:38:48 node-1 kernel: [    0.408518] EVM: security.SMACK64
Oct 28 08:38:48 node-1 kernel: [    0.408519] EVM: security.ima
Oct 28 08:38:48 node-1 kernel: [    0.408520] EVM: security.capability
Oct 28 08:38:48 node-1 kernel: [    0.408583] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.409227] pinctrl core: initialized pinctrl subsystem
Oct 28 08:38:48 node-1 kernel: [    0.409289] regulator-dummy: no parameters
Oct 28 08:38:48 node-1 kernel: [    0.409321] RTC time:  8:38:08, date: 10/28/16
Oct 28 08:38:48 node-1 kernel: [    0.409354] NET: Registered protocol family 16
Oct 28 08:38:48 node-1 kernel: [    0.409438] cpuidle: using governor ladder
Oct 28 08:38:48 node-1 kernel: [    0.409439] cpuidle: using governor menu
Oct 28 08:38:48 node-1 kernel: [    0.409473] ACPI: bus type PCI registered
Oct 28 08:38:48 node-1 kernel: [    0.409475] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 28 08:38:48 node-1 kernel: [    0.409519] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 28 08:38:48 node-1 kernel: [    0.409521] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 28 08:38:48 node-1 kernel: [    0.423267] PCI: Using configuration type 1 for base access
Oct 28 08:38:48 node-1 kernel: [    0.424260] bio: create slab <bio-0> at 0
Oct 28 08:38:48 node-1 kernel: [    0.424552] ACPI: Added _OSI(Module Device)
Oct 28 08:38:48 node-1 kernel: [    0.424554] ACPI: Added _OSI(Processor Device)
Oct 28 08:38:48 node-1 kernel: [    0.424555] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 28 08:38:48 node-1 kernel: [    0.424556] ACPI: Added _OSI(Processor Aggregator Device)
Oct 28 08:38:48 node-1 kernel: [    0.437185] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 28 08:38:48 node-1 kernel: [    0.447702] ACPI: Interpreter enabled
Oct 28 08:38:48 node-1 kernel: [    0.447708] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 28 08:38:48 node-1 kernel: [    0.447712] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 28 08:38:48 node-1 kernel: [    0.447715] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 28 08:38:48 node-1 kernel: [    0.447722] ACPI: (supports S0 S4 S5)
Oct 28 08:38:48 node-1 kernel: [    0.447723] ACPI: Using IOAPIC for interrupt routing
Oct 28 08:38:48 node-1 kernel: [    0.447765] HEST: Table parsing has been initialized.
Oct 28 08:38:48 node-1 kernel: [    0.447768] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 28 08:38:48 node-1 kernel: [    0.448320] ACPI: No dock devices found.
Oct 28 08:38:48 node-1 kernel: [    0.459823] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 28 08:38:48 node-1 kernel: [    0.459828] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 08:38:48 node-1 kernel: [    0.459831] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 08:38:48 node-1 kernel: [    0.459860] PCI host bridge to bus 0000:ff
Oct 28 08:38:48 node-1 kernel: [    0.459862] pci_bus 0000:ff: root bus resource [bus ff]
Oct 28 08:38:48 node-1 kernel: [    0.459870] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.459909] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.459939] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.459975] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460004] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.460033] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.460064] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460093] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460124] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460152] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460178] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460205] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460233] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460259] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460286] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460312] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460341] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460368] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460395] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.460423] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460449] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.460474] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460500] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460532] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.460567] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460598] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460628] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460659] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460689] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460720] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460751] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460781] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460812] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460845] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460876] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460907] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460940] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460970] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.460997] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461028] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461062] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461102] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461137] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461171] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461200] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461231] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461261] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461290] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461323] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461355] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461386] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461416] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461445] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461475] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461504] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461535] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461566] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461623] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 28 08:38:48 node-1 kernel: [    0.461625] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 08:38:48 node-1 kernel: [    0.461628] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 08:38:48 node-1 kernel: [    0.461646] PCI host bridge to bus 0000:7f
Oct 28 08:38:48 node-1 kernel: [    0.461647] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 28 08:38:48 node-1 kernel: [    0.461652] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461680] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.461706] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461735] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461756] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.461781] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.461806] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461833] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461855] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461878] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461903] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461926] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461950] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.461976] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462002] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462032] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462054] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462077] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462100] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.462124] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462146] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.462168] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462191] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462217] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 08:38:48 node-1 kernel: [    0.462251] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462277] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462303] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462330] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462355] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462381] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462408] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462439] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462463] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462492] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462520] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462548] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462577] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462604] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462630] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462660] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462685] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462712] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462740] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462768] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462793] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462818] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462843] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462870] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462895] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462920] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462949] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462975] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.462997] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.463023] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.463047] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.463075] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.463101] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.464357] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 28 08:38:48 node-1 kernel: [    0.464361] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 08:38:48 node-1 kernel: [    0.465490] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 08:38:48 node-1 kernel: [    0.466002] PCI host bridge to bus 0000:00
Oct 28 08:38:48 node-1 kernel: [    0.466005] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 28 08:38:48 node-1 kernel: [    0.466006] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 28 08:38:48 node-1 kernel: [    0.466008] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 28 08:38:48 node-1 kernel: [    0.466009] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 28 08:38:48 node-1 kernel: [    0.466010] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 28 08:38:48 node-1 kernel: [    0.466012] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 28 08:38:48 node-1 kernel: [    0.466013] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 28 08:38:48 node-1 kernel: [    0.466019] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 28 08:38:48 node-1 kernel: [    0.466102] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.466133] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.466174] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 28 08:38:48 node-1 kernel: [    0.466194] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.466224] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.466263] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 28 08:38:48 node-1 kernel: [    0.466283] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.466312] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.466352] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 28 08:38:48 node-1 kernel: [    0.466370] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.466441] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.466519] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.466595] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 08:38:48 node-1 kernel: [    0.466600] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 28 08:38:48 node-1 kernel: [    0.466686] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 28 08:38:48 node-1 kernel: [    0.466834] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 28 08:38:48 node-1 kernel: [    0.466852] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 28 08:38:48 node-1 kernel: [    0.466930] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.466985] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 28 08:38:48 node-1 kernel: [    0.467008] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.467064] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.467107] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 28 08:38:48 node-1 kernel: [    0.467135] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.467191] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.467234] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 28 08:38:48 node-1 kernel: [    0.467259] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 28 08:38:48 node-1 kernel: [    0.467276] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 28 08:38:48 node-1 kernel: [    0.467354] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.467404] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 28 08:38:48 node-1 kernel: [    0.467431] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 28 08:38:48 node-1 kernel: [    0.467679] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 28 08:38:48 node-1 kernel: [    0.467685] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 28 08:38:48 node-1 kernel: [    0.467691] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.467697] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.467704] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 28 08:38:48 node-1 kernel: [    0.467734] pci 0000:01:00.0: supports D1 D2
Oct 28 08:38:48 node-1 kernel: [    0.477978] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 08:38:48 node-1 kernel: [    0.477985] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 08:38:48 node-1 kernel: [    0.477989] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 08:38:48 node-1 kernel: [    0.478251] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.478310] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 28 08:38:48 node-1 kernel: [    0.485976] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 08:38:48 node-1 kernel: [    0.485982] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.485986] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 08:38:48 node-1 kernel: [    0.486070] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.486142] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.486236] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.486332] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 08:38:48 node-1 kernel: [    0.486340] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.486344] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 08:38:48 node-1 kernel: [    0.486433] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.486555] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.486613] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 08:38:48 node-1 kernel: [    0.486616] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.486618] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.486666] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.486786] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.486823] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.486943] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.486979] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.487100] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.487136] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 28 08:38:48 node-1 kernel: [    0.487269] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 28 08:38:48 node-1 kernel: [    0.487315] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 08:38:48 node-1 kernel: [    0.487317] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.487319] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.487380] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 28 08:38:48 node-1 kernel: [    0.487443] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.487495] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.487552] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 28 08:38:48 node-1 kernel: [    0.487637] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 28 08:38:48 node-1 kernel: [    0.487743] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 08:38:48 node-1 kernel: [    0.487745] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.487747] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.487803] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 28 08:38:48 node-1 kernel: [    0.487856] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.487905] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.488117] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 08:38:48 node-1 kernel: [    0.488121] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 08:38:48 node-1 kernel: [    0.488185] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 28 08:38:48 node-1 kernel: [    0.488238] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.488311] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.488519] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 08:38:48 node-1 kernel: [    0.488523] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 08:38:48 node-1 kernel: [    0.488582] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 28 08:38:48 node-1 kernel: [    0.488643] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.488698] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 28 08:38:48 node-1 kernel: [    0.488921] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 08:38:48 node-1 kernel: [    0.488924] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 08:38:48 node-1 kernel: [    0.489099] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 08:38:48 node-1 kernel: [    0.489138] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 08:38:48 node-1 kernel: [    0.489216] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 28 08:38:48 node-1 kernel: [    0.489235] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 28 08:38:48 node-1 kernel: [    0.489248] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 28 08:38:48 node-1 kernel: [    0.489261] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 28 08:38:48 node-1 kernel: [    0.489312] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 28 08:38:48 node-1 kernel: [    0.493982] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 08:38:48 node-1 kernel: [    0.493991] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 08:38:48 node-1 kernel: [    0.494043] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 28 08:38:48 node-1 kernel: [    0.494745] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 28 08:38:48 node-1 kernel: [    0.494748] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 08:38:48 node-1 kernel: [    0.494868] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 08:38:48 node-1 kernel: [    0.494978] PCI host bridge to bus 0000:80
Oct 28 08:38:48 node-1 kernel: [    0.494980] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 28 08:38:48 node-1 kernel: [    0.494982] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 28 08:38:48 node-1 kernel: [    0.494983] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 28 08:38:48 node-1 kernel: [    0.494991] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.495055] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.495124] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 08:38:48 node-1 kernel: [    0.495187] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 08:38:48 node-1 kernel: [    0.495192] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 28 08:38:48 node-1 kernel: [    0.495264] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 28 08:38:48 node-1 kernel: [    0.495561] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 28 08:38:48 node-1 kernel: [    0.495592] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 28 08:38:48 node-1 kernel: [    0.495622] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 28 08:38:48 node-1 kernel: [    0.495651] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 28 08:38:48 node-1 kernel: [    0.495681] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 08:38:48 node-1 kernel: [    0.495711] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 08:38:48 node-1 kernel: [    0.495740] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 08:38:48 node-1 kernel: [    0.495770] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 08:38:48 node-1 kernel: [    0.495855] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 28 08:38:48 node-1 kernel: [    0.495859] ACPI: \_SB_.UNC1: notify handler is installed
Oct 28 08:38:48 node-1 kernel: [    0.495860] ACPI: \_SB_.UNC0: notify handler is installed
Oct 28 08:38:48 node-1 kernel: [    0.495875] ACPI: \_SB_.PCI0: notify handler is installed
Oct 28 08:38:48 node-1 kernel: [    0.495927] ACPI: \_SB_.PCI1: notify handler is installed
Oct 28 08:38:48 node-1 kernel: [    0.496007] Found 4 acpi root devices
Oct 28 08:38:48 node-1 kernel: [    0.496114] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 28 08:38:48 node-1 kernel: [    0.496117] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 28 08:38:48 node-1 kernel: [    0.496118] vgaarb: loaded
Oct 28 08:38:48 node-1 kernel: [    0.496119] vgaarb: bridge control possible 0000:0c:00.0
Oct 28 08:38:48 node-1 kernel: [    0.496238] SCSI subsystem initialized
Oct 28 08:38:48 node-1 kernel: [    0.496309] libata version 3.00 loaded.
Oct 28 08:38:48 node-1 kernel: [    0.496325] ACPI: bus type USB registered
Oct 28 08:38:48 node-1 kernel: [    0.496335] usbcore: registered new interface driver usbfs
Oct 28 08:38:48 node-1 kernel: [    0.496341] usbcore: registered new interface driver hub
Oct 28 08:38:48 node-1 kernel: [    0.496362] usbcore: registered new device driver usb
Oct 28 08:38:48 node-1 kernel: [    0.496543] PCI: Using ACPI for IRQ routing
Oct 28 08:38:48 node-1 kernel: [    0.500157] PCI: pci_cache_line_size set to 64 bytes
Oct 28 08:38:48 node-1 kernel: [    0.500383] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 28 08:38:48 node-1 kernel: [    0.500384] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct 28 08:38:48 node-1 kernel: [    0.500384] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 28 08:38:48 node-1 kernel: [    0.500449] NetLabel: Initializing
Oct 28 08:38:48 node-1 kernel: [    0.500451] NetLabel:  domain hash size = 128
Oct 28 08:38:48 node-1 kernel: [    0.500452] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 28 08:38:48 node-1 kernel: [    0.500461] NetLabel:  unlabeled traffic allowed by default
Oct 28 08:38:48 node-1 kernel: [    0.500518] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 28 08:38:48 node-1 kernel: [    0.500522] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 28 08:38:48 node-1 kernel: [    0.502578] Switched to clocksource hpet
Oct 28 08:38:48 node-1 kernel: [    0.506537] AppArmor: AppArmor Filesystem Enabled
Oct 28 08:38:48 node-1 kernel: [    0.506553] pnp: PnP ACPI init
Oct 28 08:38:48 node-1 kernel: [    0.506560] ACPI: bus type PNP registered
Oct 28 08:38:48 node-1 kernel: [    0.506675] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 28 08:38:48 node-1 kernel: [    0.506683] pnp 00:01: [dma 4]
Oct 28 08:38:48 node-1 kernel: [    0.506695] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 28 08:38:48 node-1 kernel: [    0.506721] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 28 08:38:48 node-1 kernel: [    0.506741] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 28 08:38:48 node-1 kernel: [    0.506759] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 28 08:38:48 node-1 kernel: [    0.506792] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 28 08:38:48 node-1 kernel: [    0.506843] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506845] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 28 08:38:48 node-1 kernel: [    0.506847] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506849] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506850] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506854] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506857] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 28 08:38:48 node-1 kernel: [    0.506858] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506860] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506861] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506863] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506864] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506866] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 28 08:38:48 node-1 kernel: [    0.506868] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 28 08:38:48 node-1 kernel: [    0.506951] pnp 00:07: [dma 0 disabled]
Oct 28 08:38:48 node-1 kernel: [    0.506980] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 08:38:48 node-1 kernel: [    0.507054] pnp 00:08: [dma 0 disabled]
Oct 28 08:38:48 node-1 kernel: [    0.507085] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 08:38:48 node-1 kernel: [    0.507136] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 28 08:38:48 node-1 kernel: [    0.507482] pnp: PnP ACPI: found 10 devices
Oct 28 08:38:48 node-1 kernel: [    0.507483] ACPI: bus type PNP unregistered
Oct 28 08:38:48 node-1 kernel: [    0.513778] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 08:38:48 node-1 kernel: [    0.513781] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 08:38:48 node-1 kernel: [    0.513784] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 08:38:48 node-1 kernel: [    0.513788] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 08:38:48 node-1 kernel: [    0.513790] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.513804] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.513834] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 08:38:48 node-1 kernel: [    0.513848] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 08:38:48 node-1 kernel: [    0.513877] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 08:38:48 node-1 kernel: [    0.513891] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 08:38:48 node-1 kernel: [    0.513923] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 08:38:48 node-1 kernel: [    0.513938] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 08:38:48 node-1 kernel: [    0.513966] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 08:38:48 node-1 kernel: [    0.513968] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.513983] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514011] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 08:38:48 node-1 kernel: [    0.514013] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514028] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514057] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 08:38:48 node-1 kernel: [    0.514058] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514061] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514065] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 08:38:48 node-1 kernel: [    0.514067] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514069] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514073] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 08:38:48 node-1 kernel: [    0.514078] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 08:38:48 node-1 kernel: [    0.514086] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 08:38:48 node-1 kernel: [    0.514089] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 08:38:48 node-1 kernel: [    0.514095] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 28 08:38:48 node-1 kernel: [    0.514096] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 28 08:38:48 node-1 kernel: [    0.514097] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 28 08:38:48 node-1 kernel: [    0.514098] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 28 08:38:48 node-1 kernel: [    0.514099] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 28 08:38:48 node-1 kernel: [    0.514100] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 28 08:38:48 node-1 kernel: [    0.514101] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 28 08:38:48 node-1 kernel: [    0.514102] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 28 08:38:48 node-1 kernel: [    0.514103] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514104] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514104] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514105] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514106] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514107] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514108] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514109] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514110] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 28 08:38:48 node-1 kernel: [    0.514111] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514112] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 28 08:38:48 node-1 kernel: [    0.514113] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 28 08:38:48 node-1 kernel: [    0.514114] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 28 08:38:48 node-1 kernel: [    0.514115] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 28 08:38:48 node-1 kernel: [    0.514117] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 28 08:38:48 node-1 kernel: [    0.514118] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 28 08:38:48 node-1 kernel: [    0.514155] NET: Registered protocol family 2
Oct 28 08:38:48 node-1 kernel: [    0.514416] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.514752] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.514897] TCP: Hash tables configured (established 262144 bind 65536)
Oct 28 08:38:48 node-1 kernel: [    0.514933] TCP: reno registered
Oct 28 08:38:48 node-1 kernel: [    0.514965] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.515060] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.515209] NET: Registered protocol family 1
Oct 28 08:38:48 node-1 kernel: [    0.550678] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 28 08:38:48 node-1 kernel: [    0.550692] PCI: CLS 64 bytes, default 64
Oct 28 08:38:48 node-1 kernel: [    0.550769] Trying to unpack rootfs image as initramfs...
Oct 28 08:38:48 node-1 kernel: [    0.770207] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Oct 28 08:38:48 node-1 kernel: [    0.770246] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 28 08:38:48 node-1 kernel: [    0.770248] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct 28 08:38:48 node-1 kernel: [    0.770666] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770672] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770677] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770682] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770694] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770711] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770726] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770741] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770753] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770763] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770769] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770775] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770784] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770797] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770810] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770823] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 08:38:48 node-1 kernel: [    0.770935] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 28 08:38:48 node-1 kernel: [    0.770941] Scanning for low memory corruption every 60 seconds
Oct 28 08:38:48 node-1 kernel: [    0.771360] Initialise system trusted keyring
Oct 28 08:38:48 node-1 kernel: [    0.771414] audit: initializing netlink socket (disabled)
Oct 28 08:38:48 node-1 kernel: [    0.771430] type=2000 audit(1477643887.716:1): initialized
Oct 28 08:38:48 node-1 kernel: [    0.789179] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 28 08:38:48 node-1 kernel: [    0.790708] zbud: loaded
Oct 28 08:38:48 node-1 kernel: [    0.790835] VFS: Disk quotas dquot_6.5.2
Oct 28 08:38:48 node-1 kernel: [    0.790871] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 28 08:38:48 node-1 kernel: [    0.791245] fuse init (API version 7.22)
Oct 28 08:38:48 node-1 kernel: [    0.791306] msgmni has been set to 32768
Oct 28 08:38:48 node-1 kernel: [    0.791356] Key type big_key registered
Oct 28 08:38:48 node-1 kernel: [    0.791873] Key type asymmetric registered
Oct 28 08:38:48 node-1 kernel: [    0.791874] Asymmetric key parser 'x509' registered
Oct 28 08:38:48 node-1 kernel: [    0.791896] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 28 08:38:48 node-1 kernel: [    0.791973] io scheduler noop registered
Oct 28 08:38:48 node-1 kernel: [    0.791974] io scheduler deadline registered (default)
Oct 28 08:38:48 node-1 kernel: [    0.791996] io scheduler cfq registered
Oct 28 08:38:48 node-1 kernel: [    0.792416] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    0.792537] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    0.792649] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    0.792775] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    0.792885] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    0.793003] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    0.793383] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 28 08:38:48 node-1 kernel: [    0.793409] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 28 08:38:48 node-1 kernel: [    0.793425] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 28 08:38:48 node-1 kernel: [    0.793434] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793436] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793439] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 28 08:38:48 node-1 kernel: [    0.793444] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793445] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793447] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793448] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793450] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793451] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793453] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793454] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793455] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793457] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793458] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793460] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793462] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 28 08:38:48 node-1 kernel: [    0.793467] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793470] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 28 08:38:48 node-1 kernel: [    0.793482] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793485] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 28 08:38:48 node-1 kernel: [    0.793496] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793497] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 28 08:38:48 node-1 kernel: [    0.793500] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 28 08:38:48 node-1 kernel: [    0.793535] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 28 08:38:48 node-1 kernel: [    0.793541] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 28 08:38:48 node-1 kernel: [    0.793545] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 28 08:38:48 node-1 kernel: [    0.793554] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 28 08:38:48 node-1 kernel: [    0.793594] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 28 08:38:48 node-1 kernel: [    0.793596] vesafb: scrolling: redraw
Oct 28 08:38:48 node-1 kernel: [    0.793597] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 28 08:38:48 node-1 kernel: [    0.814099] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 28 08:38:48 node-1 kernel: [    0.822592] Console: switching to colour frame buffer device 80x30
Oct 28 08:38:48 node-1 kernel: [    0.831252] fb0: VESA VGA frame buffer device
Oct 28 08:38:48 node-1 kernel: [    0.831449] intel_idle: MWAIT substates: 0x2120
Oct 28 08:38:48 node-1 kernel: [    0.831450] intel_idle: v0.4 model 0x3F
Oct 28 08:38:48 node-1 kernel: [    0.831450] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 28 08:38:48 node-1 kernel: [    0.831682] ipmi message handler version 39.2
Oct 28 08:38:48 node-1 kernel: [    0.831959] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 28 08:38:48 node-1 kernel: [    0.832392] ACPI: AC Adapter [P111] (on-line)
Oct 28 08:38:48 node-1 kernel: [    0.837599] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 28 08:38:48 node-1 kernel: [    0.848573] ACPI: Power Button [PWRB]
Oct 28 08:38:48 node-1 kernel: [    0.854300] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 28 08:38:48 node-1 kernel: [    0.865904] ACPI: Power Button [PWRF]
Oct 28 08:38:48 node-1 kernel: [    0.892098] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 28 08:38:48 node-1 kernel: [    0.903718] pstore: Registered erst as persistent store backend
Oct 28 08:38:48 node-1 kernel: [    0.909903] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 28 08:38:48 node-1 kernel: [    0.921810] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 28 08:38:48 node-1 kernel: [    0.948571] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 28 08:38:48 node-1 kernel: [    0.981811] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 28 08:38:48 node-1 kernel: [    0.995830] Linux agpgart interface v0.103
Oct 28 08:38:48 node-1 kernel: [    1.003440] brd: module loaded
Oct 28 08:38:48 node-1 kernel: [    1.010452] loop: module loaded
Oct 28 08:38:48 node-1 kernel: [    1.017156] libphy: Fixed MDIO Bus: probed
Oct 28 08:38:48 node-1 kernel: [    1.023600] tun: Universal TUN/TAP device driver, 1.6
Oct 28 08:38:48 node-1 kernel: [    1.030089] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 28 08:38:48 node-1 kernel: [    1.036696] PPP generic driver version 2.4.2
Oct 28 08:38:48 node-1 kernel: [    1.043126] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 28 08:38:48 node-1 kernel: [    1.049544] ehci-pci: EHCI PCI platform driver
Oct 28 08:38:48 node-1 kernel: [    1.056049] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 28 08:38:48 node-1 kernel: [    1.062450] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 28 08:38:48 node-1 kernel: [    1.074973] ehci-pci 0000:00:1a.0: debug port 2
Oct 28 08:38:48 node-1 kernel: [    1.085164] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 28 08:38:48 node-1 kernel: [    1.085183] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 28 08:38:48 node-1 kernel: [    1.102074] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 28 08:38:48 node-1 kernel: [    1.108136] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 08:38:48 node-1 kernel: [    1.114308] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 08:38:48 node-1 kernel: [    1.126219] usb usb1: Product: EHCI Host Controller
Oct 28 08:38:48 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 08:38:48 node-1 kernel: [    1.132244] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 08:38:48 node-1 kernel: [    1.138282] usb usb1: SerialNumber: 0000:00:1a.0
Oct 28 08:38:48 node-1 kernel: [    1.144224] hub 1-0:1.0: USB hub found
Oct 28 08:38:48 node-1 kernel: [    1.149978] hub 1-0:1.0: 2 ports detected
Oct 28 08:38:48 node-1 kernel: [    1.155754] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 28 08:38:48 node-1 kernel: [    1.161336] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 28 08:38:48 node-1 kernel: [    1.172238] ehci-pci 0000:00:1d.0: debug port 2
Oct 28 08:38:48 node-1 kernel: [    1.181547] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 28 08:38:48 node-1 kernel: [    1.181550] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 28 08:38:48 node-1 kernel: [    1.197992] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 28 08:38:48 node-1 kernel: [    1.203189] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 08:38:48 node-1 kernel: [    1.208500] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 08:38:48 node-1 kernel: [    1.219087] usb usb2: Product: EHCI Host Controller
Oct 28 08:38:48 node-1 kernel: [    1.224554] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 08:38:48 node-1 kernel: [    1.230115] usb usb2: SerialNumber: 0000:00:1d.0
Oct 28 08:38:48 node-1 kernel: [    1.235646] hub 2-0:1.0: USB hub found
Oct 28 08:38:48 node-1 kernel: [    1.241012] hub 2-0:1.0: 2 ports detected
Oct 28 08:38:48 node-1 kernel: [    1.246323] ehci-platform: EHCI generic platform driver
Oct 28 08:38:48 node-1 kernel: [    1.251575] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 28 08:38:48 node-1 kernel: [    1.256935] ohci-pci: OHCI PCI platform driver
Oct 28 08:38:48 node-1 kernel: [    1.262286] ohci-platform: OHCI generic platform driver
Oct 28 08:38:48 node-1 kernel: [    1.267532] uhci_hcd: USB Universal Host Controller Interface driver
Oct 28 08:38:48 node-1 kernel: [    1.272912] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 28 08:38:48 node-1 kernel: [    1.465769] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 28 08:38:48 node-1 kernel: [    1.765525] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 28 08:38:48 node-1 kernel: [    1.781823] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 28 08:38:48 node-1 kernel: [    1.787453] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 08:38:48 node-1 kernel: [    1.793216] hub 1-1:1.0: USB hub found
Oct 28 08:38:48 node-1 kernel: [    1.798809] hub 1-1:1.0: 6 ports detected
Oct 28 08:38:48 node-1 kernel: [    1.913383] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 28 08:38:48 node-1 kernel: [    2.311646] i8042: No controller found
Oct 28 08:38:48 node-1 kernel: [    2.317183] mousedev: PS/2 mouse device common for all mice
Oct 28 08:38:48 node-1 kernel: [    2.322905] rtc_cmos 00:02: RTC can wake from S4
Oct 28 08:38:48 node-1 kernel: [    2.328631] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 28 08:38:48 node-1 kernel: [    2.329800] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 28 08:38:48 node-1 kernel: [    2.329801] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 08:38:48 node-1 kernel: [    2.330318] hub 2-1:1.0: USB hub found
Oct 28 08:38:48 node-1 kernel: [    2.330547] hub 2-1:1.0: 8 ports detected
Oct 28 08:38:48 node-1 kernel: [    2.356781] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 28 08:38:48 node-1 kernel: [    2.368089] device-mapper: uevent: version 1.0.3
Oct 28 08:38:48 node-1 kernel: [    2.373800] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 28 08:38:48 node-1 kernel: [    2.385190] ledtrig-cpu: registered to indicate activity on CPUs
Oct 28 08:38:48 node-1 kernel: [    2.391163] TCP: cubic registered
Oct 28 08:38:48 node-1 kernel: [    2.397037] NET: Registered protocol family 10
Oct 28 08:38:48 node-1 kernel: [    2.403076] NET: Registered protocol family 17
Oct 28 08:38:48 node-1 kernel: [    2.408850] Key type dns_resolver registered
Oct 28 08:38:48 node-1 kernel: [    2.414911] Loading compiled-in X.509 certificates
Oct 28 08:38:48 node-1 kernel: [    2.421166] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 28 08:38:48 node-1 kernel: [    2.432830] registered taskstats version 1
Oct 28 08:38:48 node-1 kernel: [    2.440888] Key type trusted registered
Oct 28 08:38:48 node-1 kernel: [    2.448505] Key type encrypted registered
Oct 28 08:38:48 node-1 kernel: [    2.454020] AppArmor: AppArmor sha1 policy hashing enabled
Oct 28 08:38:48 node-1 kernel: [    2.459545] IMA: No TPM chip found, activating TPM-bypass!
Oct 28 08:38:48 node-1 kernel: [    2.465634] regulator-dummy: disabling
Oct 28 08:38:48 node-1 kernel: [    2.471213]   Magic number: 4:557:625
Oct 28 08:38:48 node-1 kernel: [    2.477034] rtc_cmos 00:02: setting system clock to 2016-10-28 08:38:10 UTC (1477643890)
Oct 28 08:38:48 node-1 kernel: [    2.489672] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 28 08:38:48 node-1 kernel: [    2.495395] EDD information not available.
Oct 28 08:38:48 node-1 kernel: [    2.501050] PM: Hibernation image not present or could not be loaded.
Oct 28 08:38:48 node-1 kernel: [    2.501914] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 28 08:38:48 node-1 kernel: [    2.513544] Write protecting the kernel read-only data: 12288k
Oct 28 08:38:48 node-1 kernel: [    2.519915] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 28 08:38:48 node-1 kernel: [    2.532836] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 28 08:38:48 node-1 kernel: [    2.565121] device-mapper: multipath: version 1.6.0 loaded
Oct 28 08:38:48 node-1 kernel: [    2.573251] systemd-udevd[214]: starting version 204
Oct 28 08:38:48 node-1 kernel: [    2.599536] md: linear personality registered for level -1
Oct 28 08:38:48 node-1 kernel: [    2.613172] md: multipath personality registered for level -4
Oct 28 08:38:48 node-1 kernel: [    2.620823] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 28 08:38:48 node-1 kernel: [    2.627379] md: raid0 personality registered for level 0
Oct 28 08:38:48 node-1 kernel: [    2.635792] md: raid1 personality registered for level 1
Oct 28 08:38:48 node-1 kernel: [    2.642313] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 28 08:38:48 node-1 kernel: [    2.642315] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 28 08:38:48 node-1 kernel: [    2.642526] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 28 08:38:48 node-1 kernel: [    2.643887] megasas: FW now in Ready state
Oct 28 08:38:48 node-1 kernel: [    2.644230] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.644388] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.644497] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.644566] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.644717] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645075] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645289] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645326] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645449] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645566] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645711] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645787] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.645890] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.646076] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.646210] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.646379] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.647244] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 28 08:38:48 node-1 kernel: [    2.687963] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct 28 08:38:48 node-1 kernel: [    2.701152] 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 08:38:48 node-1 kernel: [    2.714915] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 08:38:48 node-1 kernel: [    2.722430] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.722435] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.722439] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.722444] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.722484] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.744695] raid6: sse2x1   10138 MB/s
Oct 28 08:38:48 node-1 kernel: [    2.746693] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct 28 08:38:48 node-1 kernel: [    2.746694] 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 08:38:48 node-1 kernel: [    2.746695] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 28 08:38:48 node-1 kernel: [    2.746756] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.746796] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.746833] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.746874] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.746900] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.746938] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.747030] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.757949] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 28 08:38:48 node-1 kernel: [    2.757951] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 28 08:38:48 node-1 kernel: [    2.757952] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 28 08:38:48 node-1 kernel: [    2.757953] usb 2-1.4: Manufacturer: Avocent
Oct 28 08:38:48 node-1 kernel: [    2.757953] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 28 08:38:48 node-1 kernel: [    2.760259] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct 28 08:38:48 node-1 kernel: [    2.760261] 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 08:38:48 node-1 kernel: [    2.760261] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 08:38:48 node-1 kernel: [    2.760326] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.760361] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.760400] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.760436] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.760495] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 08:38:48 node-1 kernel: [    2.772100] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct 28 08:38:48 node-1 kernel: [    2.772102] 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 08:38:48 node-1 kernel: [    2.772103] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 08:38:48 node-1 kernel: [    2.980497] raid6: sse2x2    9791 MB/s
Oct 28 08:38:48 node-1 kernel: [    3.052433] raid6: sse2x4   10141 MB/s
Oct 28 08:38:48 node-1 kernel: [    3.124378] raid6: avx2x1   14944 MB/s
Oct 28 08:38:48 node-1 kernel: [    3.196305] raid6: avx2x2   18875 MB/s
Oct 28 08:38:48 node-1 kernel: [    3.268254] raid6: avx2x4   21412 MB/s
Oct 28 08:38:48 node-1 kernel: [    3.274344] raid6: using algorithm avx2x4 (21412 MB/s)
Oct 28 08:38:48 node-1 kernel: [    3.280374] raid6: using avx2x2 recovery algorithm
Oct 28 08:38:48 node-1 kernel: [    3.286240] megasas:IOC Init cmd success
Oct 28 08:38:48 node-1 kernel: [    3.286242] Switched to clocksource tsc
Oct 28 08:38:48 node-1 kernel: [    3.286285] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    3.286324] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    3.286362] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    3.286399] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 28 08:38:48 node-1 kernel: [    3.286501] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 08:38:48 node-1 kernel: [    3.308253] megasas: INIT adapter done
Oct 28 08:38:48 node-1 kernel: [    3.314588] hidraw: raw HID events driver (C) Jiri Kosina
Oct 28 08:38:48 node-1 kernel: [    3.320365] xor: automatically using best checksumming function:
Oct 28 08:38:48 node-1 kernel: [    3.327680] usbcore: registered new interface driver usbhid
Oct 28 08:38:48 node-1 kernel: [    3.333380] usbhid: USB HID core driver
Oct 28 08:38:48 node-1 kernel: [    3.339877] 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 08:38:48 node-1 kernel: [    3.351634] 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 08:38:48 node-1 kernel: [    3.363523] 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 08:38:48 node-1 kernel: [    3.364144]    avx       : 35729.000 MB/sec
Oct 28 08:38:48 node-1 kernel: [    3.381374] 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 08:38:48 node-1 kernel: [    3.384288] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 28 08:38:48 node-1 kernel: [    3.386215] scsi0 : LSI SAS based MegaRAID driver
Oct 28 08:38:48 node-1 kernel: [    3.394338] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 08:38:48 node-1 kernel: [    3.417199] async_tx: api initialized (async)
Oct 28 08:38:48 node-1 kernel: [    3.417220] 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 08:38:48 node-1 kernel: [    3.417476] 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 08:38:48 node-1 kernel: [    3.426129] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 08:38:48 node-1 kernel: [    3.430293] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 28 08:38:48 node-1 kernel: [    3.430350] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 28 08:38:48 node-1 kernel: [    3.430664] sd 0:2:0:0: [sda] Write Protect is off
Oct 28 08:38:48 node-1 kernel: [    3.430665] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 28 08:38:48 node-1 kernel: [    3.430733] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 28 08:38:48 node-1 kernel: [    3.457692]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 28 08:38:48 node-1 kernel: [    3.459431] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 28 08:38:48 node-1 kernel: [    3.522238] md: raid6 personality registered for level 6
Oct 28 08:38:48 node-1 kernel: [    3.529395] md: raid5 personality registered for level 5
Oct 28 08:38:48 node-1 kernel: [    3.536364] md: raid4 personality registered for level 4
Oct 28 08:38:48 node-1 kernel: [    3.546152] md: raid10 personality registered for level 10
Oct 28 08:38:48 node-1 kernel: [    3.599660] random: lvm urandom read with 25 bits of entropy available
Oct 28 08:38:48 node-1 kernel: [    3.600436] multipathd (366): /proc/366/oom_adj is deprecated, please use /proc/366/oom_score_adj instead.
Oct 28 08:38:48 node-1 kernel: [    3.825568] bio: create slab <bio-1> at 1
Oct 28 08:38:48 node-1 kernel: [    4.628197] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 08:38:48 node-1 kernel: [    5.137925] init: plymouth-upstart-bridge main process (554) terminated with status 1
Oct 28 08:38:48 node-1 kernel: [    5.150135] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 08:38:48 node-1 kernel: [    5.260905] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 28 08:38:48 node-1 kernel: [    5.292264] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 28 08:38:48 node-1 kernel: [    5.425816] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 28 08:38:48 node-1 kernel: [    5.439294] random: nonblocking pool is initialized
Oct 28 08:38:48 node-1 kernel: [    5.461793] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 28 08:38:48 node-1 kernel: [    5.542862] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 08:38:48 node-1 kernel: [    5.759034] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 28 08:38:48 node-1 kernel: [    5.799256] XFS (dm-0): Mounting Filesystem
Oct 28 08:38:48 node-1 kernel: [    5.962331] XFS (dm-0): Ending clean mount
Oct 28 08:38:48 node-1 kernel: [    6.034002] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 08:38:48 node-1 kernel: [    6.074506] XFS (dm-1): Mounting Filesystem
Oct 28 08:38:48 node-1 kernel: [    6.192190] XFS (dm-1): Ending clean mount
Oct 28 08:38:48 node-1 kernel: [    8.291517] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 28 08:38:48 node-1 kernel: [    8.318650] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 28 08:38:48 node-1 kernel: [    8.546884] systemd-udevd[778]: starting version 204
Oct 28 08:38:48 node-1 kernel: [    8.751170] power_meter ACPI000D:00: Found ACPI power meter.
Oct 28 08:38:48 node-1 kernel: [    8.751185] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 28 08:38:48 node-1 kernel: [    8.758611] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 28 08:38:48 node-1 kernel: [    8.758617] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 08:38:48 node-1 kernel: [    8.758621] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 28 08:38:48 node-1 kernel: [    8.758623] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 08:38:48 node-1 kernel: [    8.758647] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 28 08:38:48 node-1 kernel: [    8.766105] wmi: Mapper loaded
Oct 28 08:38:48 node-1 kernel: [    8.771737] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 28 08:38:48 node-1 kernel: [    8.776465] IPMI System Interface driver.
Oct 28 08:38:48 node-1 kernel: [    8.776500] ipmi_si: probing via ACPI
Oct 28 08:38:48 node-1 kernel: [    8.776517] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 28 08:38:48 node-1 kernel: [    8.776518] ipmi_si: Adding ACPI-specified kcs state machine
Oct 28 08:38:48 node-1 kernel: [    8.776525] ipmi_si: probing via SMBIOS
Oct 28 08:38:48 node-1 kernel: [    8.776527] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 08:38:48 node-1 kernel: [    8.776528] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 28 08:38:48 node-1 kernel: [    8.776529] ipmi_si: probing via SPMI
Oct 28 08:38:48 node-1 kernel: [    8.776531] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 08:38:48 node-1 kernel: [    8.776531] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 28 08:38:48 node-1 kernel: [    8.776533] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 28 08:38:48 node-1 kernel: [    8.856115] systemd-udevd[799]: renamed network interface eth2 to enp8s0
Oct 28 08:38:48 node-1 kernel: [    8.879936] systemd-udevd[795]: renamed network interface eth0 to enp6s0
Oct 28 08:38:48 node-1 kernel: [    8.907870] systemd-udevd[820]: renamed network interface eth3 to enp9s0
Oct 28 08:38:48 node-1 kernel: [    8.927993] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 28 08:38:48 node-1 kernel: [    8.927998] ipmi_si 00:09: IPMI kcs interface initialized
Oct 28 08:38:48 node-1 kernel: [    8.931821] systemd-udevd[796]: renamed network interface eth1 to enp7s0
Oct 28 08:38:48 node-1 kernel: [    9.277146] type=1400 audit(1477643897.302:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.277296] type=1400 audit(1477643897.302:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.277426] type=1400 audit(1477643897.302:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.283981] type=1400 audit(1477643897.310:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1063 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.284022] type=1400 audit(1477643897.310:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.284163] type=1400 audit(1477643897.310:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1063 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.284192] type=1400 audit(1477643897.310:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.284365] type=1400 audit(1477643897.310:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1063 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.284381] type=1400 audit(1477643897.310:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.284398] type=1400 audit(1477643897.310:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Oct 28 08:38:48 node-1 kernel: [    9.836489] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 28 08:38:48 node-1 kernel: [    9.837181] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 28 08:38:48 node-1 kernel: [   10.020939] enic 0000:06:00.0 enp6s0: Link UP
Oct 28 08:38:48 node-1 kernel: [   10.021351] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 28 08:38:48 node-1 kernel: [   10.021360] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 28 08:38:48 node-1 kernel: [   18.657767] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 28 08:38:49 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 28 08:38:49 node-1 kernel: [   41.973008] init: failsafe main process (8412) killed by TERM signal
Oct 28 08:38:50 node-1 dbus[8454]: [system] AppArmor D-Bus mediation is enabled
Oct 28 08:38:50 node-1 kernel: [   42.208151] audit_printk_skb: 30 callbacks suppressed
Oct 28 08:38:50 node-1 kernel: [   42.208151] type=1400 audit(1477643930.126:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8530 comm="apparmor_parser"
Oct 28 08:38:50 node-1 kernel: [   42.208430] type=1400 audit(1477643930.126:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8529 comm="apparmor_parser"
Oct 28 08:38:50 node-1 kernel: [   42.208434] type=1400 audit(1477643930.126:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8529 comm="apparmor_parser"
Oct 28 08:38:50 node-1 kernel: [   42.208436] type=1400 audit(1477643930.126:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct 28 08:38:50 node-1 kernel: [   42.208666] type=1400 audit(1477643930.126:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8529 comm="apparmor_parser"
Oct 28 08:38:50 node-1 kernel: [   42.208667] type=1400 audit(1477643930.126:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct 28 08:38:50 node-1 kernel: [   42.208779] type=1400 audit(1477643930.126:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct 28 08:38:50 node-1 kernel: [   42.300028] type=1400 audit(1477643930.218:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8532 comm="apparmor_parser"
Oct 28 08:38:50 node-1 anacron[8604]: Anacron 2.3 started on 2016-10-28
Oct 28 08:38:50 node-1 cron[8569]: (CRON) INFO (pidfile fd = 3)
Oct 28 08:38:50 node-1 anacron[8604]: Will run job `cron.daily' in 5 min.
Oct 28 08:38:50 node-1 anacron[8604]: Will run job `cron.weekly' in 10 min.
Oct 28 08:38:50 node-1 anacron[8604]: Will run job `cron.monthly' in 15 min.
Oct 28 08:38:50 node-1 anacron[8604]: Jobs will be executed sequentially
Oct 28 08:38:50 node-1 cron[8609]: (CRON) STARTUP (fork ok)
Oct 28 08:38:50 node-1 cron[8609]: (CRON) INFO (Running @reboot jobs)
Oct 28 08:38:50 node-1 multipathd: path checkers start up
Oct 28 08:38:50 node-1 postfix/master[8749]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 28 08:38:54 node-1 puppet-agent[8933]: Reopening log files
Oct 28 08:38:57 node-1 puppet-agent[8933]: Could not request certificate: Connection refused - connect(2)
Oct 28 08:39:01 node-1 CRON[8964]: (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 08:39:03 node-1 puppet-user[9023]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 28 08:39:03 node-1 puppet-user[9023]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 08:39:04 node-1 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 28 08:39:04 node-1 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 28 08:39:04 node-1 puppet-user[9023]: Finished catalog run in 1.05 seconds
Oct 28 08:39:06 node-1 multipathd: uevent trigger error
Oct 28 08:39:06 node-1 puppet-user[9453]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 08:39:06 node-1 puppet-user[9453]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct 28 08:39:06 node-1 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 28 08:39:06 node-1 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 28 08:39:06 node-1 puppet-user[9453]: (/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 08:39:06 node-1 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 28 08:39:06 node-1 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 28 08:39:06 node-1 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 28 08:39:06 node-1 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 28 08:39:06 node-1 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 28 08:39:06 node-1 puppet-user[9453]: Finished catalog run in 0.07 seconds
Oct 28 08:39:07 node-1 puppet-user[9918]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 28 08:39:07 node-1 puppet-user[9918]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 28 08:39:08 node-1 puppet-user[9918]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 28 08:39:08 node-1 puppet-user[9918]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 28 08:39:08 node-1 puppet-user[9918]: Finished catalog run in 0.03 seconds
Oct 28 08:39:09 node-1 puppet-user[10380]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 28 08:39:09 node-1 puppet-user[10380]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 28 08:39:09 node-1 puppet-user[10380]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 28 08:39:09 node-1 puppet-user[10380]: Finished catalog run in 0.03 seconds
Oct 28 08:39:10 node-1 puppet-user[10854]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 28 08:39:11 node-1 puppet-user[10854]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Oct 28 08:39:11 node-1 puppet-user[10854]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 28 08:39:11 node-1 puppet-user[10854]: (/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 08:39:11 node-1 puppet-user[10854]: (/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 08:39:12 node-1 puppet-user[10854]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/tacker-0.2/]/Exec[rsync /etc/fuel/plugins/tacker-0.2/]/returns) executed successfully
Oct 28 08:39:12 node-1 puppet-user[10854]: Finished catalog run in 1.21 seconds
Oct 28 08:39:13 node-1 puppet-user[11494]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 28 08:39:13 node-1 puppet-user[11494]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Oct 28 08:39:13 node-1 puppet-user[11494]: (/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 08:39:14 node-1 puppet-user[11494]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[tacker-0.2.0]/Apt::Setting[list-tacker-0.2.0]/File[/etc/apt/sources.list.d/tacker-0.2.0.list]/ensure) created
Oct 28 08:39:14 node-1 puppet-user[11494]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 28 08:39:14 node-1 puppet-user[11494]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 28 08:39:14 node-1 puppet-user[11494]: (/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 08:39:14 node-1 puppet-user[11494]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 28 08:39:14 node-1 puppet-user[11494]: Finished catalog run in 0.36 seconds
Oct 28 08:39:15 node-1 puppet-user[11971]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 28 08:39:15 node-1 puppet-user[11971]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Oct 28 08:39:15 node-1 puppet-user[11971]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 28 08:39:15 node-1 kernel: [   67.885859] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 28 08:39:15 node-1 kernel: [   67.885911] 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 08:39:15 node-1 puppet-user[11971]: (/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 08:39:15 node-1 puppet-user[11971]: Finished catalog run in 0.05 seconds
Oct 28 08:39:17 node-1 puppet-user[12442]: (Scope(Class[main])) MODULAR: sync_time
Oct 28 08:39:17 node-1 puppet-user[12442]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 08:39:18 node-1 ntpdate[12857]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 28 08:39:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 08:39:18 node-1 nailgun-agent: D, [2016-10-28T08:39:01.677005 #8967] DEBUG -- : Sleep for 17 seconds before sending request
Oct 28 08:39:18 node-1 nailgun-agent: I, [2016-10-28T08:39:18.692714 #8967]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 28 08:39:19 node-1 nailgun-agent: D, [2016-10-28T08:39:19.134793 #8967] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 28 08:39:24 node-1 ntpdate[12857]: adjust time server 10.20.0.2 offset 0.059534 sec
Oct 28 08:39:24 node-1 puppet-user[12442]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 28 08:39:24 node-1 puppet-user[12442]: Finished catalog run in 6.16 seconds
Oct 28 08:39:30 node-1 puppet-user[13368]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 08:39:30 node-1 puppet-user[13368]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 28 08:39:30 node-1 puppet-user[13368]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 28 08:39:30 node-1 puppet-user[13368]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight", "plugins/tacker"]'
Oct 28 08:39:30 node-1 puppet-user[13368]: Finished catalog run in 0.07 seconds
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.069111 #8967] DEBUG -- : Trying to find block devices
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.069201 #8967] DEBUG -- : Found block device: sda
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.069300 #8967] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.069335 #8967] DEBUG -- : Trying to get list of physical devices
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.069580 #8967] DEBUG -- : Getting udev properties for device: sda
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.071506 #8967] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Oct 28 08:39:31 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7043", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.071542 #8967] DEBUG -- : Trying to find out if device sda is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.071604 #8967] DEBUG -- : Device sda removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.071647 #8967] DEBUG -- : Device sda seems to be appropriate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.072385 #8967] DEBUG -- : Getting udev properties for device: dm-0
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.074099 #8967] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-TSwejZ0UQBvgTrVouy6RR9mwaJUpfJMYNN4dnHKoBw54MGjFuHuJ9VYhT2uBAZfR /dev/disk/by-uuid/8bcede37-f040-44fc-b451-05c30b494f84 /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-TSwejZ0UQBvgTrVouy6RR9mwaJUpfJMYNN4dnHKoBw54MGjFuHuJ9VYhT2uBAZfR", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8bcede37-f040-44fc-b451-05c30b494f84", "ID_FS_UUID_ENC"=>"8bcede37-f040-44fc-b451-05c30b494f84", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73689", "nomdmonddf"=>"1", "nomd
Oct 28 08:39:31 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.074134 #8967] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.074181 #8967] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.074204 #8967] DEBUG -- : Device dm-0 seems to be appropriate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.074247 #8967] DEBUG -- : Getting udev properties for device: dm-1
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.075897 #8967] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-rHtM3zPZhW3j29ngUkEeKZnkcRS9ckNgU4E3pJcrbEs1rRoX82OskWHHAMmsqP8C /dev/disk/by-uuid/7ff86aeb-68ad-4721-ab7c-30761a3a446f /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-rHtM3zPZhW3j29ngUkEeKZnkcRS9ckNgU4E3pJcrbEs1rRoX82OskWHHAMmsqP8C", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"7ff86aeb-68ad-4721-ab7c-30761a3a446f", "ID_FS_UUID_ENC"=>"7ff86aeb-68ad-4721-ab7c-30761a3a446f", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98
Oct 28 08:39:31 node-1 nailgun-agent: 96", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.075927 #8967] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.075993 #8967] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.076044 #8967] DEBUG -- : Device dm-1 seems to be appropriate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.076071 #8967] DEBUG -- : Getting udev properties for device: dm-2
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.077756 #8967] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-d6woLFg2Y3cG2UlcgIAxHsq7vgkVtRWGHhqdzU1u1sm6fvqJulsxBSaVq9HFPF83 /dev/disk/by-uuid/9015c8af-8397-4008-a720-0793d03579ef /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-d6woLFg2Y3cG2UlcgIAxHsq7vgkVtRWGHhqdzU1u1sm6fvqJulsxBSaVq9HFPF83", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9015c8af-8397-4008-a720-0793d03579ef", "ID_FS_UUID_ENC"=>"9015c8af-8397-4008-a720-0793d03579ef", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21369", "nomdmond
Oct 28 08:39:31 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.077782 #8967] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.077824 #8967] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.077850 #8967] DEBUG -- : Device dm-2 seems to be appropriate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.077863 #8967] DEBUG -- : Getting udev properties for device: dm-3
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.079398 #8967] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-G1bkZ7IGs8Y45PL2Nh1rn40ZlR9YizF8fZSilkO8S6MO0vXyg35zMdfSsH0FSl4c /dev/disk/by-uuid/8e63ed13-7d6f-4735-a230-cee87847bd0f /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-G1bkZ7IGs8Y45PL2Nh1rn40ZlR9YizF8fZSilkO8S6MO0vXyg35zMdfSsH0FSl4c", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8e63ed13-7d6f-4735-a230-cee87847bd0f", "ID_FS_UUID_ENC"=>"8e63ed13-7d6f-4735-a230-cee87847bd0f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32525", "nomdmonddf"=>"1", 
Oct 28 08:39:31 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.079422 #8967] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.079461 #8967] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.079474 #8967] DEBUG -- : Device dm-3 seems to be appropriate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.079502 #8967] DEBUG -- : Getting udev properties for device: dm-4
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.081027 #8967] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-R9bVyFSmAqvncOJEg7K4BjZbha6S5iivftAPaxpQFrZbHf90M3nTRAHn10BYlFfA /dev/disk/by-uuid/9957eeb5-4b7b-4799-b0f0-dd8b16903c91 /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-R9bVyFSmAqvncOJEg7K4BjZbha6S5iivftAPaxpQFrZbHf90M3nTRAHn10BYlFfA", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9957eeb5-4b7b-4799-b0f0-dd8b16903c91", "ID_FS_UUID_ENC"=>"9957eeb5-4b7b-4799-b0f0-dd8b16903c91", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28055", "nomdmonddf"=>"1", "nomd
Oct 28 08:39:31 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.081050 #8967] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.081106 #8967] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.081126 #8967] DEBUG -- : Device dm-4 seems to be appropriate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.081141 #8967] DEBUG -- : Getting udev properties for device: dm-5
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.082667 #8967] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-R9bVyFSmAqvncOJEg7K4BjZbha6S5iivx6qSlBEt0HV2KlItmNCJ6fItjDFfFKvW /dev/disk/by-uuid/d04a1759-b3df-4d8e-861d-c7f56e970674 /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-R9bVyFSmAqvncOJEg7K4BjZbha6S5iivx6qSlBEt0HV2KlItmNCJ6fItjDFfFKvW", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"d04a1759-b3df-4d8e-861d-c7f56e970674", "ID_FS_UUID_ENC"=>"d04a1759-b3df-4d8e-861d-c7f56e970674", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28467", "nomdmonddf"=>"1", "nomdmonisw"
Oct 28 08:39:31 node-1 nailgun-agent: =>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.082730 #8967] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.082759 #8967] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.082771 #8967] DEBUG -- : Device dm-5 seems to be appropriate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.082783 #8967] DEBUG -- : Getting udev properties for device: ram0
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.084207 #8967] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31572", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.084237 #8967] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.084268 #8967] DEBUG -- : Device ram0 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.084297 #8967] DEBUG -- : Getting udev properties for device: ram1
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.085673 #8967] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31587", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.085704 #8967] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.085751 #8967] DEBUG -- : Device ram1 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.085770 #8967] DEBUG -- : Getting udev properties for device: ram2
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.087162 #8967] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31851", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.087187 #8967] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.087260 #8967] DEBUG -- : Device ram2 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.087280 #8967] DEBUG -- : Getting udev properties for device: ram3
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.088708 #8967] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31868", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.088744 #8967] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.088780 #8967] DEBUG -- : Device ram3 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.088799 #8967] DEBUG -- : Getting udev properties for device: ram4
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.090271 #8967] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31883", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.090291 #8967] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.090336 #8967] DEBUG -- : Device ram4 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.090356 #8967] DEBUG -- : Getting udev properties for device: ram5
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.091796 #8967] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32044", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.091816 #8967] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.091875 #8967] DEBUG -- : Device ram5 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.091894 #8967] DEBUG -- : Getting udev properties for device: ram6
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.093411 #8967] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32065", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.093435 #8967] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.093477 #8967] DEBUG -- : Device ram6 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.093497 #8967] DEBUG -- : Getting udev properties for device: ram7
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.095097 #8967] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32084", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.095132 #8967] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.095166 #8967] DEBUG -- : Device ram7 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.095185 #8967] DEBUG -- : Getting udev properties for device: ram8
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.096652 #8967] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32102", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.096679 #8967] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.096716 #8967] DEBUG -- : Device ram8 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.096760 #8967] DEBUG -- : Getting udev properties for device: ram9
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.098290 #8967] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32119", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.098326 #8967] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.098362 #8967] DEBUG -- : Device ram9 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.098382 #8967] DEBUG -- : Getting udev properties for device: loop0
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.099789 #8967] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31442", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.099810 #8967] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.099844 #8967] DEBUG -- : Device loop0 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.099861 #8967] DEBUG -- : Getting udev properties for device: loop1
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.106113 #8967] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31461", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.106140 #8967] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.106183 #8967] DEBUG -- : Device loop1 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.106202 #8967] DEBUG -- : Getting udev properties for device: loop2
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.107794 #8967] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31479", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.107830 #8967] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.107864 #8967] DEBUG -- : Device loop2 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.107883 #8967] DEBUG -- : Getting udev properties for device: loop3
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.109280 #8967] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31494", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.109337 #8967] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.109374 #8967] DEBUG -- : Device loop3 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.109392 #8967] DEBUG -- : Getting udev properties for device: loop4
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.110752 #8967] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31507", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.110772 #8967] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.110839 #8967] DEBUG -- : Device loop4 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.110857 #8967] DEBUG -- : Getting udev properties for device: loop5
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.112206 #8967] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31522", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.112226 #8967] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.112253 #8967] DEBUG -- : Device loop5 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.112302 #8967] DEBUG -- : Getting udev properties for device: loop6
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.113672 #8967] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31540", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.113692 #8967] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.113721 #8967] DEBUG -- : Device loop6 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.113740 #8967] DEBUG -- : Getting udev properties for device: loop7
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.115100 #8967] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31556", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.115120 #8967] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.115147 #8967] DEBUG -- : Device loop7 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.115165 #8967] DEBUG -- : Getting udev properties for device: ram10
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.116510 #8967] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31606", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.116530 #8967] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.116563 #8967] DEBUG -- : Device ram10 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.116580 #8967] DEBUG -- : Getting udev properties for device: ram11
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.117969 #8967] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31625", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.117988 #8967] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.118026 #8967] DEBUG -- : Device ram11 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.118043 #8967] DEBUG -- : Getting udev properties for device: ram12
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.119455 #8967] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31643", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.119475 #8967] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.119509 #8967] DEBUG -- : Device ram12 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.119526 #8967] DEBUG -- : Getting udev properties for device: ram13
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.120895 #8967] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31658", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.120917 #8967] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.120987 #8967] DEBUG -- : Device ram13 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.121004 #8967] DEBUG -- : Getting udev properties for device: ram14
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.122347 #8967] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31811", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.122367 #8967] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.122394 #8967] DEBUG -- : Device ram14 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.122448 #8967] DEBUG -- : Getting udev properties for device: ram15
Oct 28 08:39:31 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124264 #8967] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31830", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124311 #8967] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124351 #8967] DEBUG -- : Device ram15 removable parameter: "0"
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124394 #8967] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124459 #8967] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124500 #8967] DEBUG -- : Found block device: dm-0
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124515 #8967] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124529 #8967] DEBUG -- : Found block device: dm-1
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124539 #8967] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124548 #8967] DEBUG -- : Found block device: dm-2
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124560 #8967] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124569 #8967] DEBUG -- : Found block device: dm-3
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124579 #8967] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124587 #8967] DEBUG -- : Found block device: dm-4
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124636 #8967] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124645 #8967] DEBUG -- : Found block device: dm-5
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124655 #8967] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124663 #8967] DEBUG -- : Found block device: ram0
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124674 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124682 #8967] DEBUG -- : Found block device: ram1
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124693 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124701 #8967] DEBUG -- : Found block device: ram2
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124711 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124719 #8967] DEBUG -- : Found block device: ram3
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124764 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124772 #8967] DEBUG -- : Found block device: ram4
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124787 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124796 #8967] DEBUG -- : Found block device: ram5
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124805 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124813 #8967] DEBUG -- : Found block device: ram6
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124822 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124831 #8967] DEBUG -- : Found block device: ram7
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124840 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124849 #8967] DEBUG -- : Found block device: ram8
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124891 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124899 #8967] DEBUG -- : Found block device: ram9
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124909 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124918 #8967] DEBUG -- : Found block device: loop0
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124928 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124936 #8967] DEBUG -- : Found block device: loop1
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124948 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124956 #8967] DEBUG -- : Found block device: loop2
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124966 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.124974 #8967] DEBUG -- : Found block device: loop3
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125029 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125039 #8967] DEBUG -- : Found block device: loop4
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125048 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125056 #8967] DEBUG -- : Found block device: loop5
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125066 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125074 #8967] DEBUG -- : Found block device: loop6
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125084 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125092 #8967] DEBUG -- : Found block device: loop7
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125103 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125111 #8967] DEBUG -- : Found block device: ram10
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125174 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125184 #8967] DEBUG -- : Found block device: ram11
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125195 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125204 #8967] DEBUG -- : Found block device: ram12
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125214 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125222 #8967] DEBUG -- : Found block device: ram13
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125233 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125241 #8967] DEBUG -- : Found block device: ram14
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125251 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125259 #8967] DEBUG -- : Found block device: ram15
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125307 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.125340 #8967] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.201611 #8967] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 28 08:39:31 node-1 nailgun-agent: D, [2016-10-28T08:39:31.201675 #8967] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 28 08:39:32 node-1 puppet-user[13974]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 28 08:39:32 node-1 puppet-user[13974]: Compiled catalog for node-1.domain.tld in environment production in 0.51 seconds
Oct 28 08:39:32 node-1 puppet-user[13974]: (/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 08:39:32 node-1 puppet-user[13974]: (/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 08:39:32 node-1 puppet-user[13974]: (/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 08:39:32 node-1 puppet-user[13974]: (/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 08:39:32 node-1 puppet-user[13974]: (/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 08:39:32 node-1 puppet-user[13974]: (/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 08:39:32 node-1 puppet-user[13974]: (/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 08:39:33 node-1 puppet-user[13974]: (/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 08:39:33 node-1 puppet-user[13974]: (/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 08:39:33 node-1 puppet-user[13974]: (/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 08:39:33 node-1 puppet-user[13974]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 28 08:39:33 node-1 puppet-user[13974]: Finished catalog run in 0.89 seconds
Oct 28 08:39:35 node-1 kernel: [   87.058566] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 08:39:35 node-1 puppet-user[14527]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 28 08:39:35 node-1 puppet-agent[8933]: Could not run: SIGTERM
Oct 28 08:39:35 node-1 puppet-user[14527]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct 28 08:39:35 node-1 kernel: [   87.357944] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 28 08:39:35 node-1 ec2: 
Oct 28 08:39:35 node-1 ec2: #############################################################
Oct 28 08:39:35 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 28 08:39:35 node-1 ec2: 1024 45:47:8e:1b:b9:07:9c:9c:f9:dd:d0:29:00:e1:94:99  root@node-1.domain.tld (DSA)
Oct 28 08:39:35 node-1 ec2: 256 66:ab:3e:dc:1a:65:c6:f2:4c:38:8f:01:02:8b:f8:87  root@node-1.domain.tld (ECDSA)
Oct 28 08:39:35 node-1 ec2: 256 70:4f:80:c2:56:6e:27:df:70:3c:f3:e2:15:f5:d3:c1  root@node-1.domain.tld (ED25519)
Oct 28 08:39:35 node-1 ec2: 2048 df:20:04:b8:12:d3:00:90:81:8c:02:c4:dc:31:9f:48  root@node-1.domain.tld (RSA)
Oct 28 08:39:35 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 28 08:39:35 node-1 ec2: #############################################################
Oct 28 08:39:38 node-1 puppet-user[14527]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 28 08:39:43 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581256 #8967] DEBUG -- : Trying to find block devices
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581377 #8967] DEBUG -- : Found block device: sda
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581406 #8967] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581425 #8967] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581447 #8967] DEBUG -- : Found block device: dm-0
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581476 #8967] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581488 #8967] DEBUG -- : Found block device: dm-1
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581498 #8967] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581507 #8967] DEBUG -- : Found block device: dm-2
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581516 #8967] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581541 #8967] DEBUG -- : Found block device: dm-3
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581550 #8967] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581558 #8967] DEBUG -- : Found block device: dm-4
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581567 #8967] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581600 #8967] DEBUG -- : Found block device: dm-5
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581609 #8967] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581616 #8967] DEBUG -- : Found block device: ram0
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581637 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581646 #8967] DEBUG -- : Found block device: ram1
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581654 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581662 #8967] DEBUG -- : Found block device: ram2
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581686 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581694 #8967] DEBUG -- : Found block device: ram3
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581703 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581710 #8967] DEBUG -- : Found block device: ram4
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581733 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581742 #8967] DEBUG -- : Found block device: ram5
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581751 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581758 #8967] DEBUG -- : Found block device: ram6
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581778 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581786 #8967] DEBUG -- : Found block device: ram7
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581795 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581804 #8967] DEBUG -- : Found block device: ram8
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581813 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581848 #8967] DEBUG -- : Found block device: ram9
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581857 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581865 #8967] DEBUG -- : Found block device: loop0
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581874 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581882 #8967] DEBUG -- : Found block device: loop1
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581891 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581899 #8967] DEBUG -- : Found block device: loop2
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581907 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581914 #8967] DEBUG -- : Found block device: loop3
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581923 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581956 #8967] DEBUG -- : Found block device: loop4
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581965 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581973 #8967] DEBUG -- : Found block device: loop5
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581981 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581989 #8967] DEBUG -- : Found block device: loop6
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.581999 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582006 #8967] DEBUG -- : Found block device: loop7
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582015 #8967] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582023 #8967] DEBUG -- : Found block device: ram10
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582032 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582060 #8967] DEBUG -- : Found block device: ram11
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582068 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582076 #8967] DEBUG -- : Found block device: ram12
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582086 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582093 #8967] DEBUG -- : Found block device: ram13
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582102 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582110 #8967] DEBUG -- : Found block device: ram14
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582118 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582147 #8967] DEBUG -- : Found block device: ram15
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582156 #8967] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.582187 #8967] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct 28 08:39:43 node-1 nailgun-agent: D, [2016-10-28T08:39:43.742583 #8967] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 28 08:39:43 node-1 nailgun-agent: I, [2016-10-28T08:39:43.756394 #8967]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 28 08:40:01 node-1 CRON[17393]: (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 08:40:05 node-1 puppet-user[14527]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 28 08:40:05 node-1 puppet-user[14527]: Finished catalog run in 30.01 seconds
Oct 28 08:40:06 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 08:40:06 node-1 nailgun-agent: I, [2016-10-28T08:40:06.938003 #17396]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 28 08:40:07 node-1 puppet-user[17613]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 28 08:40:07 node-1 puppet-user[17613]: Compiled catalog for node-1.domain.tld in environment production in 0.61 seconds
Oct 28 08:40:08 node-1 puppet-user[17613]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 28 08:40:08 node-1 puppet-user[17613]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 28 08:40:08 node-1 puppet-user[17613]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 28 08:40:08 node-1 puppet-user[17613]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 28 08:40:08 node-1 puppet-user[17613]: Finished catalog run in 0.07 seconds
Oct 28 08:40:09 node-1 puppet-user[18204]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 28 08:40:10 node-1 puppet-user[18204]: Compiled catalog for node-1.domain.tld in environment production in 0.80 seconds
Oct 28 08:40:11 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 28 08:40:11 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 28 08:40:11 node-1 crontab[18648]: (root) LIST (root)
Oct 28 08:40:11 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 28 08:40:11 node-1 crontab[18649]: (root) REPLACE (root)
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 28 08:40:12 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 28 08:40:13 node-1 puppet-user[18204]: (/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 08:40:13 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8385" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 08:40:13 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 28 08:40:15 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:15 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:15 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:15 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:15 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:30 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:30 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:30 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:30 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:30 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 08:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 08:41:27 node-1 ntpdate[29613]: no servers can be used, exiting
<27>Oct 28 08:41:27 node-1 ntpdate[29732]: no servers can be used, exiting
<27>Oct 28 08:41:27 node-1 ntpdate[29927]: no servers can be used, exiting
<27>Oct 28 08:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:02 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:02 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:02 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:02 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:02 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:02 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:16 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:16 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:16 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:16 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:16 node-1 multipathd: uevent trigger error
<27>Oct 28 08:42:16 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:21 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 08:43:21 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 08:43:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 08:43:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 08:43:32 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 08:43:38 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 08:43:38 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 08:43:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:47 node-1 ntpdate[15686]: the NTP socket is in use, exiting
<27>Oct 28 08:43:58 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:58 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:58 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:58 node-1 multipathd: uevent trigger error
<27>Oct 28 08:43:58 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:03 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:06 node-1 haproxy[19547]: 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 08:44:06 node-1 haproxy[19547]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:07 node-1 haproxy[19551]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:07 node-1 haproxy[19551]: proxy mysqld has no server available!
<27>Oct 28 08:44:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:12 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:13 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:15 node-1 haproxy[22275]: 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 08:44:15 node-1 haproxy[22275]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:15 node-1 haproxy[22275]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:15 node-1 haproxy[22275]: proxy mysqld has no server available!
<129>Oct 28 08:44:16 node-1 haproxy[22284]: 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 08:44:16 node-1 haproxy[22284]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:16 node-1 haproxy[22284]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:16 node-1 haproxy[22284]: proxy object-storage has no server available!
<27>Oct 28 08:44:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:18 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:18 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:20 node-1 haproxy[23639]: 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 08:44:20 node-1 haproxy[23639]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:20 node-1 haproxy[23639]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:20 node-1 haproxy[23639]: proxy neutron has no server available!
<129>Oct 28 08:44:21 node-1 haproxy[23645]: 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 08:44:21 node-1 haproxy[23645]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:21 node-1 haproxy[23645]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:21 node-1 haproxy[23645]: proxy mysqld has no server available!
<129>Oct 28 08:44:21 node-1 haproxy[23645]: 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 08:44:21 node-1 haproxy[23645]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:22 node-1 haproxy[23645]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:22 node-1 haproxy[23645]: proxy object-storage has no server available!
<27>Oct 28 08:44:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:23 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:26 node-1 haproxy[25203]: 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 08:44:26 node-1 haproxy[25203]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:26 node-1 haproxy[25203]: Server keystone-1/node-4 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 08:44:26 node-1 haproxy[25203]: proxy keystone-1 has no server available!
<129>Oct 28 08:44:26 node-1 haproxy[25203]: 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 08:44:26 node-1 haproxy[25203]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:26 node-1 haproxy[25203]: Server keystone-2/node-4 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 08:44:26 node-1 haproxy[25203]: proxy keystone-2 has no server available!
<129>Oct 28 08:44:26 node-1 haproxy[25203]: 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 08:44:27 node-1 haproxy[25207]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:27 node-1 haproxy[25207]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:27 node-1 haproxy[25207]: proxy neutron has no server available!
<129>Oct 28 08:44:27 node-1 haproxy[25207]: 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 08:44:27 node-1 haproxy[25207]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:27 node-1 haproxy[25207]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:27 node-1 haproxy[25207]: proxy mysqld has no server available!
<129>Oct 28 08:44:27 node-1 haproxy[25207]: 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 08:44:27 node-1 haproxy[25207]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:27 node-1 haproxy[25207]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:27 node-1 haproxy[25207]: proxy object-storage has no server available!
<27>Oct 28 08:44:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:29 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:31 node-1 haproxy[26541]: 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 08:44:31 node-1 haproxy[26541]: Server keystone-1/node-2 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 08:44:31 node-1 haproxy[26541]: Server keystone-1/node-4 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 08:44:31 node-1 haproxy[26541]: proxy keystone-1 has no server available!
<129>Oct 28 08:44:31 node-1 haproxy[26541]: 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 08:44:31 node-1 haproxy[26541]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:32 node-1 haproxy[26546]: Server keystone-2/node-4 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 08:44:32 node-1 haproxy[26546]: proxy keystone-2 has no server available!
<129>Oct 28 08:44:32 node-1 haproxy[26546]: 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 08:44:32 node-1 haproxy[26546]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:32 node-1 haproxy[26546]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:32 node-1 haproxy[26546]: proxy neutron has no server available!
<129>Oct 28 08:44:32 node-1 haproxy[26546]: 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 08:44:32 node-1 haproxy[26546]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:32 node-1 haproxy[26546]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:32 node-1 haproxy[26546]: proxy mysqld has no server available!
<129>Oct 28 08:44:32 node-1 haproxy[26546]: 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 08:44:32 node-1 haproxy[26546]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:32 node-1 haproxy[26546]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:32 node-1 haproxy[26546]: proxy object-storage has no server available!
<129>Oct 28 08:44:33 node-1 haproxy[26546]: 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 08:44:33 node-1 haproxy[26546]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:33 node-1 haproxy[26546]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:33 node-1 haproxy[26546]: proxy aodh has no server available!
<27>Oct 28 08:44:34 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:34 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:34 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:34 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:34 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:37 node-1 haproxy[27925]: 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 08:44:37 node-1 haproxy[27925]: Server keystone-1/node-2 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 08:44:37 node-1 haproxy[27925]: Server keystone-1/node-4 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 08:44:37 node-1 haproxy[27925]: proxy keystone-1 has no server available!
<129>Oct 28 08:44:37 node-1 haproxy[27925]: 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 08:44:37 node-1 haproxy[27925]: Server keystone-2/node-2 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 08:44:37 node-1 haproxy[27925]: Server keystone-2/node-4 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 08:44:37 node-1 haproxy[27925]: proxy keystone-2 has no server available!
<129>Oct 28 08:44:37 node-1 haproxy[27925]: 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 08:44:37 node-1 haproxy[27925]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:37 node-1 haproxy[27925]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:37 node-1 haproxy[27925]: proxy neutron has no server available!
<129>Oct 28 08:44:37 node-1 haproxy[27925]: 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 08:44:38 node-1 haproxy[27931]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:38 node-1 haproxy[27931]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:38 node-1 haproxy[27931]: proxy mysqld has no server available!
<129>Oct 28 08:44:38 node-1 haproxy[27931]: 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 08:44:38 node-1 haproxy[27931]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:38 node-1 haproxy[27931]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:38 node-1 haproxy[27931]: proxy object-storage has no server available!
<129>Oct 28 08:44:38 node-1 haproxy[27931]: 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 08:44:38 node-1 haproxy[27931]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:38 node-1 haproxy[27931]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:38 node-1 haproxy[27931]: proxy aodh has no server available!
<129>Oct 28 08:44:38 node-1 haproxy[27931]: 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 08:44:38 node-1 haproxy[27931]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:38 node-1 haproxy[27931]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:38 node-1 haproxy[27931]: proxy ceilometer has no server available!
<27>Oct 28 08:44:40 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:40 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:40 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:40 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:40 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:42 node-1 haproxy[29291]: 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 08:44:42 node-1 haproxy[29291]: Server keystone-1/node-2 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 08:44:42 node-1 haproxy[29291]: Server keystone-1/node-4 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 08:44:42 node-1 haproxy[29291]: proxy keystone-1 has no server available!
<129>Oct 28 08:44:42 node-1 haproxy[29291]: 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 08:44:42 node-1 haproxy[29291]: Server keystone-2/node-2 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 08:44:43 node-1 haproxy[29295]: Server keystone-2/node-4 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 08:44:43 node-1 haproxy[29295]: proxy keystone-2 has no server available!
<129>Oct 28 08:44:43 node-1 haproxy[29295]: 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 08:44:43 node-1 haproxy[29295]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:43 node-1 haproxy[29295]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:43 node-1 haproxy[29295]: proxy neutron has no server available!
<129>Oct 28 08:44:43 node-1 haproxy[29295]: 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 08:44:43 node-1 haproxy[29295]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:43 node-1 haproxy[29295]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:43 node-1 haproxy[29295]: proxy mysqld has no server available!
<129>Oct 28 08:44:43 node-1 haproxy[29295]: 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 08:44:43 node-1 haproxy[29295]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:43 node-1 haproxy[29295]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:43 node-1 haproxy[29295]: proxy object-storage has no server available!
<129>Oct 28 08:44:43 node-1 haproxy[29295]: 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 08:44:44 node-1 haproxy[29295]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:44 node-1 haproxy[29295]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:44 node-1 haproxy[29295]: proxy aodh has no server available!
<129>Oct 28 08:44:44 node-1 haproxy[29295]: 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 08:44:44 node-1 haproxy[29295]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:44 node-1 haproxy[29295]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:44 node-1 haproxy[29295]: proxy ceilometer has no server available!
<27>Oct 28 08:44:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:45 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:48 node-1 haproxy[30619]: 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 08:44:48 node-1 haproxy[30619]: 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 08:44:48 node-1 haproxy[30619]: Server keystone-1/node-2 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 08:44:48 node-1 haproxy[30619]: Server keystone-1/node-4 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 08:44:48 node-1 haproxy[30619]: proxy keystone-1 has no server available!
<129>Oct 28 08:44:48 node-1 haproxy[30619]: 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 08:44:48 node-1 haproxy[30619]: Server keystone-2/node-2 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 08:44:48 node-1 haproxy[30619]: Server keystone-2/node-4 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 08:44:48 node-1 haproxy[30619]: proxy keystone-2 has no server available!
<129>Oct 28 08:44:48 node-1 haproxy[30619]: 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 08:44:48 node-1 haproxy[30619]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:49 node-1 haproxy[30623]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:49 node-1 haproxy[30623]: proxy neutron has no server available!
<129>Oct 28 08:44:49 node-1 haproxy[30623]: 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 08:44:49 node-1 haproxy[30623]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:49 node-1 haproxy[30623]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:49 node-1 haproxy[30623]: proxy mysqld has no server available!
<129>Oct 28 08:44:49 node-1 haproxy[30623]: 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 08:44:49 node-1 haproxy[30623]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:49 node-1 haproxy[30623]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:49 node-1 haproxy[30623]: proxy object-storage has no server available!
<129>Oct 28 08:44:49 node-1 haproxy[30623]: 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 08:44:49 node-1 haproxy[30623]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:49 node-1 haproxy[30623]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:49 node-1 haproxy[30623]: proxy aodh has no server available!
<129>Oct 28 08:44:49 node-1 haproxy[30623]: 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 08:44:49 node-1 haproxy[30623]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:49 node-1 haproxy[30623]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:49 node-1 haproxy[30623]: proxy ceilometer has no server available!
<27>Oct 28 08:44:51 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:51 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:51 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:51 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:51 node-1 multipathd: uevent trigger error
<129>Oct 28 08:44:54 node-1 haproxy[32052]: 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 08:44:54 node-1 haproxy[32052]: 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 08:44:54 node-1 haproxy[32052]: Server keystone-1/node-2 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 08:44:54 node-1 haproxy[32052]: Server keystone-1/node-4 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 08:44:54 node-1 haproxy[32052]: proxy keystone-1 has no server available!
<129>Oct 28 08:44:54 node-1 haproxy[32052]: 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 08:44:54 node-1 haproxy[32052]: Server keystone-2/node-2 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 08:44:54 node-1 haproxy[32052]: Server keystone-2/node-4 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 08:44:54 node-1 haproxy[32052]: proxy keystone-2 has no server available!
<129>Oct 28 08:44:54 node-1 haproxy[32052]: 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 08:44:54 node-1 haproxy[32052]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:54 node-1 haproxy[32052]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:54 node-1 haproxy[32052]: proxy glance-api has no server available!
<129>Oct 28 08:44:54 node-1 haproxy[32052]: 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 08:44:54 node-1 haproxy[32052]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:54 node-1 haproxy[32052]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:54 node-1 haproxy[32052]: proxy glance-glare has no server available!
<129>Oct 28 08:44:54 node-1 haproxy[32052]: 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 08:44:55 node-1 haproxy[32063]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:55 node-1 haproxy[32063]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:55 node-1 haproxy[32063]: proxy neutron has no server available!
<129>Oct 28 08:44:55 node-1 haproxy[32063]: 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 08:44:55 node-1 haproxy[32063]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:55 node-1 haproxy[32063]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:55 node-1 haproxy[32063]: proxy glance-registry has no server available!
<129>Oct 28 08:44:55 node-1 haproxy[32063]: 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 08:44:55 node-1 haproxy[32063]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:55 node-1 haproxy[32063]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:55 node-1 haproxy[32063]: proxy mysqld has no server available!
<129>Oct 28 08:44:55 node-1 haproxy[32063]: 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 08:44:55 node-1 haproxy[32063]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:55 node-1 haproxy[32063]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:55 node-1 haproxy[32063]: proxy object-storage has no server available!
<129>Oct 28 08:44:55 node-1 haproxy[32063]: 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 08:44:55 node-1 haproxy[32063]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:55 node-1 haproxy[32063]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:55 node-1 haproxy[32063]: proxy aodh has no server available!
<129>Oct 28 08:44:55 node-1 haproxy[32063]: 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 08:44:55 node-1 haproxy[32063]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:44:55 node-1 haproxy[32063]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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 08:44:55 node-1 haproxy[32063]: proxy ceilometer has no server available!
<27>Oct 28 08:44:57 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:57 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:57 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:57 node-1 multipathd: uevent trigger error
<27>Oct 28 08:44:57 node-1 multipathd: uevent trigger error
<129>Oct 28 08:45:00 node-1 haproxy[1036]: 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 08:45:00 node-1 haproxy[1036]: 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 08:45:00 node-1 haproxy[1036]: Server keystone-1/node-2 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 08:45:00 node-1 haproxy[1036]: Server keystone-1/node-4 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 08:45:00 node-1 haproxy[1036]: proxy keystone-1 has no server available!
<129>Oct 28 08:45:00 node-1 haproxy[1036]: 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 08:45:00 node-1 haproxy[1036]: Server keystone-2/node-2 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 08:45:00 node-1 haproxy[1036]: Server keystone-2/node-4 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 08:45:00 node-1 haproxy[1036]: proxy keystone-2 has no server available!
<129>Oct 28 08:45:00 node-1 haproxy[1036]: 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 08:45:00 node-1 haproxy[1036]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:00 node-1 haproxy[1036]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:00 node-1 haproxy[1036]: proxy nova-api has no server available!
<129>Oct 28 08:45:00 node-1 haproxy[1036]: 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 08:45:00 node-1 haproxy[1036]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:00 node-1 haproxy[1036]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:00 node-1 haproxy[1036]: proxy nova-metadata-api has no server available!
<129>Oct 28 08:45:00 node-1 haproxy[1036]: 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 08:45:00 node-1 haproxy[1036]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:00 node-1 haproxy[1036]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:00 node-1 haproxy[1036]: proxy glance-api has no server available!
<129>Oct 28 08:45:00 node-1 haproxy[1036]: 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 08:45:00 node-1 haproxy[1036]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:00 node-1 haproxy[1036]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:00 node-1 haproxy[1036]: proxy glance-glare has no server available!
<129>Oct 28 08:45:00 node-1 haproxy[1036]: 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 08:45:01 node-1 haproxy[1043]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:01 node-1 haproxy[1043]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:01 node-1 haproxy[1043]: proxy neutron has no server available!
<129>Oct 28 08:45:01 node-1 haproxy[1043]: 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 08:45:01 node-1 haproxy[1043]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:01 node-1 haproxy[1043]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:01 node-1 haproxy[1043]: proxy glance-registry has no server available!
<129>Oct 28 08:45:01 node-1 haproxy[1043]: 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 08:45:01 node-1 haproxy[1043]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:01 node-1 haproxy[1043]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:01 node-1 haproxy[1043]: proxy mysqld has no server available!
<129>Oct 28 08:45:01 node-1 haproxy[1043]: 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 08:45:01 node-1 haproxy[1043]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:01 node-1 haproxy[1043]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:01 node-1 haproxy[1043]: proxy object-storage has no server available!
<129>Oct 28 08:45:01 node-1 haproxy[1043]: 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 08:45:01 node-1 haproxy[1043]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:01 node-1 haproxy[1043]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:01 node-1 haproxy[1043]: proxy aodh has no server available!
<129>Oct 28 08:45:01 node-1 haproxy[1043]: 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 08:45:01 node-1 haproxy[1043]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:01 node-1 haproxy[1043]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:01 node-1 haproxy[1043]: proxy ceilometer has no server available!
<129>Oct 28 08:45:01 node-1 haproxy[1043]: 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 08:45:01 node-1 haproxy[1043]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:01 node-1 haproxy[1043]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:01 node-1 haproxy[1043]: proxy nova-novncproxy has no server available!
<27>Oct 28 08:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:03 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:03 node-1 multipathd: uevent trigger error
<129>Oct 28 08:45:05 node-1 haproxy[2527]: 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 08:45:05 node-1 haproxy[2527]: 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 08:45:05 node-1 haproxy[2527]: Server keystone-1/node-2 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 08:45:05 node-1 haproxy[2527]: Server keystone-1/node-4 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 08:45:05 node-1 haproxy[2527]: proxy keystone-1 has no server available!
<129>Oct 28 08:45:05 node-1 haproxy[2527]: 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 08:45:05 node-1 haproxy[2527]: Server keystone-2/node-2 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 08:45:05 node-1 haproxy[2527]: Server keystone-2/node-4 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 08:45:05 node-1 haproxy[2527]: proxy keystone-2 has no server available!
<129>Oct 28 08:45:05 node-1 haproxy[2527]: 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 08:45:06 node-1 haproxy[2533]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy nova-api has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:06 node-1 haproxy[2533]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy nova-metadata-api has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:06 node-1 haproxy[2533]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy cinder-api has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:06 node-1 haproxy[2533]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy glance-api has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:06 node-1 haproxy[2533]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy glance-glare has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:06 node-1 haproxy[2533]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy neutron has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:06 node-1 haproxy[2533]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy glance-registry has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:06 node-1 haproxy[2533]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:06 node-1 haproxy[2533]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:06 node-1 haproxy[2533]: proxy mysqld has no server available!
<129>Oct 28 08:45:06 node-1 haproxy[2533]: 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 08:45:07 node-1 haproxy[2533]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:07 node-1 haproxy[2533]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:07 node-1 haproxy[2533]: proxy object-storage has no server available!
<129>Oct 28 08:45:07 node-1 haproxy[2533]: 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 08:45:07 node-1 haproxy[2533]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:07 node-1 haproxy[2533]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:07 node-1 haproxy[2533]: proxy aodh has no server available!
<129>Oct 28 08:45:07 node-1 haproxy[2533]: 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 08:45:07 node-1 haproxy[2533]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:07 node-1 haproxy[2533]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:07 node-1 haproxy[2533]: proxy ceilometer has no server available!
<129>Oct 28 08:45:07 node-1 haproxy[2533]: 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 08:45:07 node-1 haproxy[2533]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:07 node-1 haproxy[2533]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:07 node-1 haproxy[2533]: proxy nova-novncproxy has no server available!
<27>Oct 28 08:45:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:08 node-1 multipathd: uevent trigger error
<129>Oct 28 08:45:11 node-1 haproxy[3927]: 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 08:45:11 node-1 haproxy[3927]: 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 08:45:11 node-1 haproxy[3927]: Server keystone-1/node-2 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 08:45:11 node-1 haproxy[3927]: Server keystone-1/node-4 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 08:45:11 node-1 haproxy[3927]: proxy keystone-1 has no server available!
<129>Oct 28 08:45:11 node-1 haproxy[3927]: 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 08:45:11 node-1 haproxy[3927]: Server keystone-2/node-2 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 08:45:11 node-1 haproxy[3927]: Server keystone-2/node-4 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 08:45:11 node-1 haproxy[3927]: proxy keystone-2 has no server available!
<129>Oct 28 08:45:11 node-1 haproxy[3927]: 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 08:45:11 node-1 haproxy[3927]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:11 node-1 haproxy[3927]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:11 node-1 haproxy[3927]: proxy nova-api has no server available!
<129>Oct 28 08:45:11 node-1 haproxy[3927]: 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 08:45:11 node-1 haproxy[3927]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:11 node-1 haproxy[3927]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:11 node-1 haproxy[3927]: proxy nova-metadata-api has no server available!
<129>Oct 28 08:45:11 node-1 haproxy[3927]: 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 08:45:11 node-1 haproxy[3927]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:11 node-1 haproxy[3927]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:11 node-1 haproxy[3927]: proxy cinder-api has no server available!
<129>Oct 28 08:45:11 node-1 haproxy[3927]: 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 08:45:11 node-1 haproxy[3927]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:11 node-1 haproxy[3927]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:11 node-1 haproxy[3927]: proxy glance-api has no server available!
<129>Oct 28 08:45:11 node-1 haproxy[3927]: 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 08:45:12 node-1 haproxy[3931]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy glance-glare has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy neutron has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy glance-registry has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy mysqld has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy object-storage has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy aodh has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy ceilometer has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy heat-api has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:12 node-1 haproxy[3931]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:12 node-1 haproxy[3931]: proxy heat-api-cfn has no server available!
<129>Oct 28 08:45:12 node-1 haproxy[3931]: 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 08:45:12 node-1 haproxy[3931]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:13 node-1 haproxy[3931]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:13 node-1 haproxy[3931]: proxy heat-api-cloudwatch has no server available!
<129>Oct 28 08:45:13 node-1 haproxy[3931]: 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 08:45:13 node-1 haproxy[3931]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 08:45:13 node-1 haproxy[3931]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, 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 08:45:13 node-1 haproxy[3931]: proxy nova-novncproxy has no server available!
<27>Oct 28 08:45:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:17 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:17 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:17 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:17 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:17 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:17 node-1 multipathd: uevent trigger error
<27>Oct 28 08:45:24 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 28 08:45:49 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 08:45:51 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 28 08:46:34 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 08:46:37 node-1 multipathd: uevent trigger error
<27>Oct 28 08:46:37 node-1 multipathd: uevent trigger error
<27>Oct 28 08:46:37 node-1 multipathd: uevent trigger error
<27>Oct 28 08:46:37 node-1 multipathd: uevent trigger error
<27>Oct 28 08:46:37 node-1 multipathd: uevent trigger error
<27>Oct 28 08:46:42 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 08:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 08:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 08:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 08:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 08:48:55 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:01 node-1 multipathd: uevent trigger error
<43>Oct 28 08:49:14 node-1 apache2_error [Fri Oct 28 08:49:11.820328 2016] [mpm_event:notice] [pid 10450:tid 139937328850816] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 08:49:14 node-1 apache2_error [Fri Oct 28 08:49:11.820403 2016] [core:notice] [pid 10450:tid 139937328850816] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 08:49:14 node-1 apache2_error [Fri Oct 28 08:49:14.503085 2016] [mpm_event:notice] [pid 10450:tid 139937328850816] AH00491: caught SIGTERM, shutting down
<27>Oct 28 08:49:19 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:20 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:20 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:20 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:20 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:20 node-1 multipathd: uevent trigger error
<43>Oct 28 08:49:24 node-1 apache2_error [Fri Oct 28 08:49:15.570162 2016] [mpm_worker:notice] [pid 12214:tid 140485500893056] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 08:49:24 node-1 apache2_error [Fri Oct 28 08:49:15.570193 2016] [core:notice] [pid 12214:tid 140485500893056] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 08:49:24 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:24 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:24 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:24 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:24 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:28 node-1 multipathd: uevent trigger error
<27>Oct 28 08:49:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 28 08:50:34 node-1 apache2_error [Fri Oct 28 08:50:30.418240 2016] [mpm_worker:notice] [pid 12214:tid 140485500893056] AH00295: caught SIGTERM, shutting down
<43>Oct 28 08:50:34 node-1 apache2_error [Fri Oct 28 08:50:31.155267 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 08:50:34 node-1 apache2_error [Fri Oct 28 08:50:31.155301 2016] [core:notice] [pid 24862:tid 139850134488960] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 08:51:14 node-1 apache2_error [Fri Oct 28 08:51:14.638823 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 08:51:14 node-1 apache2_error [Fri Oct 28 08:51:14.832348 2016] [mpm_worker:warn] [pid 24862:tid 139850134488960] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 08:51:14 node-1 apache2_error [Fri Oct 28 08:51:14.835573 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 08:51:14 node-1 apache2_error [Fri Oct 28 08:51:14.835591 2016] [core:notice] [pid 24862:tid 139850134488960] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 08:51:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:51:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:51:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:51:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:51:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:08 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:23 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 08:52:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:45 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:46 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:46 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:46 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:46 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:46 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:50 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:50 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:50 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:50 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:50 node-1 multipathd: uevent trigger error
<27>Oct 28 08:52:50 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:05 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:53:59 node-1 multipathd: uevent trigger error
<27>Oct 28 08:55:06 node-1 multipathd: uevent trigger error
<27>Oct 28 08:55:06 node-1 multipathd: uevent trigger error
<27>Oct 28 08:55:06 node-1 multipathd: uevent trigger error
<27>Oct 28 08:55:06 node-1 multipathd: uevent trigger error
<27>Oct 28 08:55:06 node-1 multipathd: uevent trigger error
<27>Oct 28 08:55:06 node-1 multipathd: uevent trigger error
<27>Oct 28 08:55:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 08:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:01 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:07 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:07 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:07 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:07 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:07 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:56:29 node-1 multipathd: uevent trigger error
<27>Oct 28 08:58:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 08:58:48 node-1 multipathd: uevent trigger error
<27>Oct 28 08:58:48 node-1 multipathd: uevent trigger error
<27>Oct 28 08:58:48 node-1 multipathd: uevent trigger error
<27>Oct 28 08:58:48 node-1 multipathd: uevent trigger error
<27>Oct 28 08:58:48 node-1 multipathd: uevent trigger error
<27>Oct 28 08:58:48 node-1 multipathd: uevent trigger error
<27>Oct 28 08:58:48 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:04 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:09 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:14 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:39 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:39 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:39 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:39 node-1 multipathd: uevent trigger error
<27>Oct 28 08:59:39 node-1 multipathd: uevent trigger error
<27>Oct 28 09:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 09:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 09:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 09:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 09:00:20 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:03 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:04 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:04 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:04 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:04 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:19 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:19 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:19 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:19 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:19 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:35 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:35 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:35 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:35 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:35 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:35 node-1 multipathd: uevent trigger error
<27>Oct 28 09:01:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 09:03:53 node-1 multipathd: uevent trigger error
<27>Oct 28 09:03:53 node-1 multipathd: uevent trigger error
<27>Oct 28 09:03:53 node-1 multipathd: uevent trigger error
<27>Oct 28 09:03:53 node-1 multipathd: uevent trigger error
<27>Oct 28 09:03:53 node-1 multipathd: uevent trigger error
<27>Oct 28 09:03:53 node-1 multipathd: uevent trigger error
<27>Oct 28 09:03:53 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:05 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:06 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:06 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:18 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:18 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:18 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:18 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:18 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:18 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:18 node-1 multipathd: uevent trigger error
<27>Oct 28 09:04:19 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct 28 09:04:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 09:05:10 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:10 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:10 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:10 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:10 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:15 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:48 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:48 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:48 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:48 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:48 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:05:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:08 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:08 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:08 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:08 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:08 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:14 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:14 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:14 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:14 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:14 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:14 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:06:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:07:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 09:08:00 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:00 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:00 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:00 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:00 node-1 multipathd: uevent trigger error
<11>Oct 28 09:08:13 node-1 liberasurecode[65634]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:13 node-1 liberasurecode[65634]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:13 node-1 liberasurecode[65634]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:13 node-1 liberasurecode[65634]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:13 node-1 liberasurecode[65658]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:13 node-1 liberasurecode[65658]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:13 node-1 liberasurecode[65658]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:13 node-1 liberasurecode[65658]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:15 node-1 liberasurecode[66040]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:15 node-1 liberasurecode[66040]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:15 node-1 liberasurecode[66040]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:15 node-1 liberasurecode[66040]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66709]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66709]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66709]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66709]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66750]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66750]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66794]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66794]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66794]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66794]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66851]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66851]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66851]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66851]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66868]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66868]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66868]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:19 node-1 liberasurecode[66868]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66882]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66882]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66882]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66882]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66894]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:20 node-1 liberasurecode[66894]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:36 node-1 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:36 node-1 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:36 node-1 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:08:36 node-1 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 09:08:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:44 node-1 multipathd: uevent trigger error
<27>Oct 28 09:08:44 node-1 multipathd: uevent trigger error
<43>Oct 28 09:09:36 node-1 apache2_error [Fri Oct 28 09:09:31.254564 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 09:09:36 node-1 apache2_error [Fri Oct 28 09:09:31.641590 2016] [mpm_worker:warn] [pid 24862:tid 139850134488960] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 09:09:36 node-1 apache2_error [Fri Oct 28 09:09:31.645420 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 09:09:36 node-1 apache2_error [Fri Oct 28 09:09:31.645441 2016] [core:notice] [pid 24862:tid 139850134488960] AH00094: Command line: '/usr/sbin/apache2'
<11>Oct 28 09:10:01 node-1 liberasurecode[79158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:10:01 node-1 liberasurecode[79158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:10:01 node-1 liberasurecode[79158]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:10:01 node-1 liberasurecode[79158]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 09:10:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:12 node-1 multipathd: uevent trigger error
<43>Oct 28 09:10:16 node-1 apache2_error [Fri Oct 28 09:10:08.480859 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 09:10:16 node-1 apache2_error [Fri Oct 28 09:10:08.676537 2016] [mpm_worker:warn] [pid 24862:tid 139850134488960] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 09:10:16 node-1 apache2_error [Fri Oct 28 09:10:08.682173 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 09:10:16 node-1 apache2_error [Fri Oct 28 09:10:08.682195 2016] [core:notice] [pid 24862:tid 139850134488960] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 09:10:37 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:37 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:37 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:37 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:37 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:37 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:43 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:43 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:43 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:43 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:43 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 09:10:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:10:51 node-1 multipathd: uevent trigger error
<43>Oct 28 09:11:26 node-1 apache2_error [Fri Oct 28 09:11:25.877312 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 09:11:26 node-1 apache2_error [Fri Oct 28 09:11:26.262584 2016] [mpm_worker:warn] [pid 24862:tid 139850134488960] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 09:11:26 node-1 apache2_error [Fri Oct 28 09:11:26.267038 2016] [mpm_worker:notice] [pid 24862:tid 139850134488960] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 09:11:26 node-1 apache2_error [Fri Oct 28 09:11:26.267063 2016] [core:notice] [pid 24862:tid 139850134488960] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 09:11:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:36 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:36 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:36 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:36 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:36 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:41 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:46 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:46 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:46 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:46 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:46 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:46 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:55 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:55 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:55 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:55 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:55 node-1 multipathd: uevent trigger error
<27>Oct 28 09:11:55 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:29 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:36 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 28 09:12:45 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:45 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:45 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:45 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:45 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:52 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:57 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:57 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:57 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:57 node-1 multipathd: uevent trigger error
<27>Oct 28 09:12:57 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:06 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:06 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:06 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:06 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:06 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:24 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:24 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:24 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:24 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:24 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 09:13:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:51 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:13:56 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:09 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:33 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:33 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:33 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:33 node-1 multipathd: uevent trigger error
<27>Oct 28 09:14:33 node-1 multipathd: uevent trigger error
<11>Oct 28 09:15:01 node-1 liberasurecode[151548]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:15:01 node-1 liberasurecode[151548]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:15:01 node-1 liberasurecode[151548]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 09:15:01 node-1 liberasurecode[151548]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 09:15:02 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:02 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:02 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:02 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:02 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:07 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:07 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:07 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:07 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:07 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:07 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:11 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:12 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:16 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:21 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:25 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:25 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:25 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:25 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:25 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:30 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:30 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:30 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:30 node-1 multipathd: uevent trigger error
<27>Oct 28 09:15:30 node-1 multipathd: uevent trigger error
