Oct 29 17:57:43 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8397" x-info="http://www.rsyslog.com"] start
Oct 29 17:57:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 29 17:57:43 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 29 17:57:43 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 29 17:57:43 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 29 17:57:43 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 29 17:57:43 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 29 17:57:43 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 29 17:57:43 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=d9465518-5722-4d2c-aa4f-f39d0569fd5b nomdmonddf nomdmonisw
Oct 29 17:57:43 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 29 17:57:43 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 29 17:57:43 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 29 17:57:43 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 29 17:57:43 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 29 17:57:43 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 29 17:57:43 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 29 17:57:43 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 29 17:57:43 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 29 17:57:43 node-1 kernel: [    0.000000] No AGP bridge found
Oct 29 17:57:43 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 29 17:57:43 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 29 17:57:43 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 29 17:57:43 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 29 17:57:43 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 29 17:57:43 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 29 17:57:43 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 29 17:57:43 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 29 17:57:43 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 29 17:57:43 node-1 kernel: [    0.000000]   2 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000]   3 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000]   4 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000]   5 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000]   6 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000]   7 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000]   8 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000]   9 disabled
Oct 29 17:57:43 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 29 17:57:43 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 29 17:57:43 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 29 17:57:43 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 29 17:57:43 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 29 17:57:43 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 29 17:57:43 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 29 17:57:43 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 29 17:57:43 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 29 17:57:43 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 29 17:57:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 29 17:57:43 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 29 17:57:43 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 29 17:57:43 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 29 17:57:43 node-1 kernel: [    0.000000] Zone ranges:
Oct 29 17:57:43 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 29 17:57:43 node-1 kernel: [    0.000000] Early memory node ranges
Oct 29 17:57:43 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct 29 17:57:43 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 29 17:57:43 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 29 17:57:43 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 29 17:57:43 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct 29 17:57:43 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct 29 17:57:43 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 29 17:57:43 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 29 17:57:43 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 29 17:57:43 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 29 17:57:43 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 29 17:57:43 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 29 17:57:43 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 29 17:57:43 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 29 17:57:43 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 29 17:57:43 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 29 17:57:43 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 29 17:57:43 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 29 17:57:43 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 29 17:57:43 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 29 17:57:43 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 29 17:57:43 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 29 17:57:43 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 29 17:57:43 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 29 17:57:43 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct 29 17:57:43 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 29 17:57:43 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=d9465518-5722-4d2c-aa4f-f39d0569fd5b nomdmonddf nomdmonisw
Oct 29 17:57:43 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 29 17:57:43 node-1 kernel: [    0.000000] Checking aperture...
Oct 29 17:57:43 node-1 kernel: [    0.000000] No AGP bridge found
Oct 29 17:57:43 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 29 17:57:43 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 29 17:57:43 node-1 kernel: [    0.000000] Memory: 32653456K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627180K reserved)
Oct 29 17:57:43 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 29 17:57:43 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 29 17:57:43 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 29 17:57:43 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 29 17:57:43 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 29 17:57:43 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 29 17:57:43 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 29 17:57:43 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 29 17:57:43 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 29 17:57:43 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 29 17:57:43 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 29 17:57:43 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 29 17:57:43 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 29 17:57:43 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 29 17:57:43 node-1 kernel: [    0.004000] tsc: Detected 3491.915 MHz processor
Oct 29 17:57:43 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.83 BogoMIPS (lpj=13967660)
Oct 29 17:57:43 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 29 17:57:43 node-1 kernel: [    0.000043] Security Framework initialized
Oct 29 17:57:43 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Oct 29 17:57:43 node-1 kernel: [    0.000062] Yama: becoming mindful.
Oct 29 17:57:43 node-1 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.006390] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.008324] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.008352] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.008644] Initializing cgroup subsys memory
Oct 29 17:57:43 node-1 kernel: [    0.008651] Initializing cgroup subsys devices
Oct 29 17:57:43 node-1 kernel: [    0.008653] Initializing cgroup subsys freezer
Oct 29 17:57:43 node-1 kernel: [    0.008655] Initializing cgroup subsys blkio
Oct 29 17:57:43 node-1 kernel: [    0.008657] Initializing cgroup subsys perf_event
Oct 29 17:57:43 node-1 kernel: [    0.008659] Initializing cgroup subsys hugetlb
Oct 29 17:57:43 node-1 kernel: [    0.008679] CPU: Physical Processor ID: 0
Oct 29 17:57:43 node-1 kernel: [    0.008680] CPU: Processor Core ID: 0
Oct 29 17:57:43 node-1 kernel: [    0.008684] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 29 17:57:43 node-1 kernel: [    0.008684] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 29 17:57:43 node-1 kernel: [    0.009377] mce: CPU supports 22 MCE banks
Oct 29 17:57:43 node-1 kernel: [    0.009405] CPU0: Thermal monitoring enabled (TM1)
Oct 29 17:57:43 node-1 kernel: [    0.009426] process: using mwait in idle threads
Oct 29 17:57:43 node-1 kernel: [    0.009429] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 29 17:57:43 node-1 kernel: [    0.009429] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 29 17:57:43 node-1 kernel: [    0.009429] tlb_flushall_shift: 6
Oct 29 17:57:43 node-1 kernel: [    0.009517] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 29 17:57:43 node-1 kernel: [    0.010240] ACPI: Core revision 20131115
Oct 29 17:57:43 node-1 kernel: [    0.023060] ACPI: All ACPI Tables successfully acquired
Oct 29 17:57:43 node-1 kernel: [    0.023225] ftrace: allocating 28622 entries in 112 pages
Oct 29 17:57:43 node-1 kernel: [    0.031974] dmar: Host address width 46
Oct 29 17:57:43 node-1 kernel: [    0.031976] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 29 17:57:43 node-1 kernel: [    0.031982] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 29 17:57:43 node-1 kernel: [    0.031984] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 29 17:57:43 node-1 kernel: [    0.031988] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 29 17:57:43 node-1 kernel: [    0.031990] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 29 17:57:43 node-1 kernel: [    0.031991] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 29 17:57:43 node-1 kernel: [    0.031992] dmar: ATSR flags: 0x0
Oct 29 17:57:43 node-1 kernel: [    0.031993] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 29 17:57:43 node-1 kernel: [    0.031994] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 29 17:57:43 node-1 kernel: [    0.032110] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 29 17:57:43 node-1 kernel: [    0.032111] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 29 17:57:43 node-1 kernel: [    0.032112] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 29 17:57:43 node-1 kernel: [    0.032113] HPET id 0 under DRHD base 0xc7ffc000
Oct 29 17:57:43 node-1 kernel: [    0.032114] Your BIOS is broken and requested that x2apic be disabled.
Oct 29 17:57:43 node-1 kernel: [    0.032114] This will slightly decrease performance.
Oct 29 17:57:43 node-1 kernel: [    0.032114] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 29 17:57:43 node-1 kernel: [    0.032545] Enabled IRQ remapping in xapic mode
Oct 29 17:57:43 node-1 kernel: [    0.032546] x2apic not enabled, IRQ remapping is in xapic mode
Oct 29 17:57:43 node-1 kernel: [    0.032550] Switched APIC routing to physical flat.
Oct 29 17:57:43 node-1 kernel: [    0.033128] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 29 17:57:43 node-1 kernel: [    0.072777] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 29 17:57:43 node-1 kernel: [    0.072783] TSC deadline timer enabled
Oct 29 17:57:43 node-1 kernel: [    0.072790] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 29 17:57:43 node-1 kernel: [    0.072797] ... version:                3
Oct 29 17:57:43 node-1 kernel: [    0.072798] ... bit width:              48
Oct 29 17:57:43 node-1 kernel: [    0.072799] ... generic registers:      4
Oct 29 17:57:43 node-1 kernel: [    0.072800] ... value mask:             0000ffffffffffff
Oct 29 17:57:43 node-1 kernel: [    0.072801] ... max period:             0000ffffffffffff
Oct 29 17:57:43 node-1 kernel: [    0.072802] ... fixed-purpose events:   3
Oct 29 17:57:43 node-1 kernel: [    0.072803] ... event mask:             000000070000000f
Oct 29 17:57:43 node-1 kernel: [    0.074212] x86: Booting SMP configuration:
Oct 29 17:57:43 node-1 kernel: [    0.088316] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 29 17:57:43 node-1 kernel: [    0.074214] .... node  #0, CPUs:        #1  #2  #3
Oct 29 17:57:43 node-1 kernel: [    0.116221] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 29 17:57:43 node-1 kernel: [    0.270357] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 29 17:57:43 node-1 kernel: [    0.326019] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 29 17:57:43 node-1 kernel: [    0.383066] x86: Booted up 2 nodes, 16 CPUs
Oct 29 17:57:43 node-1 kernel: [    0.383070] smpboot: Total of 16 processors activated (111753.56 BogoMIPS)
Oct 29 17:57:43 node-1 kernel: [    0.407566] devtmpfs: initialized
Oct 29 17:57:43 node-1 kernel: [    0.410041] EVM: security.selinux
Oct 29 17:57:43 node-1 kernel: [    0.410043] EVM: security.SMACK64
Oct 29 17:57:43 node-1 kernel: [    0.410044] EVM: security.ima
Oct 29 17:57:43 node-1 kernel: [    0.410045] EVM: security.capability
Oct 29 17:57:43 node-1 kernel: [    0.410095] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.410761] pinctrl core: initialized pinctrl subsystem
Oct 29 17:57:43 node-1 kernel: [    0.410823] regulator-dummy: no parameters
Oct 29 17:57:43 node-1 kernel: [    0.410855] RTC time: 17:57:07, date: 10/29/16
Oct 29 17:57:43 node-1 kernel: [    0.410889] NET: Registered protocol family 16
Oct 29 17:57:43 node-1 kernel: [    0.410974] cpuidle: using governor ladder
Oct 29 17:57:43 node-1 kernel: [    0.410975] cpuidle: using governor menu
Oct 29 17:57:43 node-1 kernel: [    0.411009] ACPI: bus type PCI registered
Oct 29 17:57:43 node-1 kernel: [    0.411011] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 29 17:57:43 node-1 kernel: [    0.411056] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 29 17:57:43 node-1 kernel: [    0.411059] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 29 17:57:43 node-1 kernel: [    0.424804] PCI: Using configuration type 1 for base access
Oct 29 17:57:43 node-1 kernel: [    0.425801] bio: create slab <bio-0> at 0
Oct 29 17:57:43 node-1 kernel: [    0.426086] ACPI: Added _OSI(Module Device)
Oct 29 17:57:43 node-1 kernel: [    0.426087] ACPI: Added _OSI(Processor Device)
Oct 29 17:57:43 node-1 kernel: [    0.426089] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 29 17:57:43 node-1 kernel: [    0.426090] ACPI: Added _OSI(Processor Aggregator Device)
Oct 29 17:57:43 node-1 kernel: [    0.438774] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 29 17:57:43 node-1 kernel: [    0.450375] ACPI: Interpreter enabled
Oct 29 17:57:43 node-1 kernel: [    0.450381] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 29 17:57:43 node-1 kernel: [    0.450385] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 29 17:57:43 node-1 kernel: [    0.450388] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 29 17:57:43 node-1 kernel: [    0.450395] ACPI: (supports S0 S4 S5)
Oct 29 17:57:43 node-1 kernel: [    0.450396] ACPI: Using IOAPIC for interrupt routing
Oct 29 17:57:43 node-1 kernel: [    0.450437] HEST: Table parsing has been initialized.
Oct 29 17:57:43 node-1 kernel: [    0.450440] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 29 17:57:43 node-1 kernel: [    0.450992] ACPI: No dock devices found.
Oct 29 17:57:43 node-1 kernel: [    0.462536] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 29 17:57:43 node-1 kernel: [    0.462540] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 17:57:43 node-1 kernel: [    0.462544] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 29 17:57:43 node-1 kernel: [    0.462572] PCI host bridge to bus 0000:ff
Oct 29 17:57:43 node-1 kernel: [    0.462574] pci_bus 0000:ff: root bus resource [bus ff]
Oct 29 17:57:43 node-1 kernel: [    0.462583] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462621] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.462652] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462687] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462716] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.462745] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.462776] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462806] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462839] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462867] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462893] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462919] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462947] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.462973] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463000] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463026] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463055] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463082] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463109] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.463137] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463163] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.463189] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463215] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463245] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.463280] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463311] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463340] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463371] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463402] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463433] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463463] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463494] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463524] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463557] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463590] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463623] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463657] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463688] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463715] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463746] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463779] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463818] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463852] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463885] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463915] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463945] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.463975] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464004] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464034] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464064] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464095] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464124] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464152] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464182] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464211] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464242] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464273] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464330] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 29 17:57:43 node-1 kernel: [    0.464332] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 17:57:43 node-1 kernel: [    0.464335] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 29 17:57:43 node-1 kernel: [    0.464353] PCI host bridge to bus 0000:7f
Oct 29 17:57:43 node-1 kernel: [    0.464355] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 29 17:57:43 node-1 kernel: [    0.464360] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464389] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.464419] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464451] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464474] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.464500] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.464528] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464556] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464581] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464612] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464638] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464664] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464691] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464715] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464740] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464773] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464796] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464821] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464846] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.464871] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464895] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.464920] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464944] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.464972] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 29 17:57:43 node-1 kernel: [    0.465006] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465034] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465062] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465092] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465119] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465147] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465175] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465204] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465230] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465258] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465288] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465318] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465347] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465373] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465399] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465428] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465455] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465484] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465516] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465544] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465571] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465597] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465624] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465654] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465682] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465710] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465742] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465769] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465794] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465821] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 29 17:57:43 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 29 17:57:43 node-1 kernel: [    0.465849] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465879] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.465907] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.467188] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 29 17:57:43 node-1 kernel: [    0.467191] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 17:57:43 node-1 kernel: [    0.468389] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 29 17:57:43 node-1 kernel: [    0.468931] PCI host bridge to bus 0000:00
Oct 29 17:57:43 node-1 kernel: [    0.468933] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 29 17:57:43 node-1 kernel: [    0.468935] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 29 17:57:43 node-1 kernel: [    0.468936] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 29 17:57:43 node-1 kernel: [    0.468938] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 29 17:57:43 node-1 kernel: [    0.468939] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 29 17:57:43 node-1 kernel: [    0.468940] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 29 17:57:43 node-1 kernel: [    0.468942] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 29 17:57:43 node-1 kernel: [    0.468948] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 29 17:57:43 node-1 kernel: [    0.469030] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.469060] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.469102] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 29 17:57:43 node-1 kernel: [    0.469121] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.469151] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.469191] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 29 17:57:43 node-1 kernel: [    0.469209] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.469239] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.469279] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 29 17:57:43 node-1 kernel: [    0.469296] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.469365] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.469442] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.469517] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 29 17:57:43 node-1 kernel: [    0.469522] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 29 17:57:43 node-1 kernel: [    0.469606] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 29 17:57:43 node-1 kernel: [    0.469754] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 29 17:57:43 node-1 kernel: [    0.469771] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 29 17:57:43 node-1 kernel: [    0.469849] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.469902] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 29 17:57:43 node-1 kernel: [    0.469923] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.469978] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.470022] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 29 17:57:43 node-1 kernel: [    0.470048] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.470104] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.470147] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 29 17:57:43 node-1 kernel: [    0.470171] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 29 17:57:43 node-1 kernel: [    0.470188] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 29 17:57:43 node-1 kernel: [    0.470265] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.470315] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 29 17:57:43 node-1 kernel: [    0.470341] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 29 17:57:43 node-1 kernel: [    0.470587] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 29 17:57:43 node-1 kernel: [    0.470593] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 29 17:57:43 node-1 kernel: [    0.470599] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.470605] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.470612] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 29 17:57:43 node-1 kernel: [    0.470642] pci 0000:01:00.0: supports D1 D2
Oct 29 17:57:43 node-1 kernel: [    0.476606] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 29 17:57:43 node-1 kernel: [    0.476609] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 29 17:57:43 node-1 kernel: [    0.476611] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 29 17:57:43 node-1 kernel: [    0.476717] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.476750] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 29 17:57:43 node-1 kernel: [    0.484612] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 29 17:57:43 node-1 kernel: [    0.484618] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.484622] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 29 17:57:43 node-1 kernel: [    0.484706] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.484778] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.484873] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.484954] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 29 17:57:43 node-1 kernel: [    0.484961] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.484965] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 29 17:57:43 node-1 kernel: [    0.485045] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.485181] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.485234] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 29 17:57:43 node-1 kernel: [    0.485237] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.485239] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.485288] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.485422] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.485463] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.485582] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.485618] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.485738] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.485773] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 29 17:57:43 node-1 kernel: [    0.485894] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 29 17:57:43 node-1 kernel: [    0.485934] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 29 17:57:43 node-1 kernel: [    0.485937] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.485939] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.485999] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 29 17:57:43 node-1 kernel: [    0.486061] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.486114] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.486155] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 29 17:57:43 node-1 kernel: [    0.486237] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 29 17:57:43 node-1 kernel: [    0.486342] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 29 17:57:43 node-1 kernel: [    0.486345] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.486347] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.486424] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 29 17:57:43 node-1 kernel: [    0.486485] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.486534] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.486746] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 29 17:57:43 node-1 kernel: [    0.486750] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 29 17:57:43 node-1 kernel: [    0.486813] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 29 17:57:43 node-1 kernel: [    0.486866] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.486914] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.487126] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 29 17:57:43 node-1 kernel: [    0.487130] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 29 17:57:43 node-1 kernel: [    0.487188] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 29 17:57:43 node-1 kernel: [    0.487248] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.487300] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 29 17:57:43 node-1 kernel: [    0.487550] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 29 17:57:43 node-1 kernel: [    0.487553] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 29 17:57:43 node-1 kernel: [    0.487727] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 29 17:57:43 node-1 kernel: [    0.487765] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 29 17:57:43 node-1 kernel: [    0.487842] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 29 17:57:43 node-1 kernel: [    0.487860] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 29 17:57:43 node-1 kernel: [    0.487873] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 29 17:57:43 node-1 kernel: [    0.487887] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 29 17:57:43 node-1 kernel: [    0.487937] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 29 17:57:43 node-1 kernel: [    0.492620] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 29 17:57:43 node-1 kernel: [    0.492629] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 29 17:57:43 node-1 kernel: [    0.492682] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 29 17:57:43 node-1 kernel: [    0.493239] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 29 17:57:43 node-1 kernel: [    0.493242] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 29 17:57:43 node-1 kernel: [    0.493362] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 29 17:57:43 node-1 kernel: [    0.493468] PCI host bridge to bus 0000:80
Oct 29 17:57:43 node-1 kernel: [    0.493470] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 29 17:57:43 node-1 kernel: [    0.493471] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 29 17:57:43 node-1 kernel: [    0.493473] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 29 17:57:43 node-1 kernel: [    0.493481] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.493544] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.493611] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 29 17:57:43 node-1 kernel: [    0.493672] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 29 17:57:43 node-1 kernel: [    0.493677] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 29 17:57:43 node-1 kernel: [    0.493748] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 29 17:57:43 node-1 kernel: [    0.494045] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 29 17:57:43 node-1 kernel: [    0.494076] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 29 17:57:43 node-1 kernel: [    0.494106] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 29 17:57:43 node-1 kernel: [    0.494135] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 29 17:57:43 node-1 kernel: [    0.494164] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 29 17:57:43 node-1 kernel: [    0.494194] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 29 17:57:43 node-1 kernel: [    0.494224] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 29 17:57:43 node-1 kernel: [    0.494253] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 29 17:57:43 node-1 kernel: [    0.494338] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 29 17:57:43 node-1 kernel: [    0.494342] ACPI: \_SB_.UNC1: notify handler is installed
Oct 29 17:57:43 node-1 kernel: [    0.494344] ACPI: \_SB_.UNC0: notify handler is installed
Oct 29 17:57:43 node-1 kernel: [    0.494358] ACPI: \_SB_.PCI0: notify handler is installed
Oct 29 17:57:43 node-1 kernel: [    0.494411] ACPI: \_SB_.PCI1: notify handler is installed
Oct 29 17:57:43 node-1 kernel: [    0.494490] Found 4 acpi root devices
Oct 29 17:57:43 node-1 kernel: [    0.494597] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 29 17:57:43 node-1 kernel: [    0.494599] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 29 17:57:43 node-1 kernel: [    0.494601] vgaarb: loaded
Oct 29 17:57:43 node-1 kernel: [    0.494602] vgaarb: bridge control possible 0000:0c:00.0
Oct 29 17:57:43 node-1 kernel: [    0.494712] SCSI subsystem initialized
Oct 29 17:57:43 node-1 kernel: [    0.494777] libata version 3.00 loaded.
Oct 29 17:57:43 node-1 kernel: [    0.494792] ACPI: bus type USB registered
Oct 29 17:57:43 node-1 kernel: [    0.494802] usbcore: registered new interface driver usbfs
Oct 29 17:57:43 node-1 kernel: [    0.494807] usbcore: registered new interface driver hub
Oct 29 17:57:43 node-1 kernel: [    0.494831] usbcore: registered new device driver usb
Oct 29 17:57:43 node-1 kernel: [    0.494993] PCI: Using ACPI for IRQ routing
Oct 29 17:57:43 node-1 kernel: [    0.498584] PCI: pci_cache_line_size set to 64 bytes
Oct 29 17:57:43 node-1 kernel: [    0.498784] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 29 17:57:43 node-1 kernel: [    0.498786] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct 29 17:57:43 node-1 kernel: [    0.498786] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 29 17:57:43 node-1 kernel: [    0.498848] NetLabel: Initializing
Oct 29 17:57:43 node-1 kernel: [    0.498850] NetLabel:  domain hash size = 128
Oct 29 17:57:43 node-1 kernel: [    0.498850] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 29 17:57:43 node-1 kernel: [    0.498860] NetLabel:  unlabeled traffic allowed by default
Oct 29 17:57:43 node-1 kernel: [    0.498915] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 29 17:57:43 node-1 kernel: [    0.498919] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 29 17:57:43 node-1 kernel: [    0.500979] Switched to clocksource hpet
Oct 29 17:57:43 node-1 kernel: [    0.504827] AppArmor: AppArmor Filesystem Enabled
Oct 29 17:57:43 node-1 kernel: [    0.504842] pnp: PnP ACPI init
Oct 29 17:57:43 node-1 kernel: [    0.504848] ACPI: bus type PNP registered
Oct 29 17:57:43 node-1 kernel: [    0.504972] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 29 17:57:43 node-1 kernel: [    0.504980] pnp 00:01: [dma 4]
Oct 29 17:57:43 node-1 kernel: [    0.504992] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505019] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505039] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505057] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505091] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505145] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505147] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 29 17:57:43 node-1 kernel: [    0.505149] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505150] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505152] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505157] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505159] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 29 17:57:43 node-1 kernel: [    0.505160] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505162] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505163] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505165] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505166] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505168] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 29 17:57:43 node-1 kernel: [    0.505170] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505253] pnp 00:07: [dma 0 disabled]
Oct 29 17:57:43 node-1 kernel: [    0.505282] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505356] pnp 00:08: [dma 0 disabled]
Oct 29 17:57:43 node-1 kernel: [    0.505389] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505439] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 29 17:57:43 node-1 kernel: [    0.505785] pnp: PnP ACPI: found 10 devices
Oct 29 17:57:43 node-1 kernel: [    0.505786] ACPI: bus type PNP unregistered
Oct 29 17:57:43 node-1 kernel: [    0.512074] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 29 17:57:43 node-1 kernel: [    0.512077] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 29 17:57:43 node-1 kernel: [    0.512079] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 29 17:57:43 node-1 kernel: [    0.512084] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 29 17:57:43 node-1 kernel: [    0.512085] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512100] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512129] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 29 17:57:43 node-1 kernel: [    0.512144] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512173] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 29 17:57:43 node-1 kernel: [    0.512187] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 29 17:57:43 node-1 kernel: [    0.512216] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 29 17:57:43 node-1 kernel: [    0.512231] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 29 17:57:43 node-1 kernel: [    0.512259] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 29 17:57:43 node-1 kernel: [    0.512261] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512276] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512305] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 29 17:57:43 node-1 kernel: [    0.512307] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512321] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512352] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 29 17:57:43 node-1 kernel: [    0.512354] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512357] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512361] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 29 17:57:43 node-1 kernel: [    0.512363] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512365] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512369] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 29 17:57:43 node-1 kernel: [    0.512374] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 29 17:57:43 node-1 kernel: [    0.512381] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 29 17:57:43 node-1 kernel: [    0.512385] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 29 17:57:43 node-1 kernel: [    0.512391] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 29 17:57:43 node-1 kernel: [    0.512392] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 29 17:57:43 node-1 kernel: [    0.512393] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 29 17:57:43 node-1 kernel: [    0.512394] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 29 17:57:43 node-1 kernel: [    0.512395] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 29 17:57:43 node-1 kernel: [    0.512396] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 29 17:57:43 node-1 kernel: [    0.512397] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 29 17:57:43 node-1 kernel: [    0.512397] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 29 17:57:43 node-1 kernel: [    0.512398] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512399] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512400] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512401] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512402] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512403] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512404] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512405] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512406] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 29 17:57:43 node-1 kernel: [    0.512407] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512408] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 29 17:57:43 node-1 kernel: [    0.512409] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 29 17:57:43 node-1 kernel: [    0.512410] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 29 17:57:43 node-1 kernel: [    0.512411] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 29 17:57:43 node-1 kernel: [    0.512413] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 29 17:57:43 node-1 kernel: [    0.512414] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 29 17:57:43 node-1 kernel: [    0.512453] NET: Registered protocol family 2
Oct 29 17:57:43 node-1 kernel: [    0.512709] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.513051] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.513196] TCP: Hash tables configured (established 262144 bind 65536)
Oct 29 17:57:43 node-1 kernel: [    0.513239] TCP: reno registered
Oct 29 17:57:43 node-1 kernel: [    0.513268] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.513362] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.513516] NET: Registered protocol family 1
Oct 29 17:57:43 node-1 kernel: [    0.553071] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 29 17:57:43 node-1 kernel: [    0.553085] PCI: CLS 64 bytes, default 64
Oct 29 17:57:43 node-1 kernel: [    0.553162] Trying to unpack rootfs image as initramfs...
Oct 29 17:57:43 node-1 kernel: [    0.772838] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Oct 29 17:57:43 node-1 kernel: [    0.772871] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 29 17:57:43 node-1 kernel: [    0.772873] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct 29 17:57:43 node-1 kernel: [    0.773285] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773291] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773296] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773301] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773311] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773322] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773330] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773339] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773347] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773355] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773362] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773368] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773375] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773383] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773391] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773398] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 29 17:57:43 node-1 kernel: [    0.773439] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 29 17:57:43 node-1 kernel: [    0.773443] Scanning for low memory corruption every 60 seconds
Oct 29 17:57:43 node-1 kernel: [    0.773733] Initialise system trusted keyring
Oct 29 17:57:43 node-1 kernel: [    0.773779] audit: initializing netlink socket (disabled)
Oct 29 17:57:43 node-1 kernel: [    0.773789] type=2000 audit(1477763826.724:1): initialized
Oct 29 17:57:43 node-1 kernel: [    0.791477] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 29 17:57:43 node-1 kernel: [    0.792928] zbud: loaded
Oct 29 17:57:43 node-1 kernel: [    0.793038] VFS: Disk quotas dquot_6.5.2
Oct 29 17:57:43 node-1 kernel: [    0.793076] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 29 17:57:43 node-1 kernel: [    0.793432] fuse init (API version 7.22)
Oct 29 17:57:43 node-1 kernel: [    0.793489] msgmni has been set to 32768
Oct 29 17:57:43 node-1 kernel: [    0.793534] Key type big_key registered
Oct 29 17:57:43 node-1 kernel: [    0.794054] Key type asymmetric registered
Oct 29 17:57:43 node-1 kernel: [    0.794058] Asymmetric key parser 'x509' registered
Oct 29 17:57:43 node-1 kernel: [    0.794094] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 29 17:57:43 node-1 kernel: [    0.794152] io scheduler noop registered
Oct 29 17:57:43 node-1 kernel: [    0.794153] io scheduler deadline registered (default)
Oct 29 17:57:43 node-1 kernel: [    0.794169] io scheduler cfq registered
Oct 29 17:57:43 node-1 kernel: [    0.794492] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    0.794583] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    0.794670] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    0.794756] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    0.794851] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    0.794916] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    0.795178] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 29 17:57:43 node-1 kernel: [    0.795196] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 29 17:57:43 node-1 kernel: [    0.795209] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 29 17:57:43 node-1 kernel: [    0.795219] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795221] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795223] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 29 17:57:43 node-1 kernel: [    0.795227] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795228] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795230] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795231] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795232] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795234] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795235] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795236] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795238] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795239] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795240] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795242] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795244] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 29 17:57:43 node-1 kernel: [    0.795248] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795250] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 29 17:57:43 node-1 kernel: [    0.795258] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795261] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 29 17:57:43 node-1 kernel: [    0.795270] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795272] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 29 17:57:43 node-1 kernel: [    0.795275] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 29 17:57:43 node-1 kernel: [    0.795287] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 29 17:57:43 node-1 kernel: [    0.795374] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 29 17:57:43 node-1 kernel: [    0.795379] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 29 17:57:43 node-1 kernel: [    0.795387] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 29 17:57:43 node-1 kernel: [    0.795424] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 29 17:57:43 node-1 kernel: [    0.795425] vesafb: scrolling: redraw
Oct 29 17:57:43 node-1 kernel: [    0.795426] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 29 17:57:43 node-1 kernel: [    0.816450] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 29 17:57:43 node-1 kernel: [    0.825102] Console: switching to colour frame buffer device 80x30
Oct 29 17:57:43 node-1 kernel: [    0.833961] fb0: VESA VGA frame buffer device
Oct 29 17:57:43 node-1 kernel: [    0.834164] intel_idle: MWAIT substates: 0x2120
Oct 29 17:57:43 node-1 kernel: [    0.834165] intel_idle: v0.4 model 0x3F
Oct 29 17:57:43 node-1 kernel: [    0.834166] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 29 17:57:43 node-1 kernel: [    0.834413] ipmi message handler version 39.2
Oct 29 17:57:43 node-1 kernel: [    0.834681] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 29 17:57:43 node-1 kernel: [    0.835116] ACPI: AC Adapter [P111] (on-line)
Oct 29 17:57:43 node-1 kernel: [    0.840398] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 29 17:57:43 node-1 kernel: [    0.851444] ACPI: Power Button [PWRB]
Oct 29 17:57:43 node-1 kernel: [    0.857229] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 29 17:57:43 node-1 kernel: [    0.868846] ACPI: Power Button [PWRF]
Oct 29 17:57:43 node-1 kernel: [    0.894648] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 29 17:57:43 node-1 kernel: [    0.906294] pstore: Registered erst as persistent store backend
Oct 29 17:57:43 node-1 kernel: [    0.912486] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 29 17:57:43 node-1 kernel: [    0.924446] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 29 17:57:43 node-1 kernel: [    0.951203] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 29 17:57:43 node-1 kernel: [    0.984481] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 29 17:57:43 node-1 kernel: [    0.998547] Linux agpgart interface v0.103
Oct 29 17:57:43 node-1 kernel: [    1.006204] brd: module loaded
Oct 29 17:57:43 node-1 kernel: [    1.013256] loop: module loaded
Oct 29 17:57:43 node-1 kernel: [    1.019965] libphy: Fixed MDIO Bus: probed
Oct 29 17:57:43 node-1 kernel: [    1.026437] tun: Universal TUN/TAP device driver, 1.6
Oct 29 17:57:43 node-1 kernel: [    1.032911] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 29 17:57:43 node-1 kernel: [    1.039426] PPP generic driver version 2.4.2
Oct 29 17:57:43 node-1 kernel: [    1.045817] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 29 17:57:43 node-1 kernel: [    1.052271] ehci-pci: EHCI PCI platform driver
Oct 29 17:57:43 node-1 kernel: [    1.058871] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 29 17:57:43 node-1 kernel: [    1.065280] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 29 17:57:43 node-1 kernel: [    1.077820] ehci-pci 0000:00:1a.0: debug port 2
Oct 29 17:57:43 node-1 kernel: [    1.088011] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 29 17:57:43 node-1 kernel: [    1.088029] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 29 17:57:43 node-1 kernel: [    1.104467] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 29 17:57:43 node-1 kernel: [    1.110547] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 29 17:57:43 node-1 kernel: [    1.116718] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 29 17:57:43 node-1 kernel: [    1.128623] usb usb1: Product: EHCI Host Controller
Oct 29 17:57:43 node-1 kernel: [    1.134656] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 29 17:57:43 node-1 kernel: [    1.140697] usb usb1: SerialNumber: 0000:00:1a.0
Oct 29 17:57:43 node-1 kernel: [    1.146675] hub 1-0:1.0: USB hub found
Oct 29 17:57:43 node-1 kernel: [    1.152446] hub 1-0:1.0: 2 ports detected
Oct 29 17:57:43 node-1 kernel: [    1.158229] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 29 17:57:43 node-1 kernel: [    1.163814] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 29 17:57:43 node-1 kernel: [    1.174723] ehci-pci 0000:00:1d.0: debug port 2
Oct 29 17:57:43 node-1 kernel: [    1.184027] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 29 17:57:43 node-1 kernel: [    1.184030] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 29 17:57:43 node-1 kernel: [    1.200386] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 29 17:57:43 node-1 kernel: [    1.205595] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 29 17:57:43 node-1 kernel: [    1.210898] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 29 17:57:43 node-1 kernel: [    1.221474] usb usb2: Product: EHCI Host Controller
Oct 29 17:57:43 node-1 kernel: [    1.226942] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 29 17:57:43 node-1 kernel: [    1.232494] usb usb2: SerialNumber: 0000:00:1d.0
Oct 29 17:57:43 node-1 kernel: [    1.238021] hub 2-0:1.0: USB hub found
Oct 29 17:57:43 node-1 kernel: [    1.243381] hub 2-0:1.0: 2 ports detected
Oct 29 17:57:43 node-1 kernel: [    1.248678] ehci-platform: EHCI generic platform driver
Oct 29 17:57:43 node-1 kernel: [    1.253912] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 29 17:57:43 node-1 kernel: [    1.259231] ohci-pci: OHCI PCI platform driver
Oct 29 17:57:43 node-1 kernel: [    1.264532] ohci-platform: OHCI generic platform driver
Oct 29 17:57:43 node-1 kernel: [    1.269737] uhci_hcd: USB Universal Host Controller Interface driver
Oct 29 17:57:43 node-1 kernel: [    1.275081] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 29 17:57:43 node-1 kernel: [    1.468167] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 29 17:57:43 node-1 kernel: [    1.628309] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 29 17:57:43 node-1 kernel: [    1.633836] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 29 17:57:43 node-1 kernel: [    1.639573] hub 1-1:1.0: USB hub found
Oct 29 17:57:43 node-1 kernel: [    1.645046] hub 1-1:1.0: 6 ports detected
Oct 29 17:57:43 node-1 kernel: [    1.759911] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 29 17:57:43 node-1 kernel: [    1.771925] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 29 17:57:43 node-1 kernel: [    2.027971] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 29 17:57:43 node-1 kernel: [    2.033529] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 29 17:57:43 node-1 kernel: [    2.039364] hub 2-1:1.0: USB hub found
Oct 29 17:57:43 node-1 kernel: [    2.045083] hub 2-1:1.0: 8 ports detected
Oct 29 17:57:43 node-1 kernel: [    2.316468] i8042: No controller found
Oct 29 17:57:43 node-1 kernel: [    2.321879] mousedev: PS/2 mouse device common for all mice
Oct 29 17:57:43 node-1 kernel: [    2.323507] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 29 17:57:43 node-1 kernel: [    2.332991] rtc_cmos 00:02: RTC can wake from S4
Oct 29 17:57:43 node-1 kernel: [    2.338725] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 29 17:57:43 node-1 kernel: [    2.344349] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 29 17:57:43 node-1 kernel: [    2.355456] device-mapper: uevent: version 1.0.3
Oct 29 17:57:43 node-1 kernel: [    2.361090] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 29 17:57:43 node-1 kernel: [    2.372331] ledtrig-cpu: registered to indicate activity on CPUs
Oct 29 17:57:43 node-1 kernel: [    2.378265] TCP: cubic registered
Oct 29 17:57:43 node-1 kernel: [    2.384152] NET: Registered protocol family 10
Oct 29 17:57:43 node-1 kernel: [    2.390242] NET: Registered protocol family 17
Oct 29 17:57:43 node-1 kernel: [    2.396014] Key type dns_resolver registered
Oct 29 17:57:43 node-1 kernel: [    2.402026] Loading compiled-in X.509 certificates
Oct 29 17:57:43 node-1 kernel: [    2.408262] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 29 17:57:43 node-1 kernel: [    2.419680] registered taskstats version 1
Oct 29 17:57:43 node-1 kernel: [    2.427647] Key type trusted registered
Oct 29 17:57:43 node-1 kernel: [    2.435201] Key type encrypted registered
Oct 29 17:57:43 node-1 kernel: [    2.440662] AppArmor: AppArmor sha1 policy hashing enabled
Oct 29 17:57:43 node-1 kernel: [    2.446175] IMA: No TPM chip found, activating TPM-bypass!
Oct 29 17:57:43 node-1 kernel: [    2.452338] regulator-dummy: disabling
Oct 29 17:57:43 node-1 kernel: [    2.456301] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 29 17:57:43 node-1 kernel: [    2.456302] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 29 17:57:43 node-1 kernel: [    2.456303] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 29 17:57:43 node-1 kernel: [    2.456304] usb 2-1.4: Manufacturer: Avocent
Oct 29 17:57:43 node-1 kernel: [    2.456304] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 29 17:57:43 node-1 kernel: [    2.491446]   Magic number: 4:451:998
Oct 29 17:57:43 node-1 kernel: [    2.497051] pnp 00:00: hash matches
Oct 29 17:57:43 node-1 kernel: [    2.502765] rtc_cmos 00:02: setting system clock to 2016-10-29 17:57:09 UTC (1477763829)
Oct 29 17:57:43 node-1 kernel: [    2.515187] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 29 17:57:43 node-1 kernel: [    2.520892] EDD information not available.
Oct 29 17:57:43 node-1 kernel: [    2.526504] PM: Hibernation image not present or could not be loaded.
Oct 29 17:57:43 node-1 kernel: [    2.527356] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 29 17:57:43 node-1 kernel: [    2.538679] Write protecting the kernel read-only data: 12288k
Oct 29 17:57:43 node-1 kernel: [    2.544847] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 29 17:57:43 node-1 kernel: [    2.557282] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 29 17:57:43 node-1 kernel: [    2.590477] device-mapper: multipath: version 1.6.0 loaded
Oct 29 17:57:43 node-1 kernel: [    2.598493] systemd-udevd[215]: starting version 204
Oct 29 17:57:43 node-1 kernel: [    2.625460] md: linear personality registered for level -1
Oct 29 17:57:43 node-1 kernel: [    2.640073] md: multipath personality registered for level -4
Oct 29 17:57:43 node-1 kernel: [    2.648196] md: raid0 personality registered for level 0
Oct 29 17:57:43 node-1 kernel: [    2.656408] md: raid1 personality registered for level 1
Oct 29 17:57:43 node-1 kernel: [    2.662751] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 29 17:57:43 node-1 kernel: [    2.669009] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 29 17:57:43 node-1 kernel: [    2.675420] hidraw: raw HID events driver (C) Jiri Kosina
Oct 29 17:57:43 node-1 kernel: [    2.680741] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct 29 17:57:43 node-1 kernel: [    2.680755] 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 29 17:57:43 node-1 kernel: [    2.680759] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 29 17:57:43 node-1 kernel: [    2.681294] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.681475] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.681643] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.681692] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.682008] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.686176] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 29 17:57:43 node-1 kernel: [    2.688135] megasas: FW now in Ready state
Oct 29 17:57:43 node-1 kernel: [    2.688360] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.688478] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.688602] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.688732] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.688863] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.688960] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.689067] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.689549] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.689731] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.689837] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.689957] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.690086] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.690198] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.690349] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.690465] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.690565] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.691913] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 29 17:57:43 node-1 kernel: [    2.700415] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct 29 17:57:43 node-1 kernel: [    2.700416] 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 29 17:57:43 node-1 kernel: [    2.700417] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 29 17:57:43 node-1 kernel: [    2.700870] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.701002] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.701132] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.701279] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.701391] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.701502] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.701914] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.718859] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct 29 17:57:43 node-1 kernel: [    2.718860] 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 29 17:57:43 node-1 kernel: [    2.718885] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 29 17:57:43 node-1 kernel: [    2.719615] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.719780] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.719897] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.719996] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.720191] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.733037] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct 29 17:57:43 node-1 kernel: [    2.733058] 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 29 17:57:43 node-1 kernel: [    2.733059] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 29 17:57:43 node-1 kernel: [    2.733293] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.733384] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.733604] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.733702] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.734159] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 29 17:57:43 node-1 kernel: [    2.898701] Switched to clocksource tsc
Oct 29 17:57:43 node-1 kernel: [    2.908533] usbcore: registered new interface driver usbhid
Oct 29 17:57:43 node-1 kernel: [    2.915334] usbhid: USB HID core driver
Oct 29 17:57:43 node-1 kernel: [    2.923132] 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 29 17:57:43 node-1 kernel: [    2.937155] 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 29 17:57:43 node-1 kernel: [    2.951460] 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 29 17:57:43 node-1 kernel: [    2.965780] 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 29 17:57:43 node-1 kernel: [    2.971001] raid6: sse2x1    3384 MB/s
Oct 29 17:57:43 node-1 kernel: [    2.987352] 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 29 17:57:43 node-1 kernel: [    3.001945] 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 29 17:57:43 node-1 kernel: [    3.038818] megasas:IOC Init cmd success
Oct 29 17:57:43 node-1 kernel: [    3.038820] raid6: sse2x2    5500 MB/s
Oct 29 17:57:43 node-1 kernel: [    3.074794] megasas: INIT adapter done
Oct 29 17:57:43 node-1 kernel: [    3.106775] raid6: sse2x4   16835 MB/s
Oct 29 17:57:43 node-1 kernel: [    3.150724] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 29 17:57:43 node-1 kernel: [    3.157787] scsi0 : LSI SAS based MegaRAID driver
Oct 29 17:57:43 node-1 kernel: [    3.165342] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 29 17:57:43 node-1 kernel: [    3.178713] raid6: avx2x1   22342 MB/s
Oct 29 17:57:43 node-1 kernel: [    3.190658] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 29 17:57:43 node-1 kernel: [    3.206243] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 29 17:57:43 node-1 kernel: [    3.213004] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 29 17:57:43 node-1 kernel: [    3.226632] sd 0:2:0:0: [sda] Write Protect is off
Oct 29 17:57:43 node-1 kernel: [    3.233417] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 29 17:57:43 node-1 kernel: [    3.233436] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 29 17:57:43 node-1 kernel: [    3.246659] raid6: avx2x2   26008 MB/s
Oct 29 17:57:43 node-1 kernel: [    3.285257]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 29 17:57:43 node-1 kernel: [    3.292234] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 29 17:57:43 node-1 kernel: [    3.314602] raid6: avx2x4   30625 MB/s
Oct 29 17:57:43 node-1 kernel: [    3.320921] raid6: using algorithm avx2x4 (30625 MB/s)
Oct 29 17:57:43 node-1 kernel: [    3.327146] raid6: using avx2x2 recovery algorithm
Oct 29 17:57:43 node-1 kernel: [    3.333984] xor: automatically using best checksumming function:
Oct 29 17:57:43 node-1 kernel: [    3.378527]    avx       : 35594.000 MB/sec
Oct 29 17:57:43 node-1 kernel: [    3.385066] async_tx: api initialized (async)
Oct 29 17:57:43 node-1 kernel: [    3.394781] md: raid6 personality registered for level 6
Oct 29 17:57:43 node-1 kernel: [    3.400534] md: raid5 personality registered for level 5
Oct 29 17:57:43 node-1 kernel: [    3.406045] md: raid4 personality registered for level 4
Oct 29 17:57:43 node-1 kernel: [    3.414404] md: raid10 personality registered for level 10
Oct 29 17:57:43 node-1 kernel: [    3.419692] random: lvm urandom read with 28 bits of entropy available
Oct 29 17:57:43 node-1 kernel: [    3.466337] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Oct 29 17:57:43 node-1 kernel: [    3.601335] bio: create slab <bio-1> at 1
Oct 29 17:57:43 node-1 kernel: [    4.353323] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 29 17:57:43 node-1 kernel: [    4.893889] init: plymouth-upstart-bridge main process (554) terminated with status 1
Oct 29 17:57:43 node-1 kernel: [    4.905805] init: plymouth-upstart-bridge main process ended, respawning
Oct 29 17:57:43 node-1 kernel: [    5.024278] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 29 17:57:43 node-1 kernel: [    5.057839] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 29 17:57:43 node-1 kernel: [    5.243016] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 29 17:57:43 node-1 kernel: [    5.314852] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 29 17:57:43 node-1 kernel: [    5.383996] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 29 17:57:43 node-1 kernel: [    5.533937] random: nonblocking pool is initialized
Oct 29 17:57:43 node-1 kernel: [    5.570833] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 29 17:57:43 node-1 kernel: [    5.605188] XFS (dm-0): Mounting Filesystem
Oct 29 17:57:43 node-1 kernel: [    5.784799] XFS (dm-0): Ending clean mount
Oct 29 17:57:43 node-1 kernel: [    5.863256] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 29 17:57:43 node-1 kernel: [    5.908128] XFS (dm-1): Mounting Filesystem
Oct 29 17:57:43 node-1 kernel: [    6.027272] XFS (dm-1): Ending clean mount
Oct 29 17:57:43 node-1 kernel: [    7.809772] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 29 17:57:43 node-1 kernel: [    7.823631] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 29 17:57:43 node-1 kernel: [    8.024273] systemd-udevd[780]: starting version 204
Oct 29 17:57:43 node-1 kernel: [    8.261723] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 29 17:57:43 node-1 kernel: [    8.264034] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 29 17:57:43 node-1 kernel: [    8.264039] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 29 17:57:43 node-1 kernel: [    8.264042] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 29 17:57:43 node-1 kernel: [    8.264044] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 29 17:57:43 node-1 kernel: [    8.264069] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 29 17:57:43 node-1 kernel: [    8.265967] power_meter ACPI000D:00: Found ACPI power meter.
Oct 29 17:57:43 node-1 kernel: [    8.265995] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 29 17:57:43 node-1 kernel: [    8.273095] wmi: Mapper loaded
Oct 29 17:57:43 node-1 kernel: [    8.282848] IPMI System Interface driver.
Oct 29 17:57:43 node-1 kernel: [    8.282929] ipmi_si: probing via ACPI
Oct 29 17:57:43 node-1 kernel: [    8.282944] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 29 17:57:43 node-1 kernel: [    8.282945] ipmi_si: Adding ACPI-specified kcs state machine
Oct 29 17:57:43 node-1 kernel: [    8.282961] ipmi_si: probing via SMBIOS
Oct 29 17:57:43 node-1 kernel: [    8.282963] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 29 17:57:43 node-1 kernel: [    8.282963] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 29 17:57:43 node-1 kernel: [    8.282966] ipmi_si: probing via SPMI
Oct 29 17:57:43 node-1 kernel: [    8.282967] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 29 17:57:43 node-1 kernel: [    8.282968] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 29 17:57:43 node-1 kernel: [    8.282970] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 29 17:57:43 node-1 kernel: [    8.346829] systemd-udevd[822]: renamed network interface eth1 to enp7s0
Oct 29 17:57:43 node-1 kernel: [    8.374703] systemd-udevd[815]: renamed network interface eth0 to enp6s0
Oct 29 17:57:43 node-1 kernel: [    8.434803] systemd-udevd[810]: renamed network interface eth2 to enp8s0
Oct 29 17:57:43 node-1 kernel: [    8.441010] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 29 17:57:43 node-1 kernel: [    8.441014] ipmi_si 00:09: IPMI kcs interface initialized
Oct 29 17:57:43 node-1 kernel: [    8.478600] systemd-udevd[813]: renamed network interface eth3 to enp9s0
Oct 29 17:57:43 node-1 kernel: [    8.726291] type=1400 audit(1477763835.724:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1044 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.726448] type=1400 audit(1477763835.724:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1044 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.726575] type=1400 audit(1477763835.724:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1044 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.737016] type=1400 audit(1477763835.732:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1066 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.737159] type=1400 audit(1477763835.732:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1066 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.737282] type=1400 audit(1477763835.732:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1066 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.740879] type=1400 audit(1477763835.736:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1042 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.741109] type=1400 audit(1477763835.736:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1042 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.741308] type=1400 audit(1477763835.736:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1042 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    8.761505] type=1400 audit(1477763835.756:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1043 comm="apparmor_parser"
Oct 29 17:57:43 node-1 kernel: [    9.295490] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 29 17:57:43 node-1 kernel: [    9.296349] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 29 17:57:43 node-1 kernel: [    9.524420] enic 0000:06:00.0 enp6s0: Link UP
Oct 29 17:57:43 node-1 kernel: [    9.525638] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 29 17:57:43 node-1 kernel: [    9.525644] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 29 17:57:43 node-1 kernel: [   19.246111] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 29 17:57:44 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 29 17:57:44 node-1 kernel: [   37.972879] init: failsafe main process (8424) killed by TERM signal
Oct 29 17:57:45 node-1 dbus[8475]: [system] AppArmor D-Bus mediation is enabled
Oct 29 17:57:45 node-1 kernel: [   38.203815] audit_printk_skb: 30 callbacks suppressed
Oct 29 17:57:45 node-1 kernel: [   38.203816] type=1400 audit(1477763865.134:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8551 comm="apparmor_parser"
Oct 29 17:57:45 node-1 kernel: [   38.203820] type=1400 audit(1477763865.134:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8551 comm="apparmor_parser"
Oct 29 17:57:45 node-1 kernel: [   38.203822] type=1400 audit(1477763865.134:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Oct 29 17:57:45 node-1 kernel: [   38.204057] type=1400 audit(1477763865.134:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8551 comm="apparmor_parser"
Oct 29 17:57:45 node-1 kernel: [   38.204058] type=1400 audit(1477763865.134:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Oct 29 17:57:45 node-1 kernel: [   38.204184] type=1400 audit(1477763865.134:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8551 comm="apparmor_parser"
Oct 29 17:57:45 node-1 kernel: [   38.205433] type=1400 audit(1477763865.138:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8552 comm="apparmor_parser"
Oct 29 17:57:45 node-1 kernel: [   38.271987] type=1400 audit(1477763865.202:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8554 comm="apparmor_parser"
Oct 29 17:57:45 node-1 cron[8581]: (CRON) INFO (pidfile fd = 3)
Oct 29 17:57:45 node-1 anacron[8600]: Anacron 2.3 started on 2016-10-29
Oct 29 17:57:45 node-1 cron[8605]: (CRON) STARTUP (fork ok)
Oct 29 17:57:45 node-1 anacron[8600]: Will run job `cron.daily' in 5 min.
Oct 29 17:57:45 node-1 anacron[8600]: Will run job `cron.weekly' in 10 min.
Oct 29 17:57:45 node-1 anacron[8600]: Will run job `cron.monthly' in 15 min.
Oct 29 17:57:45 node-1 anacron[8600]: Jobs will be executed sequentially
Oct 29 17:57:45 node-1 cron[8605]: (CRON) INFO (Running @reboot jobs)
Oct 29 17:57:45 node-1 multipathd: path checkers start up
Oct 29 17:57:45 node-1 postfix/master[8761]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 29 17:57:49 node-1 puppet-agent[8945]: Reopening log files
Oct 29 17:57:50 node-1 puppet-agent[8945]: Could not request certificate: Connection refused - connect(2)
Oct 29 17:58:01 node-1 CRON[9117]: (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 29 17:58:02 node-1 puppet-user[9164]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 29 17:58:02 node-1 puppet-user[9164]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 29 17:58:03 node-1 puppet-user[9164]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 29 17:58:03 node-1 puppet-user[9164]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 29 17:58:04 node-1 puppet-user[9164]: Finished catalog run in 1.08 seconds
Oct 29 17:58:05 node-1 multipathd: uevent trigger error
Oct 29 17:58:05 node-1 puppet-user[9589]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 29 17:58:05 node-1 puppet-user[9589]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 29 17:58:05 node-1 puppet-user[9589]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 29 17:58:05 node-1 puppet-user[9589]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 29 17:58:05 node-1 puppet-user[9589]: (/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 29 17:58:05 node-1 puppet-user[9589]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 29 17:58:05 node-1 puppet-user[9589]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 29 17:58:05 node-1 puppet-user[9589]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 29 17:58:05 node-1 puppet-user[9589]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 29 17:58:05 node-1 puppet-user[9589]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 29 17:58:05 node-1 puppet-user[9589]: Finished catalog run in 0.05 seconds
Oct 29 17:58:06 node-1 puppet-user[10046]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 29 17:58:06 node-1 puppet-user[10046]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 29 17:58:06 node-1 puppet-user[10046]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 29 17:58:06 node-1 puppet-user[10046]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 29 17:58:06 node-1 puppet-user[10046]: Finished catalog run in 0.03 seconds
Oct 29 17:58:08 node-1 puppet-user[10684]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 29 17:58:08 node-1 puppet-user[10684]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 29 17:58:08 node-1 puppet-user[10684]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 29 17:58:08 node-1 puppet-user[10684]: Finished catalog run in 0.05 seconds
Oct 29 17:58:09 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 17:58:09 node-1 nailgun-agent: D, [2016-10-29T17:58:01.621453 #9120] DEBUG -- : Sleep for 8 seconds before sending request
Oct 29 17:58:09 node-1 nailgun-agent: I, [2016-10-29T17:58:09.636274 #9120]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 29 17:58:09 node-1 puppet-user[11126]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 29 17:58:09 node-1 puppet-user[11126]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Oct 29 17:58:09 node-1 puppet-user[11126]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 29 17:58:10 node-1 nailgun-agent: D, [2016-10-29T17:58:10.019423 #9120] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 29 17:58:10 node-1 puppet-user[11126]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Oct 29 17:58:10 node-1 puppet-user[11126]: Finished catalog run in 0.52 seconds
Oct 29 17:58:11 node-1 puppet-user[11725]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 29 17:58:11 node-1 puppet-user[11725]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Oct 29 17:58:12 node-1 puppet-user[11725]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 29 17:58:12 node-1 puppet-user[11725]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 29 17:58:12 node-1 puppet-user[11725]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Oct 29 17:58:12 node-1 puppet-user[11725]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 29 17:58:12 node-1 puppet-user[11725]: Finished catalog run in 0.23 seconds
Oct 29 17:58:13 node-1 puppet-user[12208]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 29 17:58:13 node-1 puppet-user[12208]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Oct 29 17:58:14 node-1 puppet-user[12208]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 29 17:58:14 node-1 kernel: [   67.186443] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 29 17:58:14 node-1 kernel: [   67.186494] 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 29 17:58:14 node-1 puppet-user[12208]: (/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 29 17:58:14 node-1 puppet-user[12208]: Finished catalog run in 0.06 seconds
Oct 29 17:58:15 node-1 puppet-user[12665]: (Scope(Class[main])) MODULAR: sync_time
Oct 29 17:58:15 node-1 puppet-user[12665]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 29 17:58:16 node-1 ntpdate[13076]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 29 17:58:18 node-1 kernel: [   71.802243] init: plymouth-upstart-bridge main process ended, respawning
Oct 29 17:58:18 node-1 puppet-agent[8945]: Could not run: SIGTERM
Oct 29 17:58:19 node-1 kernel: [   72.046145] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 29 17:58:19 node-1 ec2: 
Oct 29 17:58:19 node-1 ec2: #############################################################
Oct 29 17:58:19 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 29 17:58:19 node-1 ec2: 1024 e0:8d:97:60:43:a4:39:f5:66:72:b9:3a:2b:66:c2:d8  root@node-1.domain.tld (DSA)
Oct 29 17:58:19 node-1 ec2: 256 be:55:57:a5:56:3c:3d:85:ad:fe:dd:89:34:0f:1d:51  root@node-1.domain.tld (ECDSA)
Oct 29 17:58:19 node-1 ec2: 256 5a:a8:d9:70:cf:39:ff:3c:36:2d:08:f1:9c:91:c4:74  root@node-1.domain.tld (ED25519)
Oct 29 17:58:19 node-1 ec2: 2048 b2:6c:81:29:d0:93:72:36:9a:a0:ab:37:c4:d2:ab:be  root@node-1.domain.tld (RSA)
Oct 29 17:58:19 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 29 17:58:19 node-1 ec2: #############################################################
Oct 29 17:58:22 node-1 ntpdate[13076]: adjust time server 10.20.0.2 offset 0.042411 sec
Oct 29 17:58:22 node-1 puppet-user[12665]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 29 17:58:22 node-1 puppet-user[12665]: Finished catalog run in 6.20 seconds
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.197474 #9120] DEBUG -- : Trying to find block devices
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.197597 #9120] DEBUG -- : Found block device: sda
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.197645 #9120] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.197667 #9120] DEBUG -- : Trying to get list of physical devices
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.197843 #9120] DEBUG -- : Getting udev properties for device: sda
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.199775 #9120] 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 29 17:58:22 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45463", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.199844 #9120] DEBUG -- : Trying to find out if device sda is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.199890 #9120] DEBUG -- : Device sda removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.199906 #9120] DEBUG -- : Device sda seems to be appropriate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.200336 #9120] DEBUG -- : Getting udev properties for device: dm-0
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.201996 #9120] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-AlxP7vj3ikdm3uUL2xXiOPsVekyUrejAxFnnRW3yTuPPsoUj0STRj2b1jezPAmv0 /dev/disk/by-uuid/0c04734c-7f8e-4161-a454-47c362c392bd /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-AlxP7vj3ikdm3uUL2xXiOPsVekyUrejAxFnnRW3yTuPPsoUj0STRj2b1jezPAmv0", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0c04734c-7f8e-4161-a454-47c362c392bd", "ID_FS_UUID_ENC"=>"0c04734c-7f8e-4161-a454-47c362c392bd", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54916", "nomdmonddf"=>"1", "nomd
Oct 29 17:58:22 node-1 nailgun-agent: monisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.202033 #9120] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.202063 #9120] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.202077 #9120] DEBUG -- : Device dm-0 seems to be appropriate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.202093 #9120] DEBUG -- : Getting udev properties for device: dm-1
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.203839 #9120] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-CbLFRSsdfuwSWtLlEPLY0AaSjaQflSTaqjtMP2P8h9Cn4DedFaJND3h4EzcSuskz /dev/disk/by-uuid/6eee3efd-f3a0-4732-b63b-89e8db8e0482 /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-CbLFRSsdfuwSWtLlEPLY0AaSjaQflSTaqjtMP2P8h9Cn4DedFaJND3h4EzcSuskz", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6eee3efd-f3a0-4732-b63b-89e8db8e0482", "ID_FS_UUID_ENC"=>"6eee3efd-f3a0-4732-b63b-89e8db8e0482", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82
Oct 29 17:58:22 node-1 nailgun-agent: 593", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.203897 #9120] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.203928 #9120] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.203942 #9120] DEBUG -- : Device dm-1 seems to be appropriate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.203959 #9120] DEBUG -- : Getting udev properties for device: dm-2
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.205846 #9120] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-0NS42Pntzmvzq2RHgIR7XlmSNfm1NDwBCHjoDlYvx6cGXTEzKEHFTDvH3JUalDTr /dev/disk/by-uuid/0e720ac5-ccbe-4a62-9b4f-040709c4e120 /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-0NS42Pntzmvzq2RHgIR7XlmSNfm1NDwBCHjoDlYvx6cGXTEzKEHFTDvH3JUalDTr", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0e720ac5-ccbe-4a62-9b4f-040709c4e120", "ID_FS_UUID_ENC"=>"0e720ac5-ccbe-4a62-9b4f-040709c4e120", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84122", "nomdmond
Oct 29 17:58:22 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.205878 #9120] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.205932 #9120] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.205962 #9120] DEBUG -- : Device dm-2 seems to be appropriate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.205977 #9120] DEBUG -- : Getting udev properties for device: dm-3
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.207735 #9120] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-oRbSxBV78nk30uBHlx5Kebt9MCCu3RlCarfqj9oAdgkbsrRSdWNCQNgDuYtau1PV /dev/disk/by-uuid/ac6688f0-af3a-42fd-8feb-ea2ae42f8436 /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-oRbSxBV78nk30uBHlx5Kebt9MCCu3RlCarfqj9oAdgkbsrRSdWNCQNgDuYtau1PV", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ac6688f0-af3a-42fd-8feb-ea2ae42f8436", "ID_FS_UUID_ENC"=>"ac6688f0-af3a-42fd-8feb-ea2ae42f8436", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95391", "nomdmonddf"=>"1", 
Oct 29 17:58:22 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.207761 #9120] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.207804 #9120] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.207819 #9120] DEBUG -- : Device dm-3 seems to be appropriate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.207835 #9120] DEBUG -- : Getting udev properties for device: dm-4
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.209491 #9120] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-gH7eNzVmKE9tmp2G1xhNiqzHJeR18JHAGV2pO5bOIHiLjpC0z5hq4dakcxyhPHQp /dev/disk/by-uuid/d9465518-5722-4d2c-aa4f-f39d0569fd5b /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-gH7eNzVmKE9tmp2G1xhNiqzHJeR18JHAGV2pO5bOIHiLjpC0z5hq4dakcxyhPHQp", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d9465518-5722-4d2c-aa4f-f39d0569fd5b", "ID_FS_UUID_ENC"=>"d9465518-5722-4d2c-aa4f-f39d0569fd5b", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3750", "nomdmonddf"=>"1", "nomdm
Oct 29 17:58:22 node-1 nailgun-agent: onisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.209517 #9120] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.209563 #9120] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.209577 #9120] DEBUG -- : Device dm-4 seems to be appropriate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.209593 #9120] DEBUG -- : Getting udev properties for device: dm-5
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.211206 #9120] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-gH7eNzVmKE9tmp2G1xhNiqzHJeR18JHA5TpWWcRvaOfWrh5GLcuzITr9HPXEAUtJ /dev/disk/by-uuid/92ac3d43-5a34-48c7-91c4-ebdc3f2206f7 /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-gH7eNzVmKE9tmp2G1xhNiqzHJeR18JHA5TpWWcRvaOfWrh5GLcuzITr9HPXEAUtJ", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"92ac3d43-5a34-48c7-91c4-ebdc3f2206f7", "ID_FS_UUID_ENC"=>"92ac3d43-5a34-48c7-91c4-ebdc3f2206f7", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4170", "nomdmonddf"=>"1", "nomdmonisw"=
Oct 29 17:58:22 node-1 nailgun-agent: >"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.211231 #9120] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.211278 #9120] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.211335 #9120] DEBUG -- : Device dm-5 seems to be appropriate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.211351 #9120] DEBUG -- : Getting udev properties for device: ram0
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.212955 #9120] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83077", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.212979 #9120] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.213012 #9120] DEBUG -- : Device ram0 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.213047 #9120] DEBUG -- : Getting udev properties for device: ram1
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.214602 #9120] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83179", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.214627 #9120] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.214690 #9120] DEBUG -- : Device ram1 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.214711 #9120] DEBUG -- : Getting udev properties for device: ram2
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.216272 #9120] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83547", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.216340 #9120] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.216384 #9120] DEBUG -- : Device ram2 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.216405 #9120] DEBUG -- : Getting udev properties for device: ram3
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.217897 #9120] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83599", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.217923 #9120] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.217958 #9120] DEBUG -- : Device ram3 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.217993 #9120] DEBUG -- : Getting udev properties for device: ram4
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.219475 #9120] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83651", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.219500 #9120] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.219535 #9120] DEBUG -- : Device ram4 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.219556 #9120] DEBUG -- : Getting udev properties for device: ram5
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.221030 #9120] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83699", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.221056 #9120] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.221089 #9120] DEBUG -- : Device ram5 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.221146 #9120] DEBUG -- : Getting udev properties for device: ram6
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.222825 #9120] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83757", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.222850 #9120] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.222908 #9120] DEBUG -- : Device ram6 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.222928 #9120] DEBUG -- : Getting udev properties for device: ram7
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.224619 #9120] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83809", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.224643 #9120] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.224679 #9120] DEBUG -- : Device ram7 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.224700 #9120] DEBUG -- : Getting udev properties for device: ram8
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.226323 #9120] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83856", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.226348 #9120] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.226381 #9120] DEBUG -- : Device ram8 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.226402 #9120] DEBUG -- : Getting udev properties for device: ram9
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.228058 #9120] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83906", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.228089 #9120] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.228146 #9120] DEBUG -- : Device ram9 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.228181 #9120] DEBUG -- : Getting udev properties for device: loop0
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.230112 #9120] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82426", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.230153 #9120] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.230189 #9120] DEBUG -- : Device loop0 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.230209 #9120] DEBUG -- : Getting udev properties for device: loop1
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.231650 #9120] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82495", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.231679 #9120] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.231721 #9120] DEBUG -- : Device loop1 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.231742 #9120] DEBUG -- : Getting udev properties for device: loop2
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.233226 #9120] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82591", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.233250 #9120] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.233284 #9120] DEBUG -- : Device loop2 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.233334 #9120] DEBUG -- : Getting udev properties for device: loop3
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.234794 #9120] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82685", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.234820 #9120] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.234856 #9120] DEBUG -- : Device loop3 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.234876 #9120] DEBUG -- : Getting udev properties for device: loop4
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.236694 #9120] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82748", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.236719 #9120] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.236757 #9120] DEBUG -- : Device loop4 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.236798 #9120] DEBUG -- : Getting udev properties for device: loop5
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.238260 #9120] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82823", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.238285 #9120] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.238318 #9120] DEBUG -- : Device loop5 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.238338 #9120] DEBUG -- : Getting udev properties for device: loop6
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.239799 #9120] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82885", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.239834 #9120] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.239867 #9120] DEBUG -- : Device loop6 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.239895 #9120] DEBUG -- : Getting udev properties for device: loop7
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.241352 #9120] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82985", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.241377 #9120] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.241410 #9120] DEBUG -- : Device loop7 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.241455 #9120] DEBUG -- : Getting udev properties for device: ram10
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.242915 #9120] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83232", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.242948 #9120] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.242991 #9120] DEBUG -- : Device ram10 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.243011 #9120] DEBUG -- : Getting udev properties for device: ram11
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.244531 #9120] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83289", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.244556 #9120] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.244595 #9120] DEBUG -- : Device ram11 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.244616 #9120] DEBUG -- : Getting udev properties for device: ram12
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.246060 #9120] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83341", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.246085 #9120] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.246137 #9120] DEBUG -- : Device ram12 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.246158 #9120] DEBUG -- : Getting udev properties for device: ram13
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.247611 #9120] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83394", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.247651 #9120] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.247693 #9120] DEBUG -- : Device ram13 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.247715 #9120] DEBUG -- : Getting udev properties for device: ram14
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.249187 #9120] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83447", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.249212 #9120] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.249261 #9120] DEBUG -- : Device ram14 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.249282 #9120] DEBUG -- : Getting udev properties for device: ram15
Oct 29 17:58:22 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251453 #9120] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83496", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251489 #9120] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251541 #9120] DEBUG -- : Device ram15 removable parameter: "0"
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251589 #9120] 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 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251622 #9120] DEBUG -- : Block device seems to be physical data storage: sda
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251654 #9120] DEBUG -- : Found block device: dm-0
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251696 #9120] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251709 #9120] DEBUG -- : Found block device: dm-1
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251720 #9120] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251765 #9120] DEBUG -- : Found block device: dm-2
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251777 #9120] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251803 #9120] DEBUG -- : Found block device: dm-3
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251813 #9120] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251822 #9120] DEBUG -- : Found block device: dm-4
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251844 #9120] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251870 #9120] DEBUG -- : Found block device: dm-5
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251881 #9120] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251891 #9120] DEBUG -- : Found block device: ram0
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251914 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251933 #9120] DEBUG -- : Found block device: ram1
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251968 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251978 #9120] DEBUG -- : Found block device: ram2
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.251988 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252011 #9120] DEBUG -- : Found block device: ram3
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252021 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252030 #9120] DEBUG -- : Found block device: ram4
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252058 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252066 #9120] DEBUG -- : Found block device: ram5
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252090 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252099 #9120] DEBUG -- : Found block device: ram6
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252127 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252136 #9120] DEBUG -- : Found block device: ram7
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252162 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252172 #9120] DEBUG -- : Found block device: ram8
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252181 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252203 #9120] DEBUG -- : Found block device: ram9
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252213 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252222 #9120] DEBUG -- : Found block device: loop0
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252240 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252262 #9120] DEBUG -- : Found block device: loop1
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252285 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252294 #9120] DEBUG -- : Found block device: loop2
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252303 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252311 #9120] DEBUG -- : Found block device: loop3
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252332 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.252348 #9120] DEBUG -- : Found block device: loop4
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256773 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256787 #9120] DEBUG -- : Found block device: loop5
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256800 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256809 #9120] DEBUG -- : Found block device: loop6
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256818 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256826 #9120] DEBUG -- : Found block device: loop7
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256835 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256843 #9120] DEBUG -- : Found block device: ram10
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256853 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256898 #9120] DEBUG -- : Found block device: ram11
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256907 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256915 #9120] DEBUG -- : Found block device: ram12
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256924 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256932 #9120] DEBUG -- : Found block device: ram13
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256941 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256948 #9120] DEBUG -- : Found block device: ram14
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256957 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256965 #9120] DEBUG -- : Found block device: ram15
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.256974 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.257034 #9120] 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 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.334332 #9120] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 29 17:58:22 node-1 nailgun-agent: D, [2016-10-29T17:58:22.334373 #9120] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 29 17:58:27 node-1 puppet-user[13624]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 29 17:58:27 node-1 puppet-user[13624]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 29 17:58:27 node-1 puppet-user[13624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 29 17:58:27 node-1 puppet-user[13624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Oct 29 17:58:27 node-1 puppet-user[13624]: Finished catalog run in 0.08 seconds
Oct 29 17:58:28 node-1 puppet-user[14082]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 29 17:58:28 node-1 puppet-user[14082]: Compiled catalog for node-1.domain.tld in environment production in 0.45 seconds
Oct 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/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 29 17:58:29 node-1 puppet-user[14082]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 29 17:58:29 node-1 puppet-user[14082]: Finished catalog run in 0.82 seconds
Oct 29 17:58:31 node-1 puppet-user[14573]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 29 17:58:31 node-1 puppet-user[14573]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct 29 17:58:34 node-1 puppet-user[14573]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 29 17:58:34 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367268 #9120] DEBUG -- : Trying to find block devices
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367378 #9120] DEBUG -- : Found block device: sda
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367413 #9120] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367435 #9120] DEBUG -- : Block device seems to be physical data storage: sda
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367461 #9120] DEBUG -- : Found block device: dm-0
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367477 #9120] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367491 #9120] DEBUG -- : Found block device: dm-1
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367504 #9120] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367514 #9120] DEBUG -- : Found block device: dm-2
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367581 #9120] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367592 #9120] DEBUG -- : Found block device: dm-3
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367603 #9120] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367613 #9120] DEBUG -- : Found block device: dm-4
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367624 #9120] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367633 #9120] DEBUG -- : Found block device: dm-5
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367643 #9120] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367652 #9120] DEBUG -- : Found block device: ram0
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367696 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367708 #9120] DEBUG -- : Found block device: ram1
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367754 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367767 #9120] DEBUG -- : Found block device: ram2
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367778 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367788 #9120] DEBUG -- : Found block device: ram3
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367800 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367809 #9120] DEBUG -- : Found block device: ram4
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367819 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367828 #9120] DEBUG -- : Found block device: ram5
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367839 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367849 #9120] DEBUG -- : Found block device: ram6
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367859 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367912 #9120] DEBUG -- : Found block device: ram7
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367924 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367933 #9120] DEBUG -- : Found block device: ram8
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367944 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367953 #9120] DEBUG -- : Found block device: ram9
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367965 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367975 #9120] DEBUG -- : Found block device: loop0
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.367997 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368005 #9120] DEBUG -- : Found block device: loop1
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368015 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368025 #9120] DEBUG -- : Found block device: loop2
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368070 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368079 #9120] DEBUG -- : Found block device: loop3
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368090 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368099 #9120] DEBUG -- : Found block device: loop4
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368109 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368117 #9120] DEBUG -- : Found block device: loop5
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368128 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368137 #9120] DEBUG -- : Found block device: loop6
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368147 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368155 #9120] DEBUG -- : Found block device: loop7
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368197 #9120] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368207 #9120] DEBUG -- : Found block device: ram10
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368217 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368227 #9120] DEBUG -- : Found block device: ram11
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368237 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368245 #9120] DEBUG -- : Found block device: ram12
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368255 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368263 #9120] DEBUG -- : Found block device: ram13
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368274 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368282 #9120] DEBUG -- : Found block device: ram14
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368292 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368332 #9120] DEBUG -- : Found block device: ram15
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368344 #9120] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.368377 #9120] 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 29 17:58:34 node-1 nailgun-agent: D, [2016-10-29T17:58:34.538316 #9120] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 29 17:58:34 node-1 nailgun-agent: I, [2016-10-29T17:58:34.538569 #9120]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 29 17:59:01 node-1 puppet-user[14573]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 29 17:59:01 node-1 puppet-user[14573]: Finished catalog run in 29.73 seconds
Oct 29 17:59:01 node-1 CRON[17097]: (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 29 17:59:02 node-1 puppet-user[17094]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 29 17:59:03 node-1 puppet-user[17094]: Compiled catalog for node-1.domain.tld in environment production in 0.59 seconds
Oct 29 17:59:03 node-1 puppet-user[17094]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 29 17:59:03 node-1 puppet-user[17094]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 29 17:59:03 node-1 puppet-user[17094]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 29 17:59:03 node-1 puppet-user[17094]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 29 17:59:03 node-1 puppet-user[17094]: Finished catalog run in 0.10 seconds
Oct 29 17:59:05 node-1 puppet-user[17563]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 29 17:59:06 node-1 puppet-user[17563]: Compiled catalog for node-1.domain.tld in environment production in 0.87 seconds
Oct 29 17:59:06 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 29 17:59:06 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 29 17:59:06 node-1 crontab[17999]: (root) LIST (root)
Oct 29 17:59:06 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 29 17:59:06 node-1 crontab[18000]: (root) REPLACE (root)
Oct 29 17:59:08 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 29 17:59:08 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 29 17:59:08 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 29 17:59:08 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 29 17:59:09 node-1 puppet-user[17563]: (/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 29 17:59:09 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8397" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 29 17:59:09 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 29 17:59:12 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:12 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:12 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:12 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:12 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:23 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:23 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:23 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:23 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:23 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:26 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:26 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:26 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:26 node-1 multipathd: uevent trigger error
<27>Oct 29 17:59:26 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:21 node-1 ntpdate[28936]: no servers can be used, exiting
<27>Oct 29 18:00:21 node-1 ntpdate[29201]: no servers can be used, exiting
<27>Oct 29 18:00:52 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:52 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:52 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:56 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:56 node-1 multipathd: uevent trigger error
<27>Oct 29 18:00:56 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:01:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:14 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:14 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:14 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:14 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 18:02:16 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 18:02:22 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 18:02:22 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 18:02:28 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 18:02:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 18:02:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 29 18:02:41 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:41 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:41 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:41 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:41 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:02:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:03 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:05 node-1 haproxy[18262]: 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 29 18:03:06 node-1 haproxy[18268]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:07 node-1 haproxy[18268]: 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 29 18:03:07 node-1 haproxy[18268]: proxy mysqld has no server available!
<27>Oct 29 18:03:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:12 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:14 node-1 haproxy[20843]: 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 29 18:03:14 node-1 haproxy[20843]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:15 node-1 haproxy[20860]: 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 29 18:03:15 node-1 haproxy[20860]: proxy mysqld has no server available!
<129>Oct 29 18:03:15 node-1 haproxy[20860]: 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 29 18:03:15 node-1 haproxy[20860]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:16 node-1 haproxy[20860]: 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 29 18:03:16 node-1 haproxy[20860]: proxy object-storage has no server available!
<27>Oct 29 18:03:17 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:17 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:17 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:17 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:19 node-1 haproxy[22365]: 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 29 18:03:20 node-1 haproxy[22370]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:20 node-1 haproxy[22370]: 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 29 18:03:20 node-1 haproxy[22370]: proxy neutron has no server available!
<129>Oct 29 18:03:20 node-1 haproxy[22370]: 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 29 18:03:20 node-1 haproxy[22370]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:20 node-1 haproxy[22370]: 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 29 18:03:20 node-1 haproxy[22370]: proxy mysqld has no server available!
<129>Oct 29 18:03:21 node-1 haproxy[22370]: 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 29 18:03:21 node-1 haproxy[22370]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:21 node-1 haproxy[22370]: 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 29 18:03:21 node-1 haproxy[22370]: proxy object-storage has no server available!
<27>Oct 29 18:03:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:23 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:25 node-1 haproxy[23760]: 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 29 18:03:25 node-1 haproxy[23760]: Server keystone-1/node-3 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 29 18:03:25 node-1 haproxy[23760]: 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 29 18:03:25 node-1 haproxy[23760]: proxy keystone-1 has no server available!
<129>Oct 29 18:03:25 node-1 haproxy[23760]: 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 29 18:03:25 node-1 haproxy[23760]: Server keystone-2/node-3 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 29 18:03:26 node-1 haproxy[23764]: 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 29 18:03:26 node-1 haproxy[23764]: proxy keystone-2 has no server available!
<129>Oct 29 18:03:26 node-1 haproxy[23764]: 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 29 18:03:26 node-1 haproxy[23764]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:26 node-1 haproxy[23764]: 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 29 18:03:26 node-1 haproxy[23764]: proxy neutron has no server available!
<129>Oct 29 18:03:26 node-1 haproxy[23764]: 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 29 18:03:26 node-1 haproxy[23764]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:26 node-1 haproxy[23764]: 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 29 18:03:26 node-1 haproxy[23764]: proxy mysqld has no server available!
<129>Oct 29 18:03:27 node-1 haproxy[23764]: 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 29 18:03:27 node-1 haproxy[23764]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:27 node-1 haproxy[23764]: 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 29 18:03:27 node-1 haproxy[23764]: proxy object-storage has no server available!
<27>Oct 29 18:03:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:28 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:30 node-1 haproxy[25131]: 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 29 18:03:30 node-1 haproxy[25131]: Server keystone-1/node-3 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 29 18:03:30 node-1 haproxy[25131]: 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 29 18:03:30 node-1 haproxy[25131]: proxy keystone-1 has no server available!
<129>Oct 29 18:03:30 node-1 haproxy[25131]: 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 29 18:03:31 node-1 haproxy[25135]: Server keystone-2/node-3 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 29 18:03:31 node-1 haproxy[25135]: 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 29 18:03:31 node-1 haproxy[25135]: proxy keystone-2 has no server available!
<129>Oct 29 18:03:31 node-1 haproxy[25135]: 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 29 18:03:31 node-1 haproxy[25135]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:31 node-1 haproxy[25135]: 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 29 18:03:31 node-1 haproxy[25135]: proxy neutron has no server available!
<129>Oct 29 18:03:31 node-1 haproxy[25135]: 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 29 18:03:31 node-1 haproxy[25135]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:31 node-1 haproxy[25135]: 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 29 18:03:31 node-1 haproxy[25135]: proxy mysqld has no server available!
<129>Oct 29 18:03:31 node-1 haproxy[25135]: 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 29 18:03:32 node-1 haproxy[25135]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:32 node-1 haproxy[25135]: 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 29 18:03:32 node-1 haproxy[25135]: proxy object-storage has no server available!
<129>Oct 29 18:03:32 node-1 haproxy[25135]: 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 29 18:03:32 node-1 haproxy[25135]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:32 node-1 haproxy[25135]: 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 29 18:03:32 node-1 haproxy[25135]: proxy aodh has no server available!
<27>Oct 29 18:03:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:34 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:35 node-1 haproxy[26495]: 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 29 18:03:36 node-1 haproxy[26499]: Server keystone-1/node-3 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 29 18:03:36 node-1 haproxy[26499]: 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 29 18:03:36 node-1 haproxy[26499]: proxy keystone-1 has no server available!
<129>Oct 29 18:03:36 node-1 haproxy[26499]: 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 29 18:03:36 node-1 haproxy[26499]: Server keystone-2/node-3 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 29 18:03:36 node-1 haproxy[26499]: 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 29 18:03:36 node-1 haproxy[26499]: proxy keystone-2 has no server available!
<129>Oct 29 18:03:36 node-1 haproxy[26499]: 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 29 18:03:36 node-1 haproxy[26499]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:36 node-1 haproxy[26499]: 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 29 18:03:36 node-1 haproxy[26499]: proxy neutron has no server available!
<129>Oct 29 18:03:36 node-1 haproxy[26499]: 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 29 18:03:36 node-1 haproxy[26499]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:37 node-1 haproxy[26499]: 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 29 18:03:37 node-1 haproxy[26499]: proxy mysqld has no server available!
<129>Oct 29 18:03:37 node-1 haproxy[26499]: 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 29 18:03:37 node-1 haproxy[26499]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:37 node-1 haproxy[26499]: 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 29 18:03:37 node-1 haproxy[26499]: proxy object-storage has no server available!
<129>Oct 29 18:03:37 node-1 haproxy[26499]: 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 29 18:03:37 node-1 haproxy[26499]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:37 node-1 haproxy[26499]: 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 29 18:03:37 node-1 haproxy[26499]: proxy aodh has no server available!
<129>Oct 29 18:03:37 node-1 haproxy[26499]: 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 29 18:03:37 node-1 haproxy[26499]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:37 node-1 haproxy[26499]: 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 29 18:03:37 node-1 haproxy[26499]: proxy ceilometer has no server available!
<27>Oct 29 18:03:39 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:39 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:39 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:39 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:41 node-1 haproxy[27844]: 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 29 18:03:41 node-1 haproxy[27844]: Server keystone-1/node-3 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 29 18:03:41 node-1 haproxy[27844]: 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 29 18:03:41 node-1 haproxy[27844]: proxy keystone-1 has no server available!
<129>Oct 29 18:03:41 node-1 haproxy[27844]: 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 29 18:03:41 node-1 haproxy[27844]: Server keystone-2/node-3 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 29 18:03:41 node-1 haproxy[27844]: 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 29 18:03:41 node-1 haproxy[27844]: proxy keystone-2 has no server available!
<129>Oct 29 18:03:41 node-1 haproxy[27844]: 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 29 18:03:42 node-1 haproxy[27848]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:42 node-1 haproxy[27848]: 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 29 18:03:42 node-1 haproxy[27848]: proxy neutron has no server available!
<129>Oct 29 18:03:42 node-1 haproxy[27848]: 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 29 18:03:42 node-1 haproxy[27848]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:42 node-1 haproxy[27848]: 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 29 18:03:42 node-1 haproxy[27848]: proxy mysqld has no server available!
<129>Oct 29 18:03:42 node-1 haproxy[27848]: 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 29 18:03:42 node-1 haproxy[27848]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:42 node-1 haproxy[27848]: 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 29 18:03:42 node-1 haproxy[27848]: proxy object-storage has no server available!
<129>Oct 29 18:03:42 node-1 haproxy[27848]: 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 29 18:03:42 node-1 haproxy[27848]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:43 node-1 haproxy[27848]: 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 29 18:03:43 node-1 haproxy[27848]: proxy aodh has no server available!
<129>Oct 29 18:03:43 node-1 haproxy[27848]: 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 29 18:03:43 node-1 haproxy[27848]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:43 node-1 haproxy[27848]: 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 29 18:03:43 node-1 haproxy[27848]: proxy ceilometer has no server available!
<27>Oct 29 18:03:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:44 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:46 node-1 haproxy[29160]: 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 29 18:03:46 node-1 haproxy[29160]: 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 29 18:03:47 node-1 haproxy[29167]: Server keystone-1/node-3 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 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:47 node-1 haproxy[29167]: proxy keystone-1 has no server available!
<129>Oct 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:47 node-1 haproxy[29167]: Server keystone-2/node-3 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 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:47 node-1 haproxy[29167]: proxy keystone-2 has no server available!
<129>Oct 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:47 node-1 haproxy[29167]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:47 node-1 haproxy[29167]: proxy neutron has no server available!
<129>Oct 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:47 node-1 haproxy[29167]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:47 node-1 haproxy[29167]: proxy mysqld has no server available!
<129>Oct 29 18:03:47 node-1 haproxy[29167]: 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 29 18:03:48 node-1 haproxy[29167]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:48 node-1 haproxy[29167]: 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 29 18:03:48 node-1 haproxy[29167]: proxy object-storage has no server available!
<129>Oct 29 18:03:48 node-1 haproxy[29167]: 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 29 18:03:48 node-1 haproxy[29167]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:48 node-1 haproxy[29167]: 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 29 18:03:48 node-1 haproxy[29167]: proxy aodh has no server available!
<129>Oct 29 18:03:48 node-1 haproxy[29167]: 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 29 18:03:48 node-1 haproxy[29167]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:48 node-1 haproxy[29167]: 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 29 18:03:48 node-1 haproxy[29167]: proxy ceilometer has no server available!
<27>Oct 29 18:03:49 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:49 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:49 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:49 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:52 node-1 haproxy[30554]: 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 29 18:03:52 node-1 haproxy[30554]: 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 29 18:03:52 node-1 haproxy[30554]: Server keystone-1/node-3 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 29 18:03:52 node-1 haproxy[30554]: 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 29 18:03:52 node-1 haproxy[30554]: proxy keystone-1 has no server available!
<129>Oct 29 18:03:52 node-1 haproxy[30554]: 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 29 18:03:52 node-1 haproxy[30554]: Server keystone-2/node-3 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 29 18:03:52 node-1 haproxy[30554]: 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 29 18:03:52 node-1 haproxy[30554]: proxy keystone-2 has no server available!
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: proxy glance-api has no server available!
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: proxy glance-glare has no server available!
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: proxy neutron has no server available!
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: proxy glance-registry has no server available!
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:53 node-1 haproxy[30567]: proxy mysqld has no server available!
<129>Oct 29 18:03:53 node-1 haproxy[30567]: 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 29 18:03:54 node-1 haproxy[30567]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:54 node-1 haproxy[30567]: 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 29 18:03:54 node-1 haproxy[30567]: proxy object-storage has no server available!
<129>Oct 29 18:03:54 node-1 haproxy[30567]: 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 29 18:03:54 node-1 haproxy[30567]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:54 node-1 haproxy[30567]: 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 29 18:03:54 node-1 haproxy[30567]: proxy aodh has no server available!
<129>Oct 29 18:03:54 node-1 haproxy[30567]: 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 29 18:03:54 node-1 haproxy[30567]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:54 node-1 haproxy[30567]: 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 29 18:03:54 node-1 haproxy[30567]: proxy ceilometer has no server available!
<27>Oct 29 18:03:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:03:56 node-1 multipathd: uevent trigger error
<129>Oct 29 18:03:58 node-1 haproxy[31968]: 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 29 18:03:58 node-1 haproxy[31968]: 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 29 18:03:58 node-1 haproxy[31968]: Server keystone-1/node-3 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 29 18:03:58 node-1 haproxy[31968]: 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 29 18:03:58 node-1 haproxy[31968]: proxy keystone-1 has no server available!
<129>Oct 29 18:03:58 node-1 haproxy[31968]: 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 29 18:03:58 node-1 haproxy[31968]: Server keystone-2/node-3 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 29 18:03:58 node-1 haproxy[31968]: 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 29 18:03:58 node-1 haproxy[31968]: proxy keystone-2 has no server available!
<129>Oct 29 18:03:58 node-1 haproxy[31968]: 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 29 18:03:59 node-1 haproxy[31972]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: proxy nova-api has no server available!
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: proxy nova-metadata-api has no server available!
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: proxy glance-api has no server available!
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: proxy glance-glare has no server available!
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: proxy neutron has no server available!
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: proxy glance-registry has no server available!
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:03:59 node-1 haproxy[31972]: proxy mysqld has no server available!
<129>Oct 29 18:03:59 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:00 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: proxy object-storage has no server available!
<129>Oct 29 18:04:00 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:00 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: proxy aodh has no server available!
<129>Oct 29 18:04:00 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:00 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: proxy ceilometer has no server available!
<129>Oct 29 18:04:00 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:00 node-1 haproxy[31972]: 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 29 18:04:00 node-1 haproxy[31972]: proxy nova-novncproxy has no server available!
<27>Oct 29 18:04:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:01 node-1 multipathd: uevent trigger error
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: Server keystone-1/node-3 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 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: proxy keystone-1 has no server available!
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: Server keystone-2/node-3 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 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: proxy keystone-2 has no server available!
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: proxy nova-api has no server available!
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: proxy nova-metadata-api has no server available!
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: proxy cinder-api has no server available!
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:04 node-1 haproxy[870]: proxy glance-api has no server available!
<129>Oct 29 18:04:04 node-1 haproxy[870]: 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 29 18:04:05 node-1 haproxy[874]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: proxy glance-glare has no server available!
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: proxy neutron has no server available!
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: proxy glance-registry has no server available!
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: proxy mysqld has no server available!
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: proxy object-storage has no server available!
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: proxy aodh has no server available!
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: proxy ceilometer has no server available!
<129>Oct 29 18:04:05 node-1 haproxy[874]: 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 29 18:04:05 node-1 haproxy[874]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:06 node-1 haproxy[874]: 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 29 18:04:06 node-1 haproxy[874]: proxy nova-novncproxy has no server available!
<27>Oct 29 18:04:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:07 node-1 multipathd: uevent trigger error
<129>Oct 29 18:04:09 node-1 haproxy[2377]: 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 29 18:04:09 node-1 haproxy[2377]: 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 29 18:04:09 node-1 haproxy[2377]: Server keystone-1/node-3 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 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy keystone-1 has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Server keystone-2/node-3 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 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy keystone-2 has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy nova-api has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy nova-metadata-api has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy cinder-api has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy glance-api has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy glance-glare has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy neutron has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: proxy glance-registry has no server available!
<129>Oct 29 18:04:10 node-1 haproxy[2386]: 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 29 18:04:10 node-1 haproxy[2386]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy mysqld has no server available!
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy object-storage has no server available!
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy aodh has no server available!
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy ceilometer has no server available!
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy heat-api has no server available!
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy heat-api-cfn has no server available!
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy heat-api-cloudwatch has no server available!
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 29 18:04:11 node-1 haproxy[2386]: 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 29 18:04:11 node-1 haproxy[2386]: proxy nova-novncproxy has no server available!
<27>Oct 29 18:04:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:16 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:16 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:16 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:16 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:16 node-1 multipathd: uevent trigger error
<27>Oct 29 18:04:23 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 29 18:04:48 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 29 18:04:50 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 29 18:05:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:05:21 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 29 18:05:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:05:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:05:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:05:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:05:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:08:29 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:29 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:29 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:29 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:29 node-1 multipathd: uevent trigger error
<43>Oct 29 18:08:30 node-1 apache2_error [Sat Oct 29 18:08:21.203119 2016] [mpm_event:notice] [pid 10913:tid 139920804513664] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 29 18:08:30 node-1 apache2_error [Sat Oct 29 18:08:21.203222 2016] [core:notice] [pid 10913:tid 139920804513664] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 29 18:08:30 node-1 apache2_error [Sat Oct 29 18:08:23.952101 2016] [mpm_event:notice] [pid 10913:tid 139920804513664] AH00491: caught SIGTERM, shutting down
<43>Oct 29 18:08:30 node-1 apache2_error [Sat Oct 29 18:08:25.034649 2016] [mpm_worker:notice] [pid 12053:tid 140537392920448] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 29 18:08:30 node-1 apache2_error [Sat Oct 29 18:08:25.034684 2016] [core:notice] [pid 12053:tid 140537392920448] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 18:08:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:08:37 node-1 multipathd: uevent trigger error
<43>Oct 29 18:09:40 node-1 apache2_error [Sat Oct 29 18:09:39.681699 2016] [mpm_worker:notice] [pid 12053:tid 140537392920448] AH00295: caught SIGTERM, shutting down
<43>Oct 29 18:09:40 node-1 apache2_error [Sat Oct 29 18:09:40.453778 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 18:09:40 node-1 apache2_error [Sat Oct 29 18:09:40.453808 2016] [core:notice] [pid 24767:tid 140312301979520] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 29 18:10:30 node-1 apache2_error [Sat Oct 29 18:10:24.423767 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 18:10:30 node-1 apache2_error [Sat Oct 29 18:10:24.616613 2016] [mpm_worker:warn] [pid 24767:tid 140312301979520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 29 18:10:30 node-1 apache2_error [Sat Oct 29 18:10:24.621274 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 18:10:30 node-1 apache2_error [Sat Oct 29 18:10:24.621314 2016] [core:notice] [pid 24767:tid 140312301979520] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 18:11:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:09 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:11:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:11:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:12:16 node-1 multipathd: uevent trigger error
<27>Oct 29 18:12:16 node-1 multipathd: uevent trigger error
<27>Oct 29 18:12:17 node-1 multipathd: uevent trigger error
<27>Oct 29 18:12:17 node-1 multipathd: uevent trigger error
<27>Oct 29 18:12:17 node-1 multipathd: uevent trigger error
<27>Oct 29 18:13:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:13:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:13:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:13:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:13:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:14:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:14:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:14:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:14:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:14:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:14:12 node-1 multipathd: uevent trigger error
<27>Oct 29 18:14:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:15:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:13 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:15:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:17:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:17:57 node-1 multipathd: uevent trigger error
<27>Oct 29 18:17:57 node-1 multipathd: uevent trigger error
<27>Oct 29 18:17:57 node-1 multipathd: uevent trigger error
<27>Oct 29 18:17:57 node-1 multipathd: uevent trigger error
<27>Oct 29 18:17:57 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:18:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:01 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:07 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct 29 18:20:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct 29 18:20:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct 29 18:20:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct 29 18:20:23 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct 29 18:20:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:23 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:20:38 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:38 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:38 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:38 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:38 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:20:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:21:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:21:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:21:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:21:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:21:10 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:27 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:27 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:27 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:23:27 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:27 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:27 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:23:55 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:00 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:00 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:00 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:00 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:00 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:19 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:19 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:19 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:19 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:19 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:31 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:31 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:31 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:31 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:31 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:36 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:36 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:36 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:36 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:36 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:40 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:40 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:40 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:40 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:40 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:24:46 node-1 multipathd: uevent trigger error
<27>Oct 29 18:25:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:25:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:25:33 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 29 18:26:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:37 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:53 node-1 multipathd: uevent trigger error
<27>Oct 29 18:26:53 node-1 multipathd: uevent trigger error
<11>Oct 29 18:27:06 node-1 liberasurecode[3827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:06 node-1 liberasurecode[3827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:06 node-1 liberasurecode[3827]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:06 node-1 liberasurecode[3827]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:06 node-1 liberasurecode[3874]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:06 node-1 liberasurecode[3874]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:06 node-1 liberasurecode[3874]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:06 node-1 liberasurecode[3874]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:08 node-1 liberasurecode[4392]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:08 node-1 liberasurecode[4392]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:08 node-1 liberasurecode[4392]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:08 node-1 liberasurecode[4392]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[4961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[4961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[4961]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[4961]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5008]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5008]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5008]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5008]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5052]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5052]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5052]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:12 node-1 liberasurecode[5052]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5110]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5110]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5110]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5110]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5128]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5128]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5163]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5163]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5163]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5163]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5175]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:13 node-1 liberasurecode[5175]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:22 node-1 liberasurecode[7477]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:22 node-1 liberasurecode[7477]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:22 node-1 liberasurecode[7477]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:27:22 node-1 liberasurecode[7477]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 29 18:27:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:27:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:27:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:27:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:27:30 node-1 multipathd: uevent trigger error
<43>Oct 29 18:28:22 node-1 apache2_error [Sat Oct 29 18:28:16.752589 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 18:28:22 node-1 apache2_error [Sat Oct 29 18:28:17.135991 2016] [mpm_worker:warn] [pid 24767:tid 140312301979520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 29 18:28:22 node-1 apache2_error [Sat Oct 29 18:28:17.140306 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 18:28:22 node-1 apache2_error [Sat Oct 29 18:28:17.140334 2016] [core:notice] [pid 24767:tid 140312301979520] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 18:28:58 node-1 multipathd: uevent trigger error
<27>Oct 29 18:28:58 node-1 multipathd: uevent trigger error
<27>Oct 29 18:28:58 node-1 multipathd: uevent trigger error
<27>Oct 29 18:28:58 node-1 multipathd: uevent trigger error
<27>Oct 29 18:28:58 node-1 multipathd: uevent trigger error
<43>Oct 29 18:29:02 node-1 apache2_error [Sat Oct 29 18:28:54.038220 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 18:29:02 node-1 apache2_error [Sat Oct 29 18:28:54.232726 2016] [mpm_worker:warn] [pid 24767:tid 140312301979520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 29 18:29:02 node-1 apache2_error [Sat Oct 29 18:28:54.240088 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 18:29:02 node-1 apache2_error [Sat Oct 29 18:28:54.240132 2016] [core:notice] [pid 24767:tid 140312301979520] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 18:29:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 29 18:29:42 node-1 apache2_error [Sat Oct 29 18:29:40.043722 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 29 18:29:42 node-1 apache2_error [Sat Oct 29 18:29:40.241502 2016] [mpm_worker:warn] [pid 24767:tid 140312301979520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 29 18:29:42 node-1 apache2_error [Sat Oct 29 18:29:40.245513 2016] [mpm_worker:notice] [pid 24767:tid 140312301979520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 29 18:29:42 node-1 apache2_error [Sat Oct 29 18:29:40.245528 2016] [core:notice] [pid 24767:tid 140312301979520] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 29 18:29:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:44 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:56 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:56 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:56 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:56 node-1 multipathd: uevent trigger error
<27>Oct 29 18:29:56 node-1 multipathd: uevent trigger error
<11>Oct 29 18:30:01 node-1 liberasurecode[3162]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:30:01 node-1 liberasurecode[3162]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:30:01 node-1 liberasurecode[3162]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 29 18:30:01 node-1 liberasurecode[3162]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 29 18:30:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:04 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:39 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:45 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 29 18:30:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:54 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:30:59 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:05 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:18 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:45 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:45 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:45 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:45 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:45 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:31:50 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:03 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:08 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:20 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:25 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:25 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:25 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:25 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:25 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:30 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:34 node-1 multipathd: uevent trigger error
<27>Oct 29 18:32:34 node-1 multipathd: uevent trigger error
