Aug 28 17:53:56 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] start
Aug 28 17:53:56 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Aug 28 17:53:56 node-1 rsyslogd: rsyslogd's groupid changed to 104
Aug 28 17:53:56 node-1 rsyslogd: rsyslogd's userid changed to 101
Aug 28 17:53:56 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Aug 28 17:53:56 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Aug 28 17:53:56 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Aug 28 17:53:56 node-1 kernel: [    0.000000] Linux version 3.13.0-93-generic (buildd@lgw01-13) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #140-Ubuntu SMP Mon Jul 18 21:21:05 UTC 2016 (Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39)
Aug 28 17:53:56 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-93-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=540d1894-ff07-4e50-8ea5-5d0514ec9fa3 nomdmonddf nomdmonisw
Aug 28 17:53:56 node-1 kernel: [    0.000000] KERNEL supported cpus:
Aug 28 17:53:56 node-1 kernel: [    0.000000]   Intel GenuineIntel
Aug 28 17:53:56 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Aug 28 17:53:56 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Aug 28 17:53:56 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Aug 28 17:53:56 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Aug 28 17:53:56 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Aug 28 17:53:56 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
Aug 28 17:53:56 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Aug 28 17:53:56 node-1 kernel: [    0.000000] No AGP bridge found
Aug 28 17:53:56 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Aug 28 17:53:56 node-1 kernel: [    0.000000] MTRR default type: write-back
Aug 28 17:53:56 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Aug 28 17:53:56 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Aug 28 17:53:56 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Aug 28 17:53:56 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Aug 28 17:53:56 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Aug 28 17:53:56 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Aug 28 17:53:56 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Aug 28 17:53:56 node-1 kernel: [    0.000000]   2 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000]   3 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000]   4 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000]   5 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000]   6 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000]   7 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000]   8 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000]   9 disabled
Aug 28 17:53:56 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Aug 28 17:53:56 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Aug 28 17:53:56 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Aug 28 17:53:56 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Aug 28 17:53:56 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Aug 28 17:53:56 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Aug 28 17:53:56 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Aug 28 17:53:56 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Aug 28 17:53:56 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Aug 28 17:53:56 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Aug 28 17:53:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Aug 28 17:53:56 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Aug 28 17:53:56 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Aug 28 17:53:56 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Aug 28 17:53:56 node-1 kernel: [    0.000000] Zone ranges:
Aug 28 17:53:56 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] Movable zone start for each node
Aug 28 17:53:56 node-1 kernel: [    0.000000] Early memory node ranges
Aug 28 17:53:56 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Aug 28 17:53:56 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Aug 28 17:53:56 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Aug 28 17:53:56 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Aug 28 17:53:56 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Aug 28 17:53:56 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Aug 28 17:53:56 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Aug 28 17:53:56 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Aug 28 17:53:56 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Aug 28 17:53:56 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Aug 28 17:53:56 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Aug 28 17:53:56 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Aug 28 17:53:56 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Aug 28 17:53:56 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Aug 28 17:53:56 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Aug 28 17:53:56 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Aug 28 17:53:56 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Aug 28 17:53:56 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Aug 28 17:53:56 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Aug 28 17:53:56 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Aug 28 17:53:56 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Aug 28 17:53:56 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Aug 28 17:53:56 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Aug 28 17:53:56 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 
Aug 28 17:53:56 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Aug 28 17:53:56 node-1 kernel: [    0.000000] Policy zone: Normal
Aug 28 17:53:56 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-93-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=540d1894-ff07-4e50-8ea5-5d0514ec9fa3 nomdmonddf nomdmonisw
Aug 28 17:53:56 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Aug 28 17:53:56 node-1 kernel: [    0.000000] Checking aperture...
Aug 28 17:53:56 node-1 kernel: [    0.000000] No AGP bridge found
Aug 28 17:53:56 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Aug 28 17:53:56 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Aug 28 17:53:56 node-1 kernel: [    0.000000] Memory: 32653456K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Aug 28 17:53:56 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Aug 28 17:53:56 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Aug 28 17:53:56 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Aug 28 17:53:56 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Aug 28 17:53:56 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Aug 28 17:53:56 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Aug 28 17:53:56 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Aug 28 17:53:56 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Aug 28 17:53:56 node-1 kernel: [    0.000000] console [tty0] enabled
Aug 28 17:53:56 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Aug 28 17:53:56 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Aug 28 17:53:56 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Aug 28 17:53:56 node-1 kernel: [    0.000000] hpet clockevent registered
Aug 28 17:53:56 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Aug 28 17:53:56 node-1 kernel: [    0.004000] tsc: Detected 3492.079 MHz processor
Aug 28 17:53:56 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.15 BogoMIPS (lpj=13968316)
Aug 28 17:53:56 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Aug 28 17:53:56 node-1 kernel: [    0.000048] Security Framework initialized
Aug 28 17:53:56 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Aug 28 17:53:56 node-1 kernel: [    0.000067] Yama: becoming mindful.
Aug 28 17:53:56 node-1 kernel: [    0.001463] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.006338] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.008264] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.008292] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.008582] Initializing cgroup subsys memory
Aug 28 17:53:56 node-1 kernel: [    0.008590] Initializing cgroup subsys devices
Aug 28 17:53:56 node-1 kernel: [    0.008592] Initializing cgroup subsys freezer
Aug 28 17:53:56 node-1 kernel: [    0.008594] Initializing cgroup subsys blkio
Aug 28 17:53:56 node-1 kernel: [    0.008595] Initializing cgroup subsys perf_event
Aug 28 17:53:56 node-1 kernel: [    0.008598] Initializing cgroup subsys hugetlb
Aug 28 17:53:56 node-1 kernel: [    0.008618] CPU: Physical Processor ID: 0
Aug 28 17:53:56 node-1 kernel: [    0.008619] CPU: Processor Core ID: 0
Aug 28 17:53:56 node-1 kernel: [    0.008623] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Aug 28 17:53:56 node-1 kernel: [    0.008623] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Aug 28 17:53:56 node-1 kernel: [    0.009317] mce: CPU supports 22 MCE banks
Aug 28 17:53:56 node-1 kernel: [    0.009344] CPU0: Thermal monitoring enabled (TM1)
Aug 28 17:53:56 node-1 kernel: [    0.009365] process: using mwait in idle threads
Aug 28 17:53:56 node-1 kernel: [    0.009368] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Aug 28 17:53:56 node-1 kernel: [    0.009368] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Aug 28 17:53:56 node-1 kernel: [    0.009368] tlb_flushall_shift: 6
Aug 28 17:53:56 node-1 kernel: [    0.009457] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Aug 28 17:53:56 node-1 kernel: [    0.010180] ACPI: Core revision 20131115
Aug 28 17:53:56 node-1 kernel: [    0.022888] ACPI: All ACPI Tables successfully acquired
Aug 28 17:53:56 node-1 kernel: [    0.023061] ftrace: allocating 28617 entries in 112 pages
Aug 28 17:53:56 node-1 kernel: [    0.032027] dmar: Host address width 46
Aug 28 17:53:56 node-1 kernel: [    0.032030] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Aug 28 17:53:56 node-1 kernel: [    0.032036] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 28 17:53:56 node-1 kernel: [    0.032037] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Aug 28 17:53:56 node-1 kernel: [    0.032041] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 28 17:53:56 node-1 kernel: [    0.032043] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Aug 28 17:53:56 node-1 kernel: [    0.032044] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Aug 28 17:53:56 node-1 kernel: [    0.032045] dmar: ATSR flags: 0x0
Aug 28 17:53:56 node-1 kernel: [    0.032046] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Aug 28 17:53:56 node-1 kernel: [    0.032047] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Aug 28 17:53:56 node-1 kernel: [    0.032163] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Aug 28 17:53:56 node-1 kernel: [    0.032164] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Aug 28 17:53:56 node-1 kernel: [    0.032165] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Aug 28 17:53:56 node-1 kernel: [    0.032166] HPET id 0 under DRHD base 0xc7ffc000
Aug 28 17:53:56 node-1 kernel: [    0.032167] Your BIOS is broken and requested that x2apic be disabled.
Aug 28 17:53:56 node-1 kernel: [    0.032167] This will slightly decrease performance.
Aug 28 17:53:56 node-1 kernel: [    0.032167] Use 'intremap=no_x2apic_optout' to override BIOS request.
Aug 28 17:53:56 node-1 kernel: [    0.032598] Enabled IRQ remapping in xapic mode
Aug 28 17:53:56 node-1 kernel: [    0.032599] x2apic not enabled, IRQ remapping is in xapic mode
Aug 28 17:53:56 node-1 kernel: [    0.032603] Switched APIC routing to physical flat.
Aug 28 17:53:56 node-1 kernel: [    0.033181] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Aug 28 17:53:56 node-1 kernel: [    0.072833] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Aug 28 17:53:56 node-1 kernel: [    0.072838] TSC deadline timer enabled
Aug 28 17:53:56 node-1 kernel: [    0.072845] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Aug 28 17:53:56 node-1 kernel: [    0.072851] ... version:                3
Aug 28 17:53:56 node-1 kernel: [    0.072852] ... bit width:              48
Aug 28 17:53:56 node-1 kernel: [    0.072853] ... generic registers:      4
Aug 28 17:53:56 node-1 kernel: [    0.072854] ... value mask:             0000ffffffffffff
Aug 28 17:53:56 node-1 kernel: [    0.072855] ... max period:             0000ffffffffffff
Aug 28 17:53:56 node-1 kernel: [    0.072856] ... fixed-purpose events:   3
Aug 28 17:53:56 node-1 kernel: [    0.072856] ... event mask:             000000070000000f
Aug 28 17:53:56 node-1 kernel: [    0.074230] x86: Booting SMP configuration:
Aug 28 17:53:56 node-1 kernel: [    0.088336] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Aug 28 17:53:56 node-1 kernel: [    0.074232] .... node  #0, CPUs:        #1  #2  #3
Aug 28 17:53:56 node-1 kernel: [    0.116240] .... node  #1, CPUs:    #4  #5  #6  #7
Aug 28 17:53:56 node-1 kernel: [    0.270417] .... node  #0, CPUs:    #8  #9 #10 #11
Aug 28 17:53:56 node-1 kernel: [    0.326044] .... node  #1, CPUs:   #12 #13 #14 #15
Aug 28 17:53:56 node-1 kernel: [    0.382897] x86: Booted up 2 nodes, 16 CPUs
Aug 28 17:53:56 node-1 kernel: [    0.382900] smpboot: Total of 16 processors activated (111758.95 BogoMIPS)
Aug 28 17:53:56 node-1 kernel: [    0.406803] devtmpfs: initialized
Aug 28 17:53:56 node-1 kernel: [    0.409888] EVM: security.selinux
Aug 28 17:53:56 node-1 kernel: [    0.409890] EVM: security.SMACK64
Aug 28 17:53:56 node-1 kernel: [    0.409890] EVM: security.ima
Aug 28 17:53:56 node-1 kernel: [    0.409891] EVM: security.capability
Aug 28 17:53:56 node-1 kernel: [    0.409942] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.410629] pinctrl core: initialized pinctrl subsystem
Aug 28 17:53:56 node-1 kernel: [    0.410693] regulator-dummy: no parameters
Aug 28 17:53:56 node-1 kernel: [    0.410725] RTC time: 17:53:16, date: 08/28/16
Aug 28 17:53:56 node-1 kernel: [    0.410760] NET: Registered protocol family 16
Aug 28 17:53:56 node-1 kernel: [    0.410846] cpuidle: using governor ladder
Aug 28 17:53:56 node-1 kernel: [    0.410847] cpuidle: using governor menu
Aug 28 17:53:56 node-1 kernel: [    0.410883] ACPI: bus type PCI registered
Aug 28 17:53:56 node-1 kernel: [    0.410885] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Aug 28 17:53:56 node-1 kernel: [    0.410930] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Aug 28 17:53:56 node-1 kernel: [    0.410933] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Aug 28 17:53:56 node-1 kernel: [    0.424676] PCI: Using configuration type 1 for base access
Aug 28 17:53:56 node-1 kernel: [    0.425683] bio: create slab <bio-0> at 0
Aug 28 17:53:56 node-1 kernel: [    0.425948] ACPI: Added _OSI(Module Device)
Aug 28 17:53:56 node-1 kernel: [    0.425949] ACPI: Added _OSI(Processor Device)
Aug 28 17:53:56 node-1 kernel: [    0.425951] ACPI: Added _OSI(3.0 _SCP Extensions)
Aug 28 17:53:56 node-1 kernel: [    0.425952] ACPI: Added _OSI(Processor Aggregator Device)
Aug 28 17:53:56 node-1 kernel: [    0.438622] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Aug 28 17:53:56 node-1 kernel: [    0.449350] ACPI: Interpreter enabled
Aug 28 17:53:56 node-1 kernel: [    0.449356] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Aug 28 17:53:56 node-1 kernel: [    0.449360] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Aug 28 17:53:56 node-1 kernel: [    0.449363] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Aug 28 17:53:56 node-1 kernel: [    0.449370] ACPI: (supports S0 S4 S5)
Aug 28 17:53:56 node-1 kernel: [    0.449371] ACPI: Using IOAPIC for interrupt routing
Aug 28 17:53:56 node-1 kernel: [    0.449412] HEST: Table parsing has been initialized.
Aug 28 17:53:56 node-1 kernel: [    0.449415] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Aug 28 17:53:56 node-1 kernel: [    0.449969] ACPI: No dock devices found.
Aug 28 17:53:56 node-1 kernel: [    0.461617] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Aug 28 17:53:56 node-1 kernel: [    0.461621] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 28 17:53:56 node-1 kernel: [    0.461625] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 28 17:53:56 node-1 kernel: [    0.461654] PCI host bridge to bus 0000:ff
Aug 28 17:53:56 node-1 kernel: [    0.461656] pci_bus 0000:ff: root bus resource [bus ff]
Aug 28 17:53:56 node-1 kernel: [    0.461665] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.461704] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.461735] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.461770] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.461800] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.461830] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.461861] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.461890] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.461921] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.461949] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.461976] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462002] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462033] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462059] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462086] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462113] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462141] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462169] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462196] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.462224] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462250] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.462276] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462302] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462332] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.462367] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462398] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462428] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462459] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462490] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462521] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462552] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462582] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462613] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462645] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462676] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462708] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462743] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462773] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462801] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462833] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462866] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462906] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462942] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.462976] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463005] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463034] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463066] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463098] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463132] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463164] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463196] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463227] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463257] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463287] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463317] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463349] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463381] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463444] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Aug 28 17:53:56 node-1 kernel: [    0.463447] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 28 17:53:56 node-1 kernel: [    0.463450] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 28 17:53:56 node-1 kernel: [    0.463468] PCI host bridge to bus 0000:7f
Aug 28 17:53:56 node-1 kernel: [    0.463470] pci_bus 0000:7f: root bus resource [bus 7f]
Aug 28 17:53:56 node-1 kernel: [    0.463475] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463503] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.463532] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463562] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463584] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.463610] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.463636] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463663] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463686] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463709] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463733] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463755] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463780] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463802] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463826] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463852] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463874] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463897] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463920] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.463944] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.463966] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.463988] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464012] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464039] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Aug 28 17:53:56 node-1 kernel: [    0.464073] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464100] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464126] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464154] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464180] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464208] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464235] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464263] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464289] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464318] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464347] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464375] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464405] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464429] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464455] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464483] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464509] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464535] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464566] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464595] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464621] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464647] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464673] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464702] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464730] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464757] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464788] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464814] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464837] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464864] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464890] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464920] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.464949] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.466205] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Aug 28 17:53:56 node-1 kernel: [    0.466208] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 28 17:53:56 node-1 kernel: [    0.467330] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 28 17:53:56 node-1 kernel: [    0.467844] PCI host bridge to bus 0000:00
Aug 28 17:53:56 node-1 kernel: [    0.467847] pci_bus 0000:00: root bus resource [bus 00-7e]
Aug 28 17:53:56 node-1 kernel: [    0.467848] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Aug 28 17:53:56 node-1 kernel: [    0.467850] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Aug 28 17:53:56 node-1 kernel: [    0.467851] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Aug 28 17:53:56 node-1 kernel: [    0.467852] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Aug 28 17:53:56 node-1 kernel: [    0.467854] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Aug 28 17:53:56 node-1 kernel: [    0.467855] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Aug 28 17:53:56 node-1 kernel: [    0.467861] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Aug 28 17:53:56 node-1 kernel: [    0.467944] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.467975] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.468017] pci 0000:00:01.0: System wakeup disabled by ACPI
Aug 28 17:53:56 node-1 kernel: [    0.468037] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.468066] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.468107] pci 0000:00:02.0: System wakeup disabled by ACPI
Aug 28 17:53:56 node-1 kernel: [    0.468126] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.468156] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.468196] pci 0000:00:03.0: System wakeup disabled by ACPI
Aug 28 17:53:56 node-1 kernel: [    0.468214] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.468282] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.468361] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.468439] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Aug 28 17:53:56 node-1 kernel: [    0.468444] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Aug 28 17:53:56 node-1 kernel: [    0.468529] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Aug 28 17:53:56 node-1 kernel: [    0.468679] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Aug 28 17:53:56 node-1 kernel: [    0.468697] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Aug 28 17:53:56 node-1 kernel: [    0.468775] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.468829] pci 0000:00:1a.0: System wakeup disabled by ACPI
Aug 28 17:53:56 node-1 kernel: [    0.468851] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.468906] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.468950] pci 0000:00:1c.0: System wakeup disabled by ACPI
Aug 28 17:53:56 node-1 kernel: [    0.468977] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.469033] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.469076] pci 0000:00:1c.7: System wakeup disabled by ACPI
Aug 28 17:53:56 node-1 kernel: [    0.469101] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Aug 28 17:53:56 node-1 kernel: [    0.469118] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Aug 28 17:53:56 node-1 kernel: [    0.469196] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.469246] pci 0000:00:1d.0: System wakeup disabled by ACPI
Aug 28 17:53:56 node-1 kernel: [    0.469272] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Aug 28 17:53:56 node-1 kernel: [    0.469520] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Aug 28 17:53:56 node-1 kernel: [    0.469526] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Aug 28 17:53:56 node-1 kernel: [    0.469532] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.469538] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.469545] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Aug 28 17:53:56 node-1 kernel: [    0.469575] pci 0000:01:00.0: supports D1 D2
Aug 28 17:53:56 node-1 kernel: [    0.475425] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 28 17:53:56 node-1 kernel: [    0.475431] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 28 17:53:56 node-1 kernel: [    0.475435] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 28 17:53:56 node-1 kernel: [    0.475709] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.475742] pci 0000:02:00.0: PME# supported from D0 D3hot
Aug 28 17:53:56 node-1 kernel: [    0.483425] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 28 17:53:56 node-1 kernel: [    0.483431] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.483435] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 28 17:53:56 node-1 kernel: [    0.483519] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.483591] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.483686] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.483767] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 28 17:53:56 node-1 kernel: [    0.483775] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.483779] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 28 17:53:56 node-1 kernel: [    0.483858] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.483981] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.484034] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 28 17:53:56 node-1 kernel: [    0.484037] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.484039] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.484088] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.484206] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.484245] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.484366] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.484402] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.484521] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.484556] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Aug 28 17:53:56 node-1 kernel: [    0.484675] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Aug 28 17:53:56 node-1 kernel: [    0.484716] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 28 17:53:56 node-1 kernel: [    0.484718] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.484720] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.484793] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Aug 28 17:53:56 node-1 kernel: [    0.484858] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.484910] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.484951] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Aug 28 17:53:56 node-1 kernel: [    0.485033] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Aug 28 17:53:56 node-1 kernel: [    0.485138] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 28 17:53:56 node-1 kernel: [    0.485140] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.485142] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.485198] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Aug 28 17:53:56 node-1 kernel: [    0.485251] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.485303] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.485515] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 28 17:53:56 node-1 kernel: [    0.485519] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 28 17:53:56 node-1 kernel: [    0.485580] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Aug 28 17:53:56 node-1 kernel: [    0.485633] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.485681] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.485922] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 28 17:53:56 node-1 kernel: [    0.485925] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 28 17:53:56 node-1 kernel: [    0.485982] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Aug 28 17:53:56 node-1 kernel: [    0.486042] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.486095] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Aug 28 17:53:56 node-1 kernel: [    0.486315] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 28 17:53:56 node-1 kernel: [    0.486318] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 28 17:53:56 node-1 kernel: [    0.486494] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 28 17:53:56 node-1 kernel: [    0.486532] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 28 17:53:56 node-1 kernel: [    0.486608] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Aug 28 17:53:56 node-1 kernel: [    0.486627] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Aug 28 17:53:56 node-1 kernel: [    0.486641] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Aug 28 17:53:56 node-1 kernel: [    0.486654] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Aug 28 17:53:56 node-1 kernel: [    0.486704] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Aug 28 17:53:56 node-1 kernel: [    0.491422] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 28 17:53:56 node-1 kernel: [    0.491427] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 28 17:53:56 node-1 kernel: [    0.491459] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Aug 28 17:53:56 node-1 kernel: [    0.491950] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Aug 28 17:53:56 node-1 kernel: [    0.491953] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 28 17:53:56 node-1 kernel: [    0.492072] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 28 17:53:56 node-1 kernel: [    0.492178] PCI host bridge to bus 0000:80
Aug 28 17:53:56 node-1 kernel: [    0.492181] pci_bus 0000:80: root bus resource [bus 80-fe]
Aug 28 17:53:56 node-1 kernel: [    0.492182] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Aug 28 17:53:56 node-1 kernel: [    0.492183] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Aug 28 17:53:56 node-1 kernel: [    0.492191] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.492255] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.492322] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Aug 28 17:53:56 node-1 kernel: [    0.492384] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Aug 28 17:53:56 node-1 kernel: [    0.492390] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Aug 28 17:53:56 node-1 kernel: [    0.492462] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Aug 28 17:53:56 node-1 kernel: [    0.492758] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Aug 28 17:53:56 node-1 kernel: [    0.492789] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Aug 28 17:53:56 node-1 kernel: [    0.492819] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Aug 28 17:53:56 node-1 kernel: [    0.492848] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Aug 28 17:53:56 node-1 kernel: [    0.492877] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 28 17:53:56 node-1 kernel: [    0.492907] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 28 17:53:56 node-1 kernel: [    0.492937] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 28 17:53:56 node-1 kernel: [    0.492967] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 28 17:53:56 node-1 kernel: [    0.493051] ACPI: Enabled 3 GPEs in block 00 to 3F
Aug 28 17:53:56 node-1 kernel: [    0.493056] ACPI: \_SB_.UNC1: notify handler is installed
Aug 28 17:53:56 node-1 kernel: [    0.493057] ACPI: \_SB_.UNC0: notify handler is installed
Aug 28 17:53:56 node-1 kernel: [    0.493072] ACPI: \_SB_.PCI0: notify handler is installed
Aug 28 17:53:56 node-1 kernel: [    0.493125] ACPI: \_SB_.PCI1: notify handler is installed
Aug 28 17:53:56 node-1 kernel: [    0.493204] Found 4 acpi root devices
Aug 28 17:53:56 node-1 kernel: [    0.493309] vgaarb: setting as boot device: PCI:0000:0c:00.0
Aug 28 17:53:56 node-1 kernel: [    0.493311] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Aug 28 17:53:56 node-1 kernel: [    0.493312] vgaarb: loaded
Aug 28 17:53:56 node-1 kernel: [    0.493313] vgaarb: bridge control possible 0000:0c:00.0
Aug 28 17:53:56 node-1 kernel: [    0.493423] SCSI subsystem initialized
Aug 28 17:53:56 node-1 kernel: [    0.493493] libata version 3.00 loaded.
Aug 28 17:53:56 node-1 kernel: [    0.493507] ACPI: bus type USB registered
Aug 28 17:53:56 node-1 kernel: [    0.493517] usbcore: registered new interface driver usbfs
Aug 28 17:53:56 node-1 kernel: [    0.493522] usbcore: registered new interface driver hub
Aug 28 17:53:56 node-1 kernel: [    0.493544] usbcore: registered new device driver usb
Aug 28 17:53:56 node-1 kernel: [    0.493703] PCI: Using ACPI for IRQ routing
Aug 28 17:53:56 node-1 kernel: [    0.497295] PCI: pci_cache_line_size set to 64 bytes
Aug 28 17:53:56 node-1 kernel: [    0.497501] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Aug 28 17:53:56 node-1 kernel: [    0.497503] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Aug 28 17:53:56 node-1 kernel: [    0.497503] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Aug 28 17:53:56 node-1 kernel: [    0.497569] NetLabel: Initializing
Aug 28 17:53:56 node-1 kernel: [    0.497570] NetLabel:  domain hash size = 128
Aug 28 17:53:56 node-1 kernel: [    0.497571] NetLabel:  protocols = UNLABELED CIPSOv4
Aug 28 17:53:56 node-1 kernel: [    0.497580] NetLabel:  unlabeled traffic allowed by default
Aug 28 17:53:56 node-1 kernel: [    0.497635] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Aug 28 17:53:56 node-1 kernel: [    0.497639] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Aug 28 17:53:56 node-1 kernel: [    0.499710] Switched to clocksource hpet
Aug 28 17:53:56 node-1 kernel: [    0.504160] AppArmor: AppArmor Filesystem Enabled
Aug 28 17:53:56 node-1 kernel: [    0.504198] pnp: PnP ACPI init
Aug 28 17:53:56 node-1 kernel: [    0.504210] ACPI: bus type PNP registered
Aug 28 17:53:56 node-1 kernel: [    0.504389] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504399] pnp 00:01: [dma 4]
Aug 28 17:53:56 node-1 kernel: [    0.504417] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504451] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504476] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504497] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504545] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504657] system 00:06: [io  0x0500-0x057f] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504659] system 00:06: [io  0x0400-0x047f] could not be reserved
Aug 28 17:53:56 node-1 kernel: [    0.504661] system 00:06: [io  0x0580-0x059f] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504662] system 00:06: [io  0x0600-0x061f] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504664] system 00:06: [io  0x0880-0x0883] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504665] system 00:06: [io  0x0800-0x081f] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504669] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Aug 28 17:53:56 node-1 kernel: [    0.504671] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504672] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504674] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504675] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504677] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504678] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Aug 28 17:53:56 node-1 kernel: [    0.504680] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504780] pnp 00:07: [dma 0 disabled]
Aug 28 17:53:56 node-1 kernel: [    0.504813] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504894] pnp 00:08: [dma 0 disabled]
Aug 28 17:53:56 node-1 kernel: [    0.504930] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 28 17:53:56 node-1 kernel: [    0.504989] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Aug 28 17:53:56 node-1 kernel: [    0.505435] pnp: PnP ACPI: found 10 devices
Aug 28 17:53:56 node-1 kernel: [    0.505437] ACPI: bus type PNP unregistered
Aug 28 17:53:56 node-1 kernel: [    0.511472] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 28 17:53:56 node-1 kernel: [    0.511475] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 28 17:53:56 node-1 kernel: [    0.511478] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 28 17:53:56 node-1 kernel: [    0.511483] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 28 17:53:56 node-1 kernel: [    0.511485] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511500] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511530] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 28 17:53:56 node-1 kernel: [    0.511544] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511573] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 28 17:53:56 node-1 kernel: [    0.511588] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 28 17:53:56 node-1 kernel: [    0.511617] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 28 17:53:56 node-1 kernel: [    0.511631] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 28 17:53:56 node-1 kernel: [    0.511660] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 28 17:53:56 node-1 kernel: [    0.511662] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511677] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511710] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 28 17:53:56 node-1 kernel: [    0.511712] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511726] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511769] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 28 17:53:56 node-1 kernel: [    0.511771] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511774] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511779] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 28 17:53:56 node-1 kernel: [    0.511780] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511783] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511787] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 28 17:53:56 node-1 kernel: [    0.511793] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 28 17:53:56 node-1 kernel: [    0.511802] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 28 17:53:56 node-1 kernel: [    0.511806] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 28 17:53:56 node-1 kernel: [    0.511813] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Aug 28 17:53:56 node-1 kernel: [    0.511814] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Aug 28 17:53:56 node-1 kernel: [    0.511815] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Aug 28 17:53:56 node-1 kernel: [    0.511816] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Aug 28 17:53:56 node-1 kernel: [    0.511817] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Aug 28 17:53:56 node-1 kernel: [    0.511818] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Aug 28 17:53:56 node-1 kernel: [    0.511819] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Aug 28 17:53:56 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Aug 28 17:53:56 node-1 kernel: [    0.511820] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Aug 28 17:53:56 node-1 kernel: [    0.511821] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511822] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511823] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511824] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511825] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511825] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511826] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511827] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511828] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Aug 28 17:53:56 node-1 kernel: [    0.511829] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511830] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Aug 28 17:53:56 node-1 kernel: [    0.511832] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Aug 28 17:53:56 node-1 kernel: [    0.511833] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Aug 28 17:53:56 node-1 kernel: [    0.511834] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Aug 28 17:53:56 node-1 kernel: [    0.511836] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Aug 28 17:53:56 node-1 kernel: [    0.511837] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Aug 28 17:53:56 node-1 kernel: [    0.511876] NET: Registered protocol family 2
Aug 28 17:53:56 node-1 kernel: [    0.512168] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.512539] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.512705] TCP: Hash tables configured (established 262144 bind 65536)
Aug 28 17:53:56 node-1 kernel: [    0.512747] TCP: reno registered
Aug 28 17:53:56 node-1 kernel: [    0.512779] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.512887] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.513075] NET: Registered protocol family 1
Aug 28 17:53:56 node-1 kernel: [    0.551804] pci 0000:0c:00.0: Video device with shadowed ROM
Aug 28 17:53:56 node-1 kernel: [    0.551820] PCI: CLS 64 bytes, default 64
Aug 28 17:53:56 node-1 kernel: [    0.551904] Trying to unpack rootfs image as initramfs...
Aug 28 17:53:56 node-1 kernel: [    0.774541] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Aug 28 17:53:56 node-1 kernel: [    0.774585] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Aug 28 17:53:56 node-1 kernel: [    0.774588] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Aug 28 17:53:56 node-1 kernel: [    0.775043] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775052] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775060] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775068] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775074] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775081] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775088] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775094] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775116] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775138] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775149] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775156] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775164] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775171] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775176] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775182] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Aug 28 17:53:56 node-1 kernel: [    0.775230] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Aug 28 17:53:56 node-1 kernel: [    0.775233] Scanning for low memory corruption every 60 seconds
Aug 28 17:53:56 node-1 kernel: [    0.775558] Initialise system trusted keyring
Aug 28 17:53:56 node-1 kernel: [    0.775607] audit: initializing netlink socket (disabled)
Aug 28 17:53:56 node-1 kernel: [    0.775619] type=2000 audit(1472406795.732:1): initialized
Aug 28 17:53:56 node-1 kernel: [    0.793484] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Aug 28 17:53:56 node-1 kernel: [    0.794948] zbud: loaded
Aug 28 17:53:56 node-1 kernel: [    0.795080] VFS: Disk quotas dquot_6.5.2
Aug 28 17:53:56 node-1 kernel: [    0.795121] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Aug 28 17:53:56 node-1 kernel: [    0.795502] fuse init (API version 7.22)
Aug 28 17:53:56 node-1 kernel: [    0.795554] msgmni has been set to 32768
Aug 28 17:53:56 node-1 kernel: [    0.795605] Key type big_key registered
Aug 28 17:53:56 node-1 kernel: [    0.796067] Key type asymmetric registered
Aug 28 17:53:56 node-1 kernel: [    0.796069] Asymmetric key parser 'x509' registered
Aug 28 17:53:56 node-1 kernel: [    0.796092] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Aug 28 17:53:56 node-1 kernel: [    0.796183] io scheduler noop registered
Aug 28 17:53:56 node-1 kernel: [    0.796184] io scheduler deadline registered (default)
Aug 28 17:53:56 node-1 kernel: [    0.796203] io scheduler cfq registered
Aug 28 17:53:56 node-1 kernel: [    0.796581] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    0.796710] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    0.796830] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    0.796946] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    0.797066] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    0.797161] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    0.797554] aer 0000:00:01.0:pcie02: service driver aer loaded
Aug 28 17:53:56 node-1 kernel: [    0.797594] aer 0000:00:02.0:pcie02: service driver aer loaded
Aug 28 17:53:56 node-1 kernel: [    0.797621] aer 0000:00:03.0:pcie02: service driver aer loaded
Aug 28 17:53:56 node-1 kernel: [    0.797643] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797647] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797662] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Aug 28 17:53:56 node-1 kernel: [    0.797673] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797677] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797680] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797684] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797688] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797691] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797695] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797699] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797703] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797706] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797710] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797714] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797719] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Aug 28 17:53:56 node-1 kernel: [    0.797737] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797742] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Aug 28 17:53:56 node-1 kernel: [    0.797762] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797768] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Aug 28 17:53:56 node-1 kernel: [    0.797787] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797792] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Aug 28 17:53:56 node-1 kernel: [    0.797798] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Aug 28 17:53:56 node-1 kernel: [    0.797848] ioapic: probe of 0000:00:05.4 failed with error -22
Aug 28 17:53:56 node-1 kernel: [    0.797860] ioapic: probe of 0000:80:05.4 failed with error -22
Aug 28 17:53:56 node-1 kernel: [    0.797869] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Aug 28 17:53:56 node-1 kernel: [    0.797890] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Aug 28 17:53:56 node-1 kernel: [    0.797970] vesafb: mode is 640x480x32, linelength=2560, pages=0
Aug 28 17:53:56 node-1 kernel: [    0.797972] vesafb: scrolling: redraw
Aug 28 17:53:56 node-1 kernel: [    0.797973] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Aug 28 17:53:56 node-1 kernel: [    0.818489] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Aug 28 17:53:56 node-1 kernel: [    0.826991] Console: switching to colour frame buffer device 80x30
Aug 28 17:53:56 node-1 kernel: [    0.835675] fb0: VESA VGA frame buffer device
Aug 28 17:53:56 node-1 kernel: [    0.835870] intel_idle: MWAIT substates: 0x2120
Aug 28 17:53:56 node-1 kernel: [    0.835871] intel_idle: v0.4 model 0x3F
Aug 28 17:53:56 node-1 kernel: [    0.835872] intel_idle: lapic_timer_reliable_states 0xffffffff
Aug 28 17:53:56 node-1 kernel: [    0.836101] ipmi message handler version 39.2
Aug 28 17:53:56 node-1 kernel: [    0.836365] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Aug 28 17:53:56 node-1 kernel: [    0.836798] ACPI: AC Adapter [P111] (on-line)
Aug 28 17:53:56 node-1 kernel: [    0.842044] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Aug 28 17:53:56 node-1 kernel: [    0.853090] ACPI: Power Button [PWRB]
Aug 28 17:53:56 node-1 kernel: [    0.858869] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Aug 28 17:53:56 node-1 kernel: [    0.870526] ACPI: Power Button [PWRF]
Aug 28 17:53:56 node-1 kernel: [    0.897309] ERST: Error Record Serialization Table (ERST) support is initialized.
Aug 28 17:53:56 node-1 kernel: [    0.908980] pstore: Registered erst as persistent store backend
Aug 28 17:53:56 node-1 kernel: [    0.915209] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Aug 28 17:53:56 node-1 kernel: [    0.927168] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Aug 28 17:53:56 node-1 kernel: [    0.953929] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Aug 28 17:53:56 node-1 kernel: [    0.987226] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Aug 28 17:53:56 node-1 kernel: [    1.001307] Linux agpgart interface v0.103
Aug 28 17:53:56 node-1 kernel: [    1.008925] brd: module loaded
Aug 28 17:53:56 node-1 kernel: [    1.015983] loop: module loaded
Aug 28 17:53:56 node-1 kernel: [    1.022712] libphy: Fixed MDIO Bus: probed
Aug 28 17:53:56 node-1 kernel: [    1.029184] tun: Universal TUN/TAP device driver, 1.6
Aug 28 17:53:56 node-1 kernel: [    1.035670] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Aug 28 17:53:56 node-1 kernel: [    1.042218] PPP generic driver version 2.4.2
Aug 28 17:53:56 node-1 kernel: [    1.048674] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Aug 28 17:53:56 node-1 kernel: [    1.055184] ehci-pci: EHCI PCI platform driver
Aug 28 17:53:56 node-1 kernel: [    1.061699] ehci-pci 0000:00:1a.0: EHCI Host Controller
Aug 28 17:53:56 node-1 kernel: [    1.068108] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Aug 28 17:53:56 node-1 kernel: [    1.080622] ehci-pci 0000:00:1a.0: debug port 2
Aug 28 17:53:56 node-1 kernel: [    1.090812] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Aug 28 17:53:56 node-1 kernel: [    1.090830] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Aug 28 17:53:56 node-1 kernel: [    1.107186] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Aug 28 17:53:56 node-1 kernel: [    1.113247] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Aug 28 17:53:56 node-1 kernel: [    1.119414] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 28 17:53:56 node-1 kernel: [    1.131300] usb usb1: Product: EHCI Host Controller
Aug 28 17:53:56 node-1 kernel: [    1.137325] usb usb1: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 28 17:53:56 node-1 kernel: [    1.143362] usb usb1: SerialNumber: 0000:00:1a.0
Aug 28 17:53:56 node-1 kernel: [    1.149334] hub 1-0:1.0: USB hub found
Aug 28 17:53:56 node-1 kernel: [    1.155108] hub 1-0:1.0: 2 ports detected
Aug 28 17:53:56 node-1 kernel: [    1.160907] ehci-pci 0000:00:1d.0: EHCI Host Controller
Aug 28 17:53:56 node-1 kernel: [    1.166482] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Aug 28 17:53:56 node-1 kernel: [    1.177395] ehci-pci 0000:00:1d.0: debug port 2
Aug 28 17:53:56 node-1 kernel: [    1.186677] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Aug 28 17:53:56 node-1 kernel: [    1.186680] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Aug 28 17:53:56 node-1 kernel: [    1.203104] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Aug 28 17:53:56 node-1 kernel: [    1.208304] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Aug 28 17:53:56 node-1 kernel: [    1.213601] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 28 17:53:56 node-1 kernel: [    1.224161] usb usb2: Product: EHCI Host Controller
Aug 28 17:53:56 node-1 kernel: [    1.229620] usb usb2: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 28 17:53:56 node-1 kernel: [    1.235164] usb usb2: SerialNumber: 0000:00:1d.0
Aug 28 17:53:56 node-1 kernel: [    1.240714] hub 2-0:1.0: USB hub found
Aug 28 17:53:56 node-1 kernel: [    1.246126] hub 2-0:1.0: 2 ports detected
Aug 28 17:53:56 node-1 kernel: [    1.251517] ehci-platform: EHCI generic platform driver
Aug 28 17:53:56 node-1 kernel: [    1.256735] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Aug 28 17:53:56 node-1 kernel: [    1.262040] ohci-pci: OHCI PCI platform driver
Aug 28 17:53:56 node-1 kernel: [    1.267330] ohci-platform: OHCI generic platform driver
Aug 28 17:53:56 node-1 kernel: [    1.272514] uhci_hcd: USB Universal Host Controller Interface driver
Aug 28 17:53:56 node-1 kernel: [    1.277847] i8042: PNP: No PS/2 controller found. Probing ports directly.
Aug 28 17:53:56 node-1 kernel: [    1.470883] usb 1-1: new high-speed USB device number 2 using ehci-pci
Aug 28 17:53:56 node-1 kernel: [    1.631115] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Aug 28 17:53:56 node-1 kernel: [    1.636685] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 28 17:53:56 node-1 kernel: [    1.642382] hub 1-1:1.0: USB hub found
Aug 28 17:53:56 node-1 kernel: [    1.647852] hub 1-1:1.0: 6 ports detected
Aug 28 17:53:56 node-1 kernel: [    1.762629] usb 2-1: new high-speed USB device number 2 using ehci-pci
Aug 28 17:53:56 node-1 kernel: [    1.770659] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Aug 28 17:53:56 node-1 kernel: [    2.030777] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Aug 28 17:53:56 node-1 kernel: [    2.036300] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 28 17:53:56 node-1 kernel: [    2.042166] hub 2-1:1.0: USB hub found
Aug 28 17:53:56 node-1 kernel: [    2.047763] hub 2-1:1.0: 8 ports detected
Aug 28 17:53:56 node-1 kernel: [    2.319605] i8042: No controller found
Aug 28 17:53:56 node-1 kernel: [    2.325054] mousedev: PS/2 mouse device common for all mice
Aug 28 17:53:56 node-1 kernel: [    2.326233] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Aug 28 17:53:56 node-1 kernel: [    2.336120] rtc_cmos 00:02: RTC can wake from S4
Aug 28 17:53:56 node-1 kernel: [    2.341832] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Aug 28 17:53:56 node-1 kernel: [    2.347433] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Aug 28 17:53:56 node-1 kernel: [    2.358478] device-mapper: uevent: version 1.0.3
Aug 28 17:53:56 node-1 kernel: [    2.364096] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Aug 28 17:53:56 node-1 kernel: [    2.375283] ledtrig-cpu: registered to indicate activity on CPUs
Aug 28 17:53:56 node-1 kernel: [    2.381195] TCP: cubic registered
Aug 28 17:53:56 node-1 kernel: [    2.387069] NET: Registered protocol family 10
Aug 28 17:53:56 node-1 kernel: [    2.393054] NET: Registered protocol family 17
Aug 28 17:53:56 node-1 kernel: [    2.398711] Key type dns_resolver registered
Aug 28 17:53:56 node-1 kernel: [    2.404662] Loading compiled-in X.509 certificates
Aug 28 17:53:56 node-1 kernel: [    2.410819] Loaded X.509 cert 'Magrathea: Glacier signing key: d5fcc7f0ec194773d05665948935931e3b1336a9'
Aug 28 17:53:56 node-1 kernel: [    2.422176] registered taskstats version 1
Aug 28 17:53:56 node-1 kernel: [    2.430092] Key type trusted registered
Aug 28 17:53:56 node-1 kernel: [    2.437633] Key type encrypted registered
Aug 28 17:53:56 node-1 kernel: [    2.443090] AppArmor: AppArmor sha1 policy hashing enabled
Aug 28 17:53:56 node-1 kernel: [    2.448589] IMA: No TPM chip found, activating TPM-bypass!
Aug 28 17:53:56 node-1 kernel: [    2.454732] regulator-dummy: disabling
Aug 28 17:53:56 node-1 kernel: [    2.458979] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Aug 28 17:53:56 node-1 kernel: [    2.458979] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 28 17:53:56 node-1 kernel: [    2.458980] usb 2-1.4: Product: Cisco USB Composite Device-0
Aug 28 17:53:56 node-1 kernel: [    2.458981] usb 2-1.4: Manufacturer: Avocent
Aug 28 17:53:56 node-1 kernel: [    2.458982] usb 2-1.4: SerialNumber: 20111102-00000001
Aug 28 17:53:56 node-1 kernel: [    2.493767]   Magic number: 12:260:897
Aug 28 17:53:56 node-1 kernel: [    2.499404] pci 0000:ff:08.3: hash matches
Aug 28 17:53:56 node-1 kernel: [    2.505157] rtc_cmos 00:02: setting system clock to 2016-08-28 17:53:18 UTC (1472406798)
Aug 28 17:53:56 node-1 kernel: [    2.517636] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Aug 28 17:53:56 node-1 kernel: [    2.523379] EDD information not available.
Aug 28 17:53:56 node-1 kernel: [    2.529003] PM: Hibernation image not present or could not be loaded.
Aug 28 17:53:56 node-1 kernel: [    2.529858] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Aug 28 17:53:56 node-1 kernel: [    2.541232] Write protecting the kernel read-only data: 12288k
Aug 28 17:53:56 node-1 kernel: [    2.547478] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Aug 28 17:53:56 node-1 kernel: [    2.560115] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Aug 28 17:53:56 node-1 kernel: [    2.593691] device-mapper: multipath: version 1.6.0 loaded
Aug 28 17:53:56 node-1 kernel: [    2.601902] systemd-udevd[216]: starting version 204
Aug 28 17:53:56 node-1 kernel: [    2.620185] md: linear personality registered for level -1
Aug 28 17:53:56 node-1 kernel: [    2.634869] md: multipath personality registered for level -4
Aug 28 17:53:56 node-1 kernel: [    2.643087] md: raid0 personality registered for level 0
Aug 28 17:53:56 node-1 kernel: [    2.651670] md: raid1 personality registered for level 1
Aug 28 17:53:56 node-1 kernel: [    2.660784] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Aug 28 17:53:56 node-1 kernel: [    2.667285] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Aug 28 17:53:56 node-1 kernel: [    2.667315] hidraw: raw HID events driver (C) Jiri Kosina
Aug 28 17:53:56 node-1 kernel: [    2.667667] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Aug 28 17:53:56 node-1 kernel: [    2.668120] megasas: FW now in Ready state
Aug 28 17:53:56 node-1 kernel: [    2.668181] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668210] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668246] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668276] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668313] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668346] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668380] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668419] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668456] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668488] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668525] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668563] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668600] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668636] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668672] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668710] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.668872] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Aug 28 17:53:56 node-1 kernel: [    2.708501] usbcore: registered new interface driver usbhid
Aug 28 17:53:56 node-1 kernel: [    2.715081] usbhid: USB HID core driver
Aug 28 17:53:56 node-1 kernel: [    2.716052] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Aug 28 17:53:56 node-1 kernel: [    2.716058] 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
Aug 28 17:53:56 node-1 kernel: [    2.716077] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 28 17:53:56 node-1 kernel: [    2.716459] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.716596] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.716725] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.716850] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.717280] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.725912] raid6: sse2x1    2428 MB/s
Aug 28 17:53:56 node-1 kernel: [    2.734509] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Aug 28 17:53:56 node-1 kernel: [    2.734527] enic 0000:07: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
Aug 28 17:53:56 node-1 kernel: [    2.734551] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 28 17:53:56 node-1 kernel: [    2.734818] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.734892] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.735041] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.735109] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.735314] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.750974] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Aug 28 17:53:56 node-1 kernel: [    2.750980] 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
Aug 28 17:53:56 node-1 kernel: [    2.751005] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 28 17:53:56 node-1 kernel: [    2.751353] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.751474] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.751596] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.751710] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.751975] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.765141] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Aug 28 17:53:56 node-1 kernel: [    2.765142] 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
Aug 28 17:53:56 node-1 kernel: [    2.765167] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 28 17:53:56 node-1 kernel: [    2.765377] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.765460] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.765595] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.765712] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.766119] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 28 17:53:56 node-1 kernel: [    2.794077] raid6: sse2x2    9774 MB/s
Aug 28 17:53:56 node-1 kernel: [    2.861914] raid6: sse2x4    9762 MB/s
Aug 28 17:53:56 node-1 kernel: [    2.929642] raid6: avx2x1   14599 MB/s
Aug 28 17:53:56 node-1 kernel: [    3.001596] raid6: avx2x2   18865 MB/s
Aug 28 17:53:56 node-1 kernel: [    3.073534] raid6: avx2x4   21282 MB/s
Aug 28 17:53:56 node-1 kernel: [    3.079385] raid6: using algorithm avx2x4 (21282 MB/s)
Aug 28 17:53:56 node-1 kernel: [    3.085390] raid6: using avx2x2 recovery algorithm
Aug 28 17:53:56 node-1 kernel: [    3.091258] Switched to clocksource tsc
Aug 28 17:53:56 node-1 kernel: [    3.097458] 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
Aug 28 17:53:56 node-1 kernel: [    3.109451] xor: automatically using best checksumming function:
Aug 28 17:53:56 node-1 kernel: [    3.109827] 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
Aug 28 17:53:56 node-1 kernel: [    3.110902] 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
Aug 28 17:53:56 node-1 kernel: [    3.111764] 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
Aug 28 17:53:56 node-1 kernel: [    3.112695] 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
Aug 28 17:53:56 node-1 kernel: [    3.113585] 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
Aug 28 17:53:56 node-1 kernel: [    3.137499] megasas:IOC Init cmd success
Aug 28 17:53:56 node-1 kernel: [    3.185477] megasas: INIT adapter done
Aug 28 17:53:56 node-1 kernel: [    3.221396]    avx       : 36873.000 MB/sec
Aug 28 17:53:56 node-1 kernel: [    3.228222] async_tx: api initialized (async)
Aug 28 17:53:56 node-1 kernel: [    3.237912] md: raid6 personality registered for level 6
Aug 28 17:53:56 node-1 kernel: [    3.243832] md: raid5 personality registered for level 5
Aug 28 17:53:56 node-1 kernel: [    3.249536] md: raid4 personality registered for level 4
Aug 28 17:53:56 node-1 kernel: [    3.258310] md: raid10 personality registered for level 10
Aug 28 17:53:56 node-1 kernel: [    3.261622] megaraid_sas 0000:01:00.0: Controller type: iMR
Aug 28 17:53:56 node-1 kernel: [    3.263508] scsi0 : LSI SAS based MegaRAID driver
Aug 28 17:53:56 node-1 kernel: [    3.271134] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 28 17:53:56 node-1 kernel: [    3.303199] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 28 17:53:56 node-1 kernel: [    3.321183] sd 0:2:0:0: Attached scsi generic sg0 type 0
Aug 28 17:53:56 node-1 kernel: [    3.322325] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Aug 28 17:53:56 node-1 kernel: [    3.323031] sd 0:2:0:0: [sda] Write Protect is off
Aug 28 17:53:56 node-1 kernel: [    3.323046] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Aug 28 17:53:56 node-1 kernel: [    3.323294] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Aug 28 17:53:56 node-1 kernel: [    3.354274]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Aug 28 17:53:56 node-1 kernel: [    3.359450] sd 0:2:0:0: [sda] Attached SCSI disk
Aug 28 17:53:56 node-1 kernel: [    3.400654] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Aug 28 17:53:56 node-1 kernel: [    3.493344] random: lvm urandom read with 24 bits of entropy available
Aug 28 17:53:56 node-1 kernel: [    3.657705] bio: create slab <bio-1> at 1
Aug 28 17:53:56 node-1 kernel: [    4.356266] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Aug 28 17:53:56 node-1 kernel: [    5.095197] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Aug 28 17:53:56 node-1 kernel: [    5.122099] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Aug 28 17:53:56 node-1 kernel: [    5.230196] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Aug 28 17:53:56 node-1 kernel: [    5.319988] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Aug 28 17:53:56 node-1 kernel: [    5.431057] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Aug 28 17:53:56 node-1 kernel: [    5.492245] random: nonblocking pool is initialized
Aug 28 17:53:56 node-1 kernel: [    5.635349] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Aug 28 17:53:56 node-1 kernel: [    5.676836] XFS (dm-0): Mounting Filesystem
Aug 28 17:53:56 node-1 kernel: [    6.040068] XFS (dm-0): Ending clean mount
Aug 28 17:53:56 node-1 kernel: [    6.089823] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Aug 28 17:53:56 node-1 kernel: [    6.131594] XFS (dm-1): Mounting Filesystem
Aug 28 17:53:56 node-1 kernel: [    6.247841] XFS (dm-1): Ending clean mount
Aug 28 17:53:56 node-1 kernel: [    7.923939] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Aug 28 17:53:56 node-1 kernel: [    7.949508] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Aug 28 17:53:56 node-1 kernel: [    8.123826] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 28 17:53:56 node-1 kernel: [    8.123829] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Aug 28 17:53:56 node-1 kernel: [    8.123832] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Aug 28 17:53:56 node-1 kernel: [    8.123835] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Aug 28 17:53:56 node-1 kernel: [    8.172644] systemd-udevd[773]: starting version 204
Aug 28 17:53:56 node-1 kernel: [    8.374666] power_meter ACPI000D:00: Found ACPI power meter.
Aug 28 17:53:56 node-1 kernel: [    8.374696] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Aug 28 17:53:56 node-1 kernel: [    8.381740] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Aug 28 17:53:56 node-1 kernel: [    8.381747] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 28 17:53:56 node-1 kernel: [    8.381750] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Aug 28 17:53:56 node-1 kernel: [    8.381754] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 28 17:53:56 node-1 kernel: [    8.381812] lpc_ich: Resource conflict(s) found affecting gpio_ich
Aug 28 17:53:56 node-1 kernel: [    8.392763] wmi: Mapper loaded
Aug 28 17:53:56 node-1 kernel: [    8.406316] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Aug 28 17:53:56 node-1 kernel: [    8.408714] IPMI System Interface driver.
Aug 28 17:53:56 node-1 kernel: [    8.408753] ipmi_si: probing via ACPI
Aug 28 17:53:56 node-1 kernel: [    8.408768] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Aug 28 17:53:56 node-1 kernel: [    8.408769] ipmi_si: Adding ACPI-specified kcs state machine
Aug 28 17:53:56 node-1 kernel: [    8.408777] ipmi_si: probing via SMBIOS
Aug 28 17:53:56 node-1 kernel: [    8.408778] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Aug 28 17:53:56 node-1 kernel: [    8.408779] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Aug 28 17:53:56 node-1 kernel: [    8.408782] ipmi_si: probing via SPMI
Aug 28 17:53:56 node-1 kernel: [    8.408783] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Aug 28 17:53:56 node-1 kernel: [    8.408784] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Aug 28 17:53:56 node-1 kernel: [    8.408785] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Aug 28 17:53:56 node-1 kernel: [    8.477442] systemd-udevd[801]: renamed network interface eth1 to enp7s0
Aug 28 17:53:56 node-1 kernel: [    8.505351] systemd-udevd[791]: renamed network interface eth0 to enp6s0
Aug 28 17:53:56 node-1 kernel: [    8.537258] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Aug 28 17:53:56 node-1 kernel: [    8.545257] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Aug 28 17:53:56 node-1 kernel: [    8.545265] ipmi_si 00:09: IPMI kcs interface initialized
Aug 28 17:53:56 node-1 kernel: [    8.581367] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Aug 28 17:53:56 node-1 kernel: [    8.867495] type=1400 audit(1472406804.863:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1031 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.867655] type=1400 audit(1472406804.863:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1031 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.867784] type=1400 audit(1472406804.863:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1031 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.869191] type=1400 audit(1472406804.867:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1030 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.869338] type=1400 audit(1472406804.867:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1030 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.869468] type=1400 audit(1472406804.867:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1030 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.883354] type=1400 audit(1472406804.879:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1025 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.883493] type=1400 audit(1472406804.879:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1025 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.883613] type=1400 audit(1472406804.879:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1025 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    8.919551] type=1400 audit(1472406804.915:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1029 comm="apparmor_parser"
Aug 28 17:53:56 node-1 kernel: [    9.527205] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Aug 28 17:53:56 node-1 kernel: [    9.540978] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Aug 28 17:53:56 node-1 kernel: [    9.714532] enic 0000:06:00.0 enp6s0: Link UP
Aug 28 17:53:56 node-1 kernel: [    9.715750] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Aug 28 17:53:56 node-1 kernel: [    9.715755] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Aug 28 17:53:56 node-1 kernel: [   18.734311] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Aug 28 17:53:57 node-1 failsafe: Failsafe of 120 seconds reached.
Aug 28 17:53:57 node-1 kernel: [   41.968416] init: failsafe main process (8407) killed by TERM signal
Aug 28 17:53:57 node-1 dbus[8435]: [system] AppArmor D-Bus mediation is enabled
Aug 28 17:53:58 node-1 kernel: [   42.236119] audit_printk_skb: 30 callbacks suppressed
Aug 28 17:53:58 node-1 kernel: [   42.236121] type=1400 audit(1472406838.062:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8532 comm="apparmor_parser"
Aug 28 17:53:58 node-1 kernel: [   42.236125] type=1400 audit(1472406838.062:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8532 comm="apparmor_parser"
Aug 28 17:53:58 node-1 kernel: [   42.236128] type=1400 audit(1472406838.062:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8532 comm="apparmor_parser"
Aug 28 17:53:58 node-1 kernel: [   42.236300] type=1400 audit(1472406838.066:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8533 comm="apparmor_parser"
Aug 28 17:53:58 node-1 kernel: [   42.236489] type=1400 audit(1472406838.066:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8532 comm="apparmor_parser"
Aug 28 17:53:58 node-1 kernel: [   42.236494] type=1400 audit(1472406838.066:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8532 comm="apparmor_parser"
Aug 28 17:53:58 node-1 kernel: [   42.236677] type=1400 audit(1472406838.066:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8532 comm="apparmor_parser"
Aug 28 17:53:58 node-1 kernel: [   42.322459] type=1400 audit(1472406838.150:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8535 comm="apparmor_parser"
Aug 28 17:53:58 node-1 anacron[8596]: Anacron 2.3 started on 2016-08-28
Aug 28 17:53:58 node-1 anacron[8596]: Will run job `cron.daily' in 5 min.
Aug 28 17:53:58 node-1 anacron[8596]: Will run job `cron.weekly' in 10 min.
Aug 28 17:53:58 node-1 anacron[8596]: Will run job `cron.monthly' in 15 min.
Aug 28 17:53:58 node-1 anacron[8596]: Jobs will be executed sequentially
Aug 28 17:53:58 node-1 cron[8565]: (CRON) INFO (pidfile fd = 3)
Aug 28 17:53:58 node-1 multipathd: path checkers start up
Aug 28 17:53:58 node-1 cron[8638]: (CRON) STARTUP (fork ok)
Aug 28 17:53:58 node-1 cron[8638]: (CRON) INFO (Running @reboot jobs)
Aug 28 17:53:58 node-1 postfix/master[8744]: daemon started -- version 2.11.0, configuration /etc/postfix
Aug 28 17:54:01 node-1 CRON[8919]: (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")
Aug 28 17:54:02 node-1 puppet-agent[8939]: Reopening log files
Aug 28 17:54:03 node-1 puppet-agent[8939]: Could not request certificate: Connection refused - connect(2)
Aug 28 17:54:09 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 28 17:54:09 node-1 nailgun-agent: D, [2016-08-28T17:54:01.570895 #8922] DEBUG -- : Sleep for 8 seconds before sending request
Aug 28 17:54:09 node-1 nailgun-agent: I, [2016-08-28T17:54:09.607648 #8922]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 28 17:54:10 node-1 nailgun-agent: D, [2016-08-28T17:54:10.455890 #8922] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Aug 28 17:54:13 node-1 puppet-user[9147]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Aug 28 17:54:13 node-1 puppet-user[9147]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Aug 28 17:54:14 node-1 puppet-user[9147]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Aug 28 17:54:14 node-1 puppet-user[9147]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Aug 28 17:54:14 node-1 puppet-user[9147]: Finished catalog run in 0.91 seconds
Aug 28 17:54:16 node-1 multipathd: uevent trigger error
Aug 28 17:54:16 node-1 puppet-user[9567]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 28 17:54:16 node-1 puppet-user[9567]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Aug 28 17:54:16 node-1 puppet-user[9567]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Aug 28 17:54:16 node-1 puppet-user[9567]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Aug 28 17:54:16 node-1 puppet-user[9567]: (/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"]'
Aug 28 17:54:16 node-1 puppet-user[9567]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Aug 28 17:54:16 node-1 puppet-user[9567]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Aug 28 17:54:16 node-1 puppet-user[9567]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Aug 28 17:54:16 node-1 puppet-user[9567]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Aug 28 17:54:16 node-1 puppet-user[9567]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Aug 28 17:54:16 node-1 puppet-user[9567]: Finished catalog run in 0.07 seconds
Aug 28 17:54:18 node-1 puppet-user[10037]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Aug 28 17:54:18 node-1 puppet-user[10037]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Aug 28 17:54:18 node-1 puppet-user[10037]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Aug 28 17:54:18 node-1 puppet-user[10037]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Aug 28 17:54:18 node-1 puppet-user[10037]: Finished catalog run in 0.03 seconds
Aug 28 17:54:20 node-1 puppet-user[10628]: (Scope(Class[main])) MODULAR: configuration_symlink
Aug 28 17:54:20 node-1 puppet-user[10628]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Aug 28 17:54:20 node-1 puppet-user[10628]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Aug 28 17:54:20 node-1 puppet-user[10628]: Finished catalog run in 0.04 seconds
Aug 28 17:54:21 node-1 puppet-user[11101]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Aug 28 17:54:21 node-1 puppet-user[11101]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Aug 28 17:54:22 node-1 puppet-user[11101]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Aug 28 17:54:22 node-1 puppet-user[11101]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.589426 #8922] DEBUG -- : Trying to find block devices
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.589512 #8922] DEBUG -- : Found block device: sda
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.589550 #8922] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.589573 #8922] DEBUG -- : Trying to get list of physical devices
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.589718 #8922] DEBUG -- : Getting udev properties for device: sda
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.591452 #8922] 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
Aug 28 17:54:22 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16437", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.591478 #8922] DEBUG -- : Trying to find out if device sda is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.591521 #8922] DEBUG -- : Device sda removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.591536 #8922] DEBUG -- : Device sda seems to be appropriate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.591969 #8922] DEBUG -- : Getting udev properties for device: dm-0
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.593554 #8922] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-Ryqssls9fjxnxBw9CvFYT08ertwgMbPePvXX5OyXwjf0xOZmRvUjdOcXPTWCgt1w /dev/disk/by-uuid/721ce9ac-7c81-49ca-ac99-c99c2ad0eccd /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-Ryqssls9fjxnxBw9CvFYT08ertwgMbPePvXX5OyXwjf0xOZmRvUjdOcXPTWCgt1w", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"721ce9ac-7c81-49ca-ac99-c99c2ad0eccd", "ID_FS_UUID_ENC"=>"721ce9ac-7c81-49ca-ac99-c99c2ad0eccd", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16599", "nomdmonddf"=>"1", "nomd
Aug 28 17:54:22 node-1 nailgun-agent: monisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.593580 #8922] DEBUG -- : Trying to find out if device dm-0 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.593630 #8922] DEBUG -- : Device dm-0 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.593645 #8922] DEBUG -- : Device dm-0 seems to be appropriate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.593658 #8922] DEBUG -- : Getting udev properties for device: dm-1
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.595904 #8922] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-oIrwjaeZhQo1oabHsLDBg2Cm6D2rlXleFBR3sPVbTReU7stfFtgeeEfXIqFjgqTv /dev/disk/by-uuid/4b65f3b0-0d8d-495d-bb6b-981804b6d8e5 /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-oIrwjaeZhQo1oabHsLDBg2Cm6D2rlXleFBR3sPVbTReU7stfFtgeeEfXIqFjgqTv", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4b65f3b0-0d8d-495d-bb6b-981804b6d8e5", "ID_FS_UUID_ENC"=>"4b65f3b0-0d8d-495d-bb6b-981804b6d8e5", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56
Aug 28 17:54:22 node-1 nailgun-agent: 729", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.595934 #8922] DEBUG -- : Trying to find out if device dm-1 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.595977 #8922] DEBUG -- : Device dm-1 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.595990 #8922] DEBUG -- : Device dm-1 seems to be appropriate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.596005 #8922] DEBUG -- : Getting udev properties for device: dm-2
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.597561 #8922] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-1MjnM9NkE0KoZ5OZ7EbQzBbC1gdsKkHFkhsWvpPtFJRGWzNupbNtAnPSZsqvxtfD /dev/disk/by-uuid/52629967-2cd2-48f6-a219-c1249767644a /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-1MjnM9NkE0KoZ5OZ7EbQzBbC1gdsKkHFkhsWvpPtFJRGWzNupbNtAnPSZsqvxtfD", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"52629967-2cd2-48f6-a219-c1249767644a", "ID_FS_UUID_ENC"=>"52629967-2cd2-48f6-a219-c1249767644a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"67586", "nomdmond
Aug 28 17:54:22 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.597587 #8922] DEBUG -- : Trying to find out if device dm-2 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.597654 #8922] DEBUG -- : Device dm-2 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.597667 #8922] DEBUG -- : Device dm-2 seems to be appropriate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.597681 #8922] DEBUG -- : Getting udev properties for device: dm-3
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.599233 #8922] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-zC2C3dXg8FlzgYnCUPFFtDpG1tCVCJ6YLgGb77SyQObC6q9EZJh49i9YHb80AlPO /dev/disk/by-uuid/cdca8583-d767-4a22-8862-199b4eefc9c9 /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-zC2C3dXg8FlzgYnCUPFFtDpG1tCVCJ6YLgGb77SyQObC6q9EZJh49i9YHb80AlPO", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cdca8583-d767-4a22-8862-199b4eefc9c9", "ID_FS_UUID_ENC"=>"cdca8583-d767-4a22-8862-199b4eefc9c9", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70988", "nomdmonddf"=>"1", 
Aug 28 17:54:22 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.599272 #8922] DEBUG -- : Trying to find out if device dm-3 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.599303 #8922] DEBUG -- : Device dm-3 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.599317 #8922] DEBUG -- : Device dm-3 seems to be appropriate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.599332 #8922] DEBUG -- : Getting udev properties for device: dm-4
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.600883 #8922] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-a67fnVR02TFLpQ08ZSPaTQiWfiZMQ0SnMOAgpn63U10igXNmvtTDELhP8Ffgozru /dev/disk/by-uuid/540d1894-ff07-4e50-8ea5-5d0514ec9fa3 /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-a67fnVR02TFLpQ08ZSPaTQiWfiZMQ0SnMOAgpn63U10igXNmvtTDELhP8Ffgozru", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"540d1894-ff07-4e50-8ea5-5d0514ec9fa3", "ID_FS_UUID_ENC"=>"540d1894-ff07-4e50-8ea5-5d0514ec9fa3", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90118", "nomdmonddf"=>"1", "nomd
Aug 28 17:54:22 node-1 nailgun-agent: monisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.600911 #8922] DEBUG -- : Trying to find out if device dm-4 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.600977 #8922] DEBUG -- : Device dm-4 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.600991 #8922] DEBUG -- : Device dm-4 seems to be appropriate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.601006 #8922] DEBUG -- : Getting udev properties for device: dm-5
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.602583 #8922] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-a67fnVR02TFLpQ08ZSPaTQiWfiZMQ0SncqKkktxvhZ1xKixMzTbi6rplWKhj3v8d /dev/disk/by-uuid/437fa0d9-5fc0-4e06-b3e7-ecbcd2943d44 /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-a67fnVR02TFLpQ08ZSPaTQiWfiZMQ0SncqKkktxvhZ1xKixMzTbi6rplWKhj3v8d", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"437fa0d9-5fc0-4e06-b3e7-ecbcd2943d44", "ID_FS_UUID_ENC"=>"437fa0d9-5fc0-4e06-b3e7-ecbcd2943d44", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90566", "nomdmonddf"=>"1", "nomdmonisw"
Aug 28 17:54:22 node-1 nailgun-agent: =>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.602622 #8922] DEBUG -- : Trying to find out if device dm-5 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.602682 #8922] DEBUG -- : Device dm-5 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.602697 #8922] DEBUG -- : Device dm-5 seems to be appropriate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.602712 #8922] DEBUG -- : Getting udev properties for device: ram0
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.604134 #8922] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87450", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.604171 #8922] DEBUG -- : Trying to find out if device ram0 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.604211 #8922] DEBUG -- : Device ram0 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.604245 #8922] DEBUG -- : Getting udev properties for device: ram1
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.605646 #8922] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87543", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.605671 #8922] DEBUG -- : Trying to find out if device ram1 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.605706 #8922] DEBUG -- : Device ram1 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.605743 #8922] DEBUG -- : Getting udev properties for device: ram2
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.607159 #8922] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88681", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.607184 #8922] DEBUG -- : Trying to find out if device ram2 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.607224 #8922] DEBUG -- : Device ram2 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.607244 #8922] DEBUG -- : Getting udev properties for device: ram3
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.608640 #8922] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88815", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.608673 #8922] DEBUG -- : Trying to find out if device ram3 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.608722 #8922] DEBUG -- : Device ram3 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.608742 #8922] DEBUG -- : Getting udev properties for device: ram4
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.610136 #8922] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88895", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.610162 #8922] DEBUG -- : Trying to find out if device ram4 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.610197 #8922] DEBUG -- : Device ram4 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.610232 #8922] DEBUG -- : Getting udev properties for device: ram5
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.611623 #8922] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89001", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.611648 #8922] DEBUG -- : Trying to find out if device ram5 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.611681 #8922] DEBUG -- : Device ram5 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.611712 #8922] DEBUG -- : Getting udev properties for device: ram6
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.613104 #8922] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89126", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.613128 #8922] DEBUG -- : Trying to find out if device ram6 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.613178 #8922] DEBUG -- : Device ram6 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.613198 #8922] DEBUG -- : Getting udev properties for device: ram7
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.614588 #8922] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89209", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.614624 #8922] DEBUG -- : Trying to find out if device ram7 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.614667 #8922] DEBUG -- : Device ram7 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.614687 #8922] DEBUG -- : Getting udev properties for device: ram8
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.616084 #8922] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89307", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.616109 #8922] DEBUG -- : Trying to find out if device ram8 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.616141 #8922] DEBUG -- : Device ram8 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.616161 #8922] DEBUG -- : Getting udev properties for device: ram9
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.617541 #8922] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89390", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.617580 #8922] DEBUG -- : Trying to find out if device ram9 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.617643 #8922] DEBUG -- : Device ram9 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.617664 #8922] DEBUG -- : Getting udev properties for device: loop0
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.619080 #8922] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86666", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.619106 #8922] DEBUG -- : Trying to find out if device loop0 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.619141 #8922] DEBUG -- : Device loop0 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.619167 #8922] DEBUG -- : Getting udev properties for device: loop1
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.620543 #8922] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86748", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.620580 #8922] DEBUG -- : Trying to find out if device loop1 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.620613 #8922] DEBUG -- : Device loop1 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.620638 #8922] DEBUG -- : Getting udev properties for device: loop2
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.622036 #8922] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86863", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.622071 #8922] DEBUG -- : Trying to find out if device loop2 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.622120 #8922] DEBUG -- : Device loop2 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.622139 #8922] DEBUG -- : Getting udev properties for device: loop3
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.623547 #8922] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86956", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.623571 #8922] DEBUG -- : Trying to find out if device loop3 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.623643 #8922] DEBUG -- : Device loop3 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.623663 #8922] DEBUG -- : Getting udev properties for device: loop4
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.625142 #8922] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87052", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.625182 #8922] DEBUG -- : Trying to find out if device loop4 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.625224 #8922] DEBUG -- : Device loop4 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.625243 #8922] DEBUG -- : Getting udev properties for device: loop5
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.626640 #8922] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87115", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.626665 #8922] DEBUG -- : Trying to find out if device loop5 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.626698 #8922] DEBUG -- : Device loop5 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.626717 #8922] DEBUG -- : Getting udev properties for device: loop6
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.628121 #8922] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87185", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.628147 #8922] DEBUG -- : Trying to find out if device loop6 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.628192 #8922] DEBUG -- : Device loop6 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.628211 #8922] DEBUG -- : Getting udev properties for device: loop7
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.629603 #8922] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87299", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.629640 #8922] DEBUG -- : Trying to find out if device loop7 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.629673 #8922] DEBUG -- : Device loop7 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.629711 #8922] DEBUG -- : Getting udev properties for device: ram10
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.635378 #8922] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87679", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.635407 #8922] DEBUG -- : Trying to find out if device ram10 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.635449 #8922] DEBUG -- : Device ram10 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.635469 #8922] DEBUG -- : Getting udev properties for device: ram11
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.636972 #8922] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87791", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.637029 #8922] DEBUG -- : Trying to find out if device ram11 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.637068 #8922] DEBUG -- : Device ram11 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.637087 #8922] DEBUG -- : Getting udev properties for device: ram12
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.638447 #8922] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87871", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.638473 #8922] DEBUG -- : Trying to find out if device ram12 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.638541 #8922] DEBUG -- : Device ram12 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.638560 #8922] DEBUG -- : Getting udev properties for device: ram13
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.639938 #8922] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88347", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.639965 #8922] DEBUG -- : Trying to find out if device ram13 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.639999 #8922] DEBUG -- : Device ram13 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.640046 #8922] DEBUG -- : Getting udev properties for device: ram14
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.641404 #8922] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88465", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.641431 #8922] DEBUG -- : Trying to find out if device ram14 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.641462 #8922] DEBUG -- : Device ram14 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.641481 #8922] DEBUG -- : Getting udev properties for device: ram15
Aug 28 17:54:22 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.642832 #8922] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88558", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.642857 #8922] DEBUG -- : Trying to find out if device ram15 is removable or not
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.642888 #8922] DEBUG -- : Device ram15 removable parameter: "0"
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.642922 #8922] 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"}]
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.642936 #8922] DEBUG -- : Block device seems to be physical data storage: sda
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.642975 #8922] DEBUG -- : Found block device: dm-0
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643012 #8922] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643038 #8922] DEBUG -- : Found block device: dm-1
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643049 #8922] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643058 #8922] DEBUG -- : Found block device: dm-2
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643067 #8922] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643075 #8922] DEBUG -- : Found block device: dm-3
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643084 #8922] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643094 #8922] DEBUG -- : Found block device: dm-4
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643105 #8922] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643113 #8922] DEBUG -- : Found block device: dm-5
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643150 #8922] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643160 #8922] DEBUG -- : Found block device: ram0
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643169 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643177 #8922] DEBUG -- : Found block device: ram1
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643186 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643195 #8922] DEBUG -- : Found block device: ram2
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643204 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643212 #8922] DEBUG -- : Found block device: ram3
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643221 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643229 #8922] DEBUG -- : Found block device: ram4
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643238 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643277 #8922] DEBUG -- : Found block device: ram5
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643287 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643295 #8922] DEBUG -- : Found block device: ram6
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643303 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643312 #8922] DEBUG -- : Found block device: ram7
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643323 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643331 #8922] DEBUG -- : Found block device: ram8
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643340 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643348 #8922] DEBUG -- : Found block device: ram9
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643357 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643402 #8922] DEBUG -- : Found block device: loop0
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643412 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643420 #8922] DEBUG -- : Found block device: loop1
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643429 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643437 #8922] DEBUG -- : Found block device: loop2
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643446 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643454 #8922] DEBUG -- : Found block device: loop3
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643463 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643471 #8922] DEBUG -- : Found block device: loop4
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643517 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643526 #8922] DEBUG -- : Found block device: loop5
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643536 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643544 #8922] DEBUG -- : Found block device: loop6
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643553 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643561 #8922] DEBUG -- : Found block device: loop7
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643570 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643577 #8922] DEBUG -- : Found block device: ram10
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643587 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643625 #8922] DEBUG -- : Found block device: ram11
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643635 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643643 #8922] DEBUG -- : Found block device: ram12
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643652 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643660 #8922] DEBUG -- : Found block device: ram13
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643669 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643677 #8922] DEBUG -- : Found block device: ram14
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643686 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643694 #8922] DEBUG -- : Found block device: ram15
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643705 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.643769 #8922] 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}]
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.727035 #8922] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Aug 28 17:54:22 node-1 nailgun-agent: D, [2016-08-28T17:54:22.727112 #8922] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Aug 28 17:54:22 node-1 puppet-user[11101]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Aug 28 17:54:23 node-1 puppet-user[11101]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Aug 28 17:54:23 node-1 puppet-user[11101]: Finished catalog run in 1.18 seconds
Aug 28 17:54:24 node-1 puppet-user[11819]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Aug 28 17:54:24 node-1 puppet-user[11819]: Compiled catalog for node-1.domain.tld in environment production in 0.24 seconds
Aug 28 17:54:24 node-1 puppet-user[11819]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Aug 28 17:54:24 node-1 puppet-user[11819]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Aug 28 17:54:24 node-1 puppet-user[11819]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Aug 28 17:54:24 node-1 puppet-user[11819]: (/Stage[main]/Apt/File[preferences]/ensure) created
Aug 28 17:54:24 node-1 puppet-user[11819]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Aug 28 17:54:25 node-1 puppet-user[11819]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Aug 28 17:54:25 node-1 puppet-user[11819]: Finished catalog run in 0.34 seconds
Aug 28 17:54:26 node-1 puppet-user[12310]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Aug 28 17:54:26 node-1 puppet-user[12310]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Aug 28 17:54:27 node-1 puppet-user[12310]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Aug 28 17:54:27 node-1 kernel: [   71.253708] nr_pdflush_threads exported in /proc is scheduled for removal
Aug 28 17:54:27 node-1 kernel: [   71.253757] 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.
Aug 28 17:54:27 node-1 puppet-user[12310]: (/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'
Aug 28 17:54:27 node-1 puppet-user[12310]: Finished catalog run in 0.05 seconds
Aug 28 17:54:28 node-1 puppet-user[12771]: (Scope(Class[main])) MODULAR: sync_time
Aug 28 17:54:29 node-1 puppet-user[12771]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Aug 28 17:54:29 node-1 ntpdate[13196]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Aug 28 17:54:34 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622102 #8922] DEBUG -- : Trying to find block devices
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622182 #8922] DEBUG -- : Found block device: sda
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622209 #8922] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622226 #8922] DEBUG -- : Block device seems to be physical data storage: sda
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622259 #8922] DEBUG -- : Found block device: dm-0
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622272 #8922] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622282 #8922] DEBUG -- : Found block device: dm-1
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622292 #8922] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622313 #8922] DEBUG -- : Found block device: dm-2
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622324 #8922] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622333 #8922] DEBUG -- : Found block device: dm-3
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622343 #8922] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622353 #8922] DEBUG -- : Found block device: dm-4
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622379 #8922] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622399 #8922] DEBUG -- : Found block device: dm-5
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622409 #8922] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622418 #8922] DEBUG -- : Found block device: ram0
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622428 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622436 #8922] DEBUG -- : Found block device: ram1
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622445 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622454 #8922] DEBUG -- : Found block device: ram2
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622463 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622471 #8922] DEBUG -- : Found block device: ram3
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622480 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622505 #8922] DEBUG -- : Found block device: ram4
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622514 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622522 #8922] DEBUG -- : Found block device: ram5
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622531 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622539 #8922] DEBUG -- : Found block device: ram6
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622548 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622556 #8922] DEBUG -- : Found block device: ram7
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622565 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622573 #8922] DEBUG -- : Found block device: ram8
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622601 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622610 #8922] DEBUG -- : Found block device: ram9
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622619 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622627 #8922] DEBUG -- : Found block device: loop0
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622636 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622645 #8922] DEBUG -- : Found block device: loop1
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622654 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622686 #8922] DEBUG -- : Found block device: loop2
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622697 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622706 #8922] DEBUG -- : Found block device: loop3
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622715 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622723 #8922] DEBUG -- : Found block device: loop4
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622732 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622740 #8922] DEBUG -- : Found block device: loop5
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622749 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622782 #8922] DEBUG -- : Found block device: loop6
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622792 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622800 #8922] DEBUG -- : Found block device: loop7
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622809 #8922] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622817 #8922] DEBUG -- : Found block device: ram10
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622826 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622835 #8922] DEBUG -- : Found block device: ram11
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622844 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622851 #8922] DEBUG -- : Found block device: ram12
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622860 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622869 #8922] DEBUG -- : Found block device: ram13
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622905 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622914 #8922] DEBUG -- : Found block device: ram14
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622923 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622931 #8922] DEBUG -- : Found block device: ram15
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622941 #8922] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.622967 #8922] 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}]
Aug 28 17:54:34 node-1 nailgun-agent: D, [2016-08-28T17:54:34.789393 #8922] DEBUG -- : Response: status: 200 body: {"id": 1}
Aug 28 17:54:34 node-1 nailgun-agent: I, [2016-08-28T17:54:34.789531 #8922]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Aug 28 17:54:35 node-1 ntpdate[13196]: adjust time server 10.20.0.2 offset 0.087980 sec
Aug 28 17:54:35 node-1 puppet-user[12771]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Aug 28 17:54:35 node-1 puppet-user[12771]: Finished catalog run in 6.18 seconds
Aug 28 17:54:43 node-1 kernel: [   87.891803] init: plymouth-upstart-bridge main process ended, respawning
Aug 28 17:54:43 node-1 puppet-agent[8939]: Could not run: SIGTERM
Aug 28 17:54:44 node-1 kernel: [   88.170681] ip_tables: (C) 2000-2006 Netfilter Core Team
Aug 28 17:54:44 node-1 ec2: 
Aug 28 17:54:44 node-1 ec2: #############################################################
Aug 28 17:54:44 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Aug 28 17:54:44 node-1 ec2: 1024 0e:0a:e9:60:a9:95:32:ae:44:9d:3a:0b:ec:ac:a2:60  root@node-1.domain.tld (DSA)
Aug 28 17:54:44 node-1 ec2: 256 eb:7d:bd:d3:4b:5e:f9:6f:c3:92:8d:fa:d2:be:06:1c  root@node-1.domain.tld (ECDSA)
Aug 28 17:54:44 node-1 ec2: 256 5e:1c:12:fa:e0:65:02:30:69:3a:56:37:55:8c:0c:8f  root@node-1.domain.tld (ED25519)
Aug 28 17:54:44 node-1 ec2: 2048 a9:d5:c5:cf:49:1d:91:c6:ac:3d:23:cd:8e:56:95:38  root@node-1.domain.tld (RSA)
Aug 28 17:54:44 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Aug 28 17:54:44 node-1 ec2: #############################################################
Aug 28 17:55:01 node-1 CRON[13842]: (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")
Aug 28 17:55:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 28 17:55:18 node-1 nailgun-agent: I, [2016-08-28T17:55:18.967269 #13845]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 28 17:55:25 node-1 puppet-user[14001]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 28 17:55:25 node-1 puppet-user[14001]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Aug 28 17:55:26 node-1 puppet-user[14001]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Aug 28 17:55:26 node-1 puppet-user[14001]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Aug 28 17:55:26 node-1 puppet-user[14001]: Finished catalog run in 0.07 seconds
Aug 28 17:55:27 node-1 puppet-user[14462]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Aug 28 17:55:29 node-1 puppet-user[14462]: Compiled catalog for node-1.domain.tld in environment production in 1.40 seconds
Aug 28 17:55:29 node-1 puppet-user[14462]: (/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
Aug 28 17:55:29 node-1 puppet-user[14462]: (/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
Aug 28 17:55:29 node-1 puppet-user[14462]: (/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
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/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
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/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
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Aug 28 17:55:29 node-1 puppet-user[14462]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Aug 28 17:55:31 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 28 17:55:31 node-1 nailgun-agent: I, [2016-08-28T17:55:31.984994 #13845]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Aug 28 17:55:48 node-1 puppet-user[14462]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Aug 28 17:55:48 node-1 puppet-user[14462]: Finished catalog run in 19.17 seconds
Aug 28 17:55:50 node-1 puppet-user[15566]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Aug 28 17:55:50 node-1 puppet-user[15566]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Aug 28 17:55:55 node-1 puppet-user[15566]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Aug 28 17:56:02 node-1 CRON[16756]: (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")
Aug 28 17:56:20 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 28 17:56:20 node-1 nailgun-agent: I, [2016-08-28T17:56:20.177730 #16759]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 28 17:56:26 node-1 puppet-user[15566]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Aug 28 17:56:26 node-1 puppet-user[15566]: Finished catalog run in 35.19 seconds
Aug 28 17:56:28 node-1 puppet-user[18146]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Aug 28 17:56:28 node-1 puppet-user[18146]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Aug 28 17:56:28 node-1 puppet-user[18146]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Aug 28 17:56:28 node-1 puppet-user[18146]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Aug 28 17:56:28 node-1 puppet-user[18146]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Aug 28 17:56:28 node-1 puppet-user[18146]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Aug 28 17:56:28 node-1 puppet-user[18146]: Finished catalog run in 0.10 seconds
Aug 28 17:56:30 node-1 puppet-user[18613]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Aug 28 17:56:31 node-1 puppet-user[18613]: Compiled catalog for node-1.domain.tld in environment production in 0.95 seconds
Aug 28 17:56:31 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Aug 28 17:56:31 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Aug 28 17:56:31 node-1 crontab[19053]: (root) LIST (root)
Aug 28 17:56:31 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Aug 28 17:56:31 node-1 crontab[19054]: (root) REPLACE (root)
Aug 28 17:56:33 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 28 17:56:33 node-1 nailgun-agent: I, [2016-08-28T17:56:33.183579 #16759]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Aug 28 17:56:34 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/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
Aug 28 17:56:35 node-1 puppet-user[18613]: (/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
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/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
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Aug 28 17:56:35 node-1 puppet-user[18613]: (/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
Aug 28 17:56:35 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/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
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/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
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/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
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/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
Aug 28 17:56:36 node-1 puppet-user[18613]: (/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
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Aug 28 17:56:36 node-1 puppet-user[18613]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Aug 28 17:56:36 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 28 17:56:36 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Aug 28 17:56:38 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:38 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:38 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:38 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:38 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:38 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:56 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:56 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:56 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:56 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:57 node-1 multipathd: uevent trigger error
<27>Aug 28 17:56:57 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:00 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:00 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:00 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:00 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:00 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:02 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:02 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:02 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:02 node-1 multipathd: uevent trigger error
<27>Aug 28 17:57:02 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:02 node-1 ntpdate[30595]: no servers can be used, exiting
<27>Aug 28 17:58:33 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:33 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:33 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:33 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:33 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:33 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:33 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:36 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:36 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:36 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:36 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:36 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:36 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:48 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:48 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:48 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:48 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:48 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:58:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:50 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:59 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:59 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:59 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:59 node-1 multipathd: uevent trigger error
<27>Aug 28 17:59:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:01 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 28 18:00:01 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 28 18:00:07 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 28 18:00:07 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 28 18:00:13 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 28 18:00:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 28 18:00:18 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 28 18:00:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:43 node-1 multipathd: uevent trigger error
<129>Aug 28 18:00:46 node-1 haproxy[18981]: 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>Aug 28 18:00:46 node-1 haproxy[18981]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:00:46 node-1 haproxy[18981]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:00:46 node-1 haproxy[18981]: proxy mysqld has no server available!
<27>Aug 28 18:00:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:52 node-1 multipathd: uevent trigger error
<129>Aug 28 18:00:54 node-1 haproxy[21311]: 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>Aug 28 18:00:55 node-1 haproxy[21315]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:00:55 node-1 haproxy[21315]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:00:55 node-1 haproxy[21315]: proxy mysqld has no server available!
<129>Aug 28 18:00:55 node-1 haproxy[21315]: 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>Aug 28 18:00:55 node-1 haproxy[21315]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:00:56 node-1 haproxy[21315]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:00:56 node-1 haproxy[21315]: proxy object-storage has no server available!
<27>Aug 28 18:00:57 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:57 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:57 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:57 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:57 node-1 multipathd: uevent trigger error
<27>Aug 28 18:00:57 node-1 multipathd: uevent trigger error
<129>Aug 28 18:00:59 node-1 haproxy[22556]: 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>Aug 28 18:01:00 node-1 haproxy[22560]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:00 node-1 haproxy[22560]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:00 node-1 haproxy[22560]: proxy neutron has no server available!
<129>Aug 28 18:01:00 node-1 haproxy[22560]: 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>Aug 28 18:01:00 node-1 haproxy[22560]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:00 node-1 haproxy[22560]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:00 node-1 haproxy[22560]: proxy mysqld has no server available!
<129>Aug 28 18:01:01 node-1 haproxy[22560]: 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>Aug 28 18:01:01 node-1 haproxy[22560]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:01 node-1 haproxy[22560]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:01 node-1 haproxy[22560]: proxy object-storage has no server available!
<27>Aug 28 18:01:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:02 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:05 node-1 haproxy[24004]: 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>Aug 28 18:01:05 node-1 haproxy[24004]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:05 node-1 haproxy[24004]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:05 node-1 haproxy[24004]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:05 node-1 haproxy[24004]: 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>Aug 28 18:01:05 node-1 haproxy[24004]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:05 node-1 haproxy[24004]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:05 node-1 haproxy[24004]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:06 node-1 haproxy[24010]: 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>Aug 28 18:01:06 node-1 haproxy[24010]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:06 node-1 haproxy[24010]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:06 node-1 haproxy[24010]: proxy neutron has no server available!
<129>Aug 28 18:01:06 node-1 haproxy[24010]: 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>Aug 28 18:01:06 node-1 haproxy[24010]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:06 node-1 haproxy[24010]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:06 node-1 haproxy[24010]: proxy mysqld has no server available!
<129>Aug 28 18:01:06 node-1 haproxy[24010]: 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>Aug 28 18:01:06 node-1 haproxy[24010]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:07 node-1 haproxy[24010]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:07 node-1 haproxy[24010]: proxy object-storage has no server available!
<27>Aug 28 18:01:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:08 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:10 node-1 haproxy[25286]: 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>Aug 28 18:01:10 node-1 haproxy[25286]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:10 node-1 haproxy[25286]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:10 node-1 haproxy[25286]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:10 node-1 haproxy[25286]: 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>Aug 28 18:01:10 node-1 haproxy[25286]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:10 node-1 haproxy[25286]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:10 node-1 haproxy[25286]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:10 node-1 haproxy[25286]: 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>Aug 28 18:01:11 node-1 haproxy[25290]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:11 node-1 haproxy[25290]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:11 node-1 haproxy[25290]: proxy neutron has no server available!
<129>Aug 28 18:01:11 node-1 haproxy[25290]: 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>Aug 28 18:01:11 node-1 haproxy[25290]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:11 node-1 haproxy[25290]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:11 node-1 haproxy[25290]: proxy mysqld has no server available!
<129>Aug 28 18:01:11 node-1 haproxy[25290]: 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>Aug 28 18:01:11 node-1 haproxy[25290]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:11 node-1 haproxy[25290]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:11 node-1 haproxy[25290]: proxy object-storage has no server available!
<129>Aug 28 18:01:11 node-1 haproxy[25290]: 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>Aug 28 18:01:11 node-1 haproxy[25290]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:12 node-1 haproxy[25290]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:12 node-1 haproxy[25290]: proxy aodh has no server available!
<27>Aug 28 18:01:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:13 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:15 node-1 haproxy[26676]: 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>Aug 28 18:01:15 node-1 haproxy[26676]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:15 node-1 haproxy[26676]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:15 node-1 haproxy[26676]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:15 node-1 haproxy[26676]: 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>Aug 28 18:01:15 node-1 haproxy[26676]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:15 node-1 haproxy[26676]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:15 node-1 haproxy[26676]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:15 node-1 haproxy[26676]: 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>Aug 28 18:01:16 node-1 haproxy[26685]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:16 node-1 haproxy[26685]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:16 node-1 haproxy[26685]: proxy neutron has no server available!
<129>Aug 28 18:01:16 node-1 haproxy[26685]: 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>Aug 28 18:01:16 node-1 haproxy[26685]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:16 node-1 haproxy[26685]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:16 node-1 haproxy[26685]: proxy mysqld has no server available!
<129>Aug 28 18:01:16 node-1 haproxy[26685]: 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>Aug 28 18:01:16 node-1 haproxy[26685]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:16 node-1 haproxy[26685]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:16 node-1 haproxy[26685]: proxy object-storage has no server available!
<129>Aug 28 18:01:16 node-1 haproxy[26685]: 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>Aug 28 18:01:16 node-1 haproxy[26685]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:16 node-1 haproxy[26685]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:16 node-1 haproxy[26685]: proxy aodh has no server available!
<129>Aug 28 18:01:17 node-1 haproxy[26685]: 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>Aug 28 18:01:17 node-1 haproxy[26685]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:17 node-1 haproxy[26685]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:17 node-1 haproxy[26685]: proxy ceilometer has no server available!
<27>Aug 28 18:01:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:18 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:20 node-1 haproxy[27907]: 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>Aug 28 18:01:20 node-1 haproxy[27907]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:21 node-1 haproxy[27921]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:21 node-1 haproxy[27921]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:21 node-1 haproxy[27921]: 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>Aug 28 18:01:21 node-1 haproxy[27921]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:21 node-1 haproxy[27921]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:21 node-1 haproxy[27921]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:21 node-1 haproxy[27921]: 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>Aug 28 18:01:21 node-1 haproxy[27921]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:21 node-1 haproxy[27921]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:21 node-1 haproxy[27921]: proxy neutron has no server available!
<129>Aug 28 18:01:21 node-1 haproxy[27921]: 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>Aug 28 18:01:21 node-1 haproxy[27921]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:21 node-1 haproxy[27921]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:21 node-1 haproxy[27921]: proxy mysqld has no server available!
<129>Aug 28 18:01:21 node-1 haproxy[27921]: 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>Aug 28 18:01:22 node-1 haproxy[27921]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:22 node-1 haproxy[27921]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:22 node-1 haproxy[27921]: proxy object-storage has no server available!
<129>Aug 28 18:01:22 node-1 haproxy[27921]: 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>Aug 28 18:01:22 node-1 haproxy[27921]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:22 node-1 haproxy[27921]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:22 node-1 haproxy[27921]: proxy aodh has no server available!
<129>Aug 28 18:01:22 node-1 haproxy[27921]: 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>Aug 28 18:01:22 node-1 haproxy[27921]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:22 node-1 haproxy[27921]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:22 node-1 haproxy[27921]: proxy ceilometer has no server available!
<27>Aug 28 18:01:23 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:23 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:23 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:23 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:23 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:25 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>Aug 28 18:01:26 node-1 haproxy[29164]: 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>Aug 28 18:01:26 node-1 haproxy[29164]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:26 node-1 haproxy[29164]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:26 node-1 haproxy[29164]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:26 node-1 haproxy[29164]: 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>Aug 28 18:01:26 node-1 haproxy[29164]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:26 node-1 haproxy[29164]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:26 node-1 haproxy[29164]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:26 node-1 haproxy[29164]: 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>Aug 28 18:01:26 node-1 haproxy[29164]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:26 node-1 haproxy[29164]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:26 node-1 haproxy[29164]: proxy neutron has no server available!
<129>Aug 28 18:01:26 node-1 haproxy[29164]: 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>Aug 28 18:01:26 node-1 haproxy[29164]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:27 node-1 haproxy[29164]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:27 node-1 haproxy[29164]: proxy mysqld has no server available!
<129>Aug 28 18:01:27 node-1 haproxy[29164]: 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>Aug 28 18:01:27 node-1 haproxy[29164]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:27 node-1 haproxy[29164]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:27 node-1 haproxy[29164]: proxy object-storage has no server available!
<129>Aug 28 18:01:27 node-1 haproxy[29164]: 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>Aug 28 18:01:27 node-1 haproxy[29164]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:27 node-1 haproxy[29164]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:27 node-1 haproxy[29164]: proxy aodh has no server available!
<129>Aug 28 18:01:27 node-1 haproxy[29164]: 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>Aug 28 18:01:27 node-1 haproxy[29164]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:27 node-1 haproxy[29164]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:27 node-1 haproxy[29164]: proxy ceilometer has no server available!
<27>Aug 28 18:01:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:28 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:31 node-1 haproxy[30454]: 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>Aug 28 18:01:31 node-1 haproxy[30454]: 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>Aug 28 18:01:31 node-1 haproxy[30454]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:31 node-1 haproxy[30454]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:31 node-1 haproxy[30454]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:31 node-1 haproxy[30454]: 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>Aug 28 18:01:32 node-1 haproxy[30458]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:32 node-1 haproxy[30458]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:32 node-1 haproxy[30458]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:32 node-1 haproxy[30458]: 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>Aug 28 18:01:32 node-1 haproxy[30458]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:32 node-1 haproxy[30458]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:32 node-1 haproxy[30458]: proxy glance-api has no server available!
<129>Aug 28 18:01:32 node-1 haproxy[30458]: 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>Aug 28 18:01:32 node-1 haproxy[30458]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:32 node-1 haproxy[30458]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:32 node-1 haproxy[30458]: proxy glance-glare has no server available!
<129>Aug 28 18:01:32 node-1 haproxy[30458]: 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>Aug 28 18:01:32 node-1 haproxy[30458]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:32 node-1 haproxy[30458]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:32 node-1 haproxy[30458]: proxy neutron has no server available!
<129>Aug 28 18:01:32 node-1 haproxy[30458]: 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>Aug 28 18:01:32 node-1 haproxy[30458]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:32 node-1 haproxy[30458]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:32 node-1 haproxy[30458]: proxy glance-registry has no server available!
<129>Aug 28 18:01:32 node-1 haproxy[30458]: 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>Aug 28 18:01:32 node-1 haproxy[30458]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:32 node-1 haproxy[30458]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:32 node-1 haproxy[30458]: proxy mysqld has no server available!
<129>Aug 28 18:01:33 node-1 haproxy[30458]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:33 node-1 haproxy[30458]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:33 node-1 haproxy[30458]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:33 node-1 haproxy[30458]: proxy object-storage has no server available!
<129>Aug 28 18:01:33 node-1 haproxy[30458]: 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>Aug 28 18:01:33 node-1 haproxy[30458]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:33 node-1 haproxy[30458]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:33 node-1 haproxy[30458]: proxy aodh has no server available!
<129>Aug 28 18:01:33 node-1 haproxy[30458]: 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>Aug 28 18:01:33 node-1 haproxy[30458]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:33 node-1 haproxy[30458]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:33 node-1 haproxy[30458]: proxy ceilometer has no server available!
<27>Aug 28 18:01:34 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:34 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:34 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:34 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:34 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:37 node-1 haproxy[31737]: 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>Aug 28 18:01:37 node-1 haproxy[31737]: 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>Aug 28 18:01:37 node-1 haproxy[31737]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:37 node-1 haproxy[31737]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:37 node-1 haproxy[31737]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:37 node-1 haproxy[31737]: 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>Aug 28 18:01:37 node-1 haproxy[31737]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:37 node-1 haproxy[31737]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:37 node-1 haproxy[31737]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:37 node-1 haproxy[31737]: 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>Aug 28 18:01:37 node-1 haproxy[31737]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:37 node-1 haproxy[31737]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:37 node-1 haproxy[31737]: proxy nova-api has no server available!
<129>Aug 28 18:01:37 node-1 haproxy[31737]: 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>Aug 28 18:01:37 node-1 haproxy[31737]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:37 node-1 haproxy[31737]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:37 node-1 haproxy[31737]: proxy nova-metadata-api has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:38 node-1 haproxy[31744]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:38 node-1 haproxy[31744]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:38 node-1 haproxy[31744]: proxy glance-api has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:38 node-1 haproxy[31744]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:38 node-1 haproxy[31744]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:38 node-1 haproxy[31744]: proxy glance-glare has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:38 node-1 haproxy[31744]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:38 node-1 haproxy[31744]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:38 node-1 haproxy[31744]: proxy neutron has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:38 node-1 haproxy[31744]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:38 node-1 haproxy[31744]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:38 node-1 haproxy[31744]: proxy glance-registry has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:38 node-1 haproxy[31744]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:38 node-1 haproxy[31744]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:38 node-1 haproxy[31744]: proxy mysqld has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:38 node-1 haproxy[31744]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:38 node-1 haproxy[31744]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:38 node-1 haproxy[31744]: proxy object-storage has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:38 node-1 haproxy[31744]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:38 node-1 haproxy[31744]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:38 node-1 haproxy[31744]: proxy aodh has no server available!
<129>Aug 28 18:01:38 node-1 haproxy[31744]: 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>Aug 28 18:01:39 node-1 haproxy[31744]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:39 node-1 haproxy[31744]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:39 node-1 haproxy[31744]: proxy ceilometer has no server available!
<129>Aug 28 18:01:39 node-1 haproxy[31744]: 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>Aug 28 18:01:39 node-1 haproxy[31744]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:39 node-1 haproxy[31744]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:39 node-1 haproxy[31744]: proxy nova-novncproxy has no server available!
<27>Aug 28 18:01:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:40 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:42 node-1 haproxy[528]: 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>Aug 28 18:01:42 node-1 haproxy[528]: 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>Aug 28 18:01:42 node-1 haproxy[528]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:43 node-1 haproxy[532]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:43 node-1 haproxy[532]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy nova-api has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:43 node-1 haproxy[532]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy nova-metadata-api has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:43 node-1 haproxy[532]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy cinder-api has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:43 node-1 haproxy[532]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy glance-api has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:43 node-1 haproxy[532]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy glance-glare has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:43 node-1 haproxy[532]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:43 node-1 haproxy[532]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:43 node-1 haproxy[532]: proxy neutron has no server available!
<129>Aug 28 18:01:43 node-1 haproxy[532]: 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>Aug 28 18:01:44 node-1 haproxy[532]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:44 node-1 haproxy[532]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:44 node-1 haproxy[532]: proxy glance-registry has no server available!
<129>Aug 28 18:01:44 node-1 haproxy[532]: 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>Aug 28 18:01:44 node-1 haproxy[532]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:44 node-1 haproxy[532]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:44 node-1 haproxy[532]: proxy mysqld has no server available!
<129>Aug 28 18:01:44 node-1 haproxy[532]: 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>Aug 28 18:01:44 node-1 haproxy[532]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:44 node-1 haproxy[532]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:44 node-1 haproxy[532]: proxy object-storage has no server available!
<129>Aug 28 18:01:44 node-1 haproxy[532]: 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>Aug 28 18:01:44 node-1 haproxy[532]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:44 node-1 haproxy[532]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:44 node-1 haproxy[532]: proxy aodh has no server available!
<129>Aug 28 18:01:44 node-1 haproxy[532]: 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>Aug 28 18:01:44 node-1 haproxy[532]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:44 node-1 haproxy[532]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:44 node-1 haproxy[532]: proxy ceilometer has no server available!
<129>Aug 28 18:01:44 node-1 haproxy[532]: 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>Aug 28 18:01:44 node-1 haproxy[532]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:44 node-1 haproxy[532]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:44 node-1 haproxy[532]: proxy nova-novncproxy has no server available!
<27>Aug 28 18:01:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:45 node-1 multipathd: uevent trigger error
<129>Aug 28 18:01:48 node-1 haproxy[1845]: 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>Aug 28 18:01:48 node-1 haproxy[1845]: 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>Aug 28 18:01:48 node-1 haproxy[1845]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:48 node-1 haproxy[1845]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:48 node-1 haproxy[1845]: proxy keystone-1 has no server available!
<129>Aug 28 18:01:48 node-1 haproxy[1845]: 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>Aug 28 18:01:48 node-1 haproxy[1845]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:48 node-1 haproxy[1845]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:48 node-1 haproxy[1845]: proxy keystone-2 has no server available!
<129>Aug 28 18:01:48 node-1 haproxy[1845]: 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>Aug 28 18:01:48 node-1 haproxy[1845]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:48 node-1 haproxy[1845]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:48 node-1 haproxy[1845]: proxy nova-api has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy nova-metadata-api has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy cinder-api has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy glance-api has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy glance-glare has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy neutron has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy glance-registry has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy mysqld has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy object-storage has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:49 node-1 haproxy[1849]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:49 node-1 haproxy[1849]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:49 node-1 haproxy[1849]: proxy aodh has no server available!
<129>Aug 28 18:01:49 node-1 haproxy[1849]: 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>Aug 28 18:01:50 node-1 haproxy[1849]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:50 node-1 haproxy[1849]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:50 node-1 haproxy[1849]: proxy ceilometer has no server available!
<129>Aug 28 18:01:50 node-1 haproxy[1849]: 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>Aug 28 18:01:50 node-1 haproxy[1849]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:50 node-1 haproxy[1849]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:50 node-1 haproxy[1849]: proxy heat-api has no server available!
<129>Aug 28 18:01:50 node-1 haproxy[1849]: 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>Aug 28 18:01:50 node-1 haproxy[1849]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:50 node-1 haproxy[1849]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:50 node-1 haproxy[1849]: proxy heat-api-cfn has no server available!
<129>Aug 28 18:01:50 node-1 haproxy[1849]: 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>Aug 28 18:01:50 node-1 haproxy[1849]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:50 node-1 haproxy[1849]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:50 node-1 haproxy[1849]: proxy heat-api-cloudwatch has no server available!
<129>Aug 28 18:01:50 node-1 haproxy[1849]: 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>Aug 28 18:01:50 node-1 haproxy[1849]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 28 18:01:50 node-1 haproxy[1849]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Aug 28 18:01:50 node-1 haproxy[1849]: proxy nova-novncproxy has no server available!
<27>Aug 28 18:01:51 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:51 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:51 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:51 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:51 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:51 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:51 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:55 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:55 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:55 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:55 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:55 node-1 multipathd: uevent trigger error
<27>Aug 28 18:01:55 node-1 multipathd: uevent trigger error
<27>Aug 28 18:02:07 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Aug 28 18:02:32 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Aug 28 18:02:34 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Aug 28 18:03:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:03:15 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 28 18:03:31 node-1 multipathd: uevent trigger error
<27>Aug 28 18:03:31 node-1 multipathd: uevent trigger error
<27>Aug 28 18:03:31 node-1 multipathd: uevent trigger error
<27>Aug 28 18:03:31 node-1 multipathd: uevent trigger error
<27>Aug 28 18:03:31 node-1 multipathd: uevent trigger error
<27>Aug 28 18:03:31 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:05:59 node-1 multipathd: uevent trigger error
<43>Aug 28 18:06:17 node-1 apache2_error [Sun Aug 28 18:06:11.657287 2016] [mpm_event:notice] [pid 10676:tid 140114629728128] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 28 18:06:17 node-1 apache2_error [Sun Aug 28 18:06:11.657427 2016] [core:notice] [pid 10676:tid 140114629728128] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 28 18:06:17 node-1 apache2_error [Sun Aug 28 18:06:14.674403 2016] [mpm_event:notice] [pid 10676:tid 140114629728128] AH00491: caught SIGTERM, shutting down
<43>Aug 28 18:06:17 node-1 apache2_error [Sun Aug 28 18:06:15.766014 2016] [mpm_worker:notice] [pid 11066:tid 140717018666880] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 28 18:06:17 node-1 apache2_error [Sun Aug 28 18:06:15.766081 2016] [core:notice] [pid 11066:tid 140717018666880] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 28 18:06:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:06:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:25 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:06:28 node-1 multipathd: uevent trigger error
<43>Aug 28 18:07:37 node-1 apache2_error [Sun Aug 28 18:07:37.101956 2016] [mpm_worker:notice] [pid 11066:tid 140717018666880] AH00295: caught SIGTERM, shutting down
<43>Aug 28 18:07:47 node-1 apache2_error [Sun Aug 28 18:07:37.841301 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 28 18:07:47 node-1 apache2_error [Sun Aug 28 18:07:37.841329 2016] [core:notice] [pid 25477:tid 140211483039616] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 28 18:08:27 node-1 apache2_error [Sun Aug 28 18:08:21.771137 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 28 18:08:27 node-1 apache2_error [Sun Aug 28 18:08:21.966820 2016] [mpm_worker:warn] [pid 25477:tid 140211483039616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 28 18:08:27 node-1 apache2_error [Sun Aug 28 18:08:21.971086 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 28 18:08:27 node-1 apache2_error [Sun Aug 28 18:08:21.971103 2016] [core:notice] [pid 25477:tid 140211483039616] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 28 18:09:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:12 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:12 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:12 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:09:27 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:27 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:27 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:27 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:27 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:27 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:27 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:53 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:53 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:53 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:53 node-1 multipathd: uevent trigger error
<27>Aug 28 18:09:53 node-1 multipathd: uevent trigger error
<27>Aug 28 18:10:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:10:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:10:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:10:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:10:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:11:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:11:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:11:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:11:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:11:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:11:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:12:19 node-1 multipathd: uevent trigger error
<27>Aug 28 18:12:19 node-1 multipathd: uevent trigger error
<27>Aug 28 18:12:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:12:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:12:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:12:20 node-1 multipathd: uevent trigger error
<27>Aug 28 18:12:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:13:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:18 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:24 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:24 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:24 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:24 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:24 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:46 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:46 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:46 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:46 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:46 node-1 multipathd: uevent trigger error
<27>Aug 28 18:13:46 node-1 multipathd: uevent trigger error
<27>Aug 28 18:15:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:16:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:33 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:33 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:33 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:33 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:33 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:16:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:17:48 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:18:32 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:32 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:32 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:32 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:32 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:32 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:47 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:47 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:47 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:47 node-1 multipathd: uevent trigger error
<27>Aug 28 18:18:47 node-1 multipathd: uevent trigger error
<27>Aug 28 18:19:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:19:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:19:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:19:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:19:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:27 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:21:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:28 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:43 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: uevent trigger error
<27>Aug 28 18:21:56 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Aug 28 18:22:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:22:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:45 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:49 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:23:54 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:05 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:24:37 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:37 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:37 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:37 node-1 multipathd: uevent trigger error
<27>Aug 28 18:24:37 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:41 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:41 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:41 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:41 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:41 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:41 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:59 node-1 multipathd: uevent trigger error
<27>Aug 28 18:25:59 node-1 multipathd: uevent trigger error
<11>Aug 28 18:26:13 node-1 liberasurecode[72068]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:13 node-1 liberasurecode[72068]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:13 node-1 liberasurecode[72068]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:13 node-1 liberasurecode[72068]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:13 node-1 liberasurecode[72195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:13 node-1 liberasurecode[72195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:13 node-1 liberasurecode[72195]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:13 node-1 liberasurecode[72195]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:15 node-1 liberasurecode[72866]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:15 node-1 liberasurecode[72866]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:15 node-1 liberasurecode[72866]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:15 node-1 liberasurecode[72866]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73518]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73518]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73518]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73518]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73559]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73559]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73604]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73604]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73604]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73604]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73663]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73663]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73663]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73663]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73676]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73676]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73676]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73676]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73692]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73692]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73692]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73692]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73706]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73706]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73706]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:21 node-1 liberasurecode[73706]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:30 node-1 liberasurecode[74328]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:30 node-1 liberasurecode[74328]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:30 node-1 liberasurecode[74328]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:26:30 node-1 liberasurecode[74328]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 28 18:26:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:26:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:26:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:26:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:26:38 node-1 multipathd: uevent trigger error
<43>Aug 28 18:27:29 node-1 apache2_error [Sun Aug 28 18:27:25.129057 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 28 18:27:29 node-1 apache2_error [Sun Aug 28 18:27:25.509965 2016] [mpm_worker:warn] [pid 25477:tid 140211483039616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 28 18:27:29 node-1 apache2_error [Sun Aug 28 18:27:25.512631 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 28 18:27:29 node-1 apache2_error [Sun Aug 28 18:27:25.512655 2016] [core:notice] [pid 25477:tid 140211483039616] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 28 18:27:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 28 18:28:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:06 node-1 multipathd: uevent trigger error
<43>Aug 28 18:28:09 node-1 apache2_error [Sun Aug 28 18:28:02.483986 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 28 18:28:09 node-1 apache2_error [Sun Aug 28 18:28:04.002733 2016] [mpm_worker:warn] [pid 25477:tid 140211483039616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 28 18:28:09 node-1 apache2_error [Sun Aug 28 18:28:04.016517 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 28 18:28:09 node-1 apache2_error [Sun Aug 28 18:28:04.016568 2016] [core:notice] [pid 25477:tid 140211483039616] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 28 18:28:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:13 node-1 multipathd: uevent trigger error
<43>Aug 28 18:28:49 node-1 apache2_error [Sun Aug 28 18:28:48.090196 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 28 18:28:49 node-1 apache2_error [Sun Aug 28 18:28:48.288782 2016] [mpm_worker:warn] [pid 25477:tid 140211483039616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 28 18:28:49 node-1 apache2_error [Sun Aug 28 18:28:48.298130 2016] [mpm_worker:notice] [pid 25477:tid 140211483039616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 28 18:28:49 node-1 apache2_error [Sun Aug 28 18:28:48.298163 2016] [core:notice] [pid 25477:tid 140211483039616] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 28 18:28:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:52 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:58 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:58 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:58 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:58 node-1 multipathd: uevent trigger error
<27>Aug 28 18:28:58 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:04 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:04 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:04 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:04 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:04 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:04 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:11 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:46 node-1 multipathd: uevent trigger error
<27>Aug 28 18:29:54 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<11>Aug 28 18:30:01 node-1 liberasurecode[116923]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:30:01 node-1 liberasurecode[116923]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:30:01 node-1 liberasurecode[116923]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 28 18:30:01 node-1 liberasurecode[116923]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 28 18:30:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:02 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:03 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:03 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:16 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:16 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:16 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:16 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:16 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:38 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 28 18:30:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:30:40 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:06 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:07 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:14 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:14 node-1 multipathd: uevent trigger error
<129>Aug 28 18:31:19 node-1 haproxy[1849]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Aug 28 18:31:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:26 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:31:38 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:08 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:13 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:17 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:17 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:17 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:17 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:17 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:17 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:21 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:30 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:30 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:30 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:30 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:30 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:35 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:39 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:39 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:39 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:39 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:39 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:44 node-1 multipathd: uevent trigger error
<27>Aug 28 18:32:44 node-1 multipathd: uevent trigger error
