Oct 18 16:23:31 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8394" x-info="http://www.rsyslog.com"] start
Oct 18 16:23:31 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 18 16:23:31 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 18 16:23:31 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 18 16:23:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 18 16:23:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 18 16:23:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 18 16:23:31 node-1 kernel: [    0.000000] Linux version 3.13.0-98-generic (buildd@lgw01-45) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #145-Ubuntu SMP Sat Oct 8 20:13:07 UTC 2016 (Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39)
Oct 18 16:23:31 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e5d5dd70-7afa-42cb-ad81-c1b7a3c34e21 nomdmonddf nomdmonisw
Oct 18 16:23:31 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 18 16:23:31 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 18 16:23:31 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 18 16:23:31 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 18 16:23:31 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 18 16:23:31 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 18 16:23:31 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 18 16:23:31 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct 18 16:23:31 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 18 16:23:31 node-1 kernel: [    0.000000] No AGP bridge found
Oct 18 16:23:31 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 18 16:23:31 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 18 16:23:31 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 18 16:23:31 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 18 16:23:31 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 18 16:23:31 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 18 16:23:31 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 18 16:23:31 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 18 16:23:31 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 18 16:23:31 node-1 kernel: [    0.000000]   2 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000]   3 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000]   4 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000]   5 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000]   6 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000]   7 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000]   8 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000]   9 disabled
Oct 18 16:23:31 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 18 16:23:31 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 18 16:23:31 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 18 16:23:31 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 18 16:23:31 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 18 16:23:31 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 18 16:23:31 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 18 16:23:31 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 18 16:23:31 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 18 16:23:31 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 18 16:23:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 18 16:23:31 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35828000-0x36c0bfff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 18 16:23:31 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 18 16:23:31 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 18 16:23:31 node-1 kernel: [    0.000000] Zone ranges:
Oct 18 16:23:31 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 18 16:23:31 node-1 kernel: [    0.000000] Early memory node ranges
Oct 18 16:23:31 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 18 16:23:31 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 18 16:23:31 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 18 16:23:31 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 18 16:23:31 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 18 16:23:31 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 18 16:23:31 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 18 16:23:31 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 18 16:23:31 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 18 16:23:31 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 18 16:23:31 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 18 16:23:31 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 18 16:23:31 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 18 16:23:31 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 18 16:23:31 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 18 16:23:31 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 18 16:23:31 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 18 16:23:31 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 18 16:23:31 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 18 16:23:31 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 18 16:23:31 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 18 16:23:31 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 18 16:23:31 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 18 16:23:31 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct 18 16:23:31 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 18 16:23:31 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 18 16:23:31 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=e5d5dd70-7afa-42cb-ad81-c1b7a3c34e21 nomdmonddf nomdmonisw
Oct 18 16:23:31 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 18 16:23:31 node-1 kernel: [    0.000000] Checking aperture...
Oct 18 16:23:31 node-1 kernel: [    0.000000] No AGP bridge found
Oct 18 16:23:31 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 18 16:23:31 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 18 16:23:31 node-1 kernel: [    0.000000] Memory: 32653328K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627168K reserved)
Oct 18 16:23:31 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 18 16:23:31 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 18 16:23:31 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 18 16:23:31 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 18 16:23:31 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 18 16:23:31 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 18 16:23:31 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 18 16:23:31 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 18 16:23:31 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 18 16:23:31 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 18 16:23:31 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 18 16:23:31 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 18 16:23:31 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 18 16:23:31 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 18 16:23:31 node-1 kernel: [    0.004000] tsc: Detected 3491.842 MHz processor
Oct 18 16:23:31 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.68 BogoMIPS (lpj=13967368)
Oct 18 16:23:31 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 18 16:23:31 node-1 kernel: [    0.000053] Security Framework initialized
Oct 18 16:23:31 node-1 kernel: [    0.000072] AppArmor: AppArmor initialized
Oct 18 16:23:31 node-1 kernel: [    0.000073] Yama: becoming mindful.
Oct 18 16:23:31 node-1 kernel: [    0.001470] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.006425] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.008353] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.008380] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.008657] Initializing cgroup subsys memory
Oct 18 16:23:31 node-1 kernel: [    0.008664] Initializing cgroup subsys devices
Oct 18 16:23:31 node-1 kernel: [    0.008666] Initializing cgroup subsys freezer
Oct 18 16:23:31 node-1 kernel: [    0.008668] Initializing cgroup subsys blkio
Oct 18 16:23:31 node-1 kernel: [    0.008670] Initializing cgroup subsys perf_event
Oct 18 16:23:31 node-1 kernel: [    0.008672] Initializing cgroup subsys hugetlb
Oct 18 16:23:31 node-1 kernel: [    0.008691] CPU: Physical Processor ID: 0
Oct 18 16:23:31 node-1 kernel: [    0.008692] CPU: Processor Core ID: 0
Oct 18 16:23:31 node-1 kernel: [    0.008696] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 18 16:23:31 node-1 kernel: [    0.008696] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 18 16:23:31 node-1 kernel: [    0.009390] mce: CPU supports 22 MCE banks
Oct 18 16:23:31 node-1 kernel: [    0.009417] CPU0: Thermal monitoring enabled (TM1)
Oct 18 16:23:31 node-1 kernel: [    0.009438] process: using mwait in idle threads
Oct 18 16:23:31 node-1 kernel: [    0.009441] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 18 16:23:31 node-1 kernel: [    0.009441] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 18 16:23:31 node-1 kernel: [    0.009441] tlb_flushall_shift: 6
Oct 18 16:23:31 node-1 kernel: [    0.009530] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 18 16:23:31 node-1 kernel: [    0.010256] ACPI: Core revision 20131115
Oct 18 16:23:31 node-1 kernel: [    0.023083] ACPI: All ACPI Tables successfully acquired
Oct 18 16:23:31 node-1 kernel: [    0.023242] ftrace: allocating 28622 entries in 112 pages
Oct 18 16:23:31 node-1 kernel: [    0.032008] dmar: Host address width 46
Oct 18 16:23:31 node-1 kernel: [    0.032010] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 18 16:23:31 node-1 kernel: [    0.032016] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 18 16:23:31 node-1 kernel: [    0.032018] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 18 16:23:31 node-1 kernel: [    0.032022] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 18 16:23:31 node-1 kernel: [    0.032024] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 18 16:23:31 node-1 kernel: [    0.032025] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 18 16:23:31 node-1 kernel: [    0.032026] dmar: ATSR flags: 0x0
Oct 18 16:23:31 node-1 kernel: [    0.032027] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 18 16:23:31 node-1 kernel: [    0.032028] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 18 16:23:31 node-1 kernel: [    0.032144] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 18 16:23:31 node-1 kernel: [    0.032145] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 18 16:23:31 node-1 kernel: [    0.032146] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 18 16:23:31 node-1 kernel: [    0.032147] HPET id 0 under DRHD base 0xc7ffc000
Oct 18 16:23:31 node-1 kernel: [    0.032148] Your BIOS is broken and requested that x2apic be disabled.
Oct 18 16:23:31 node-1 kernel: [    0.032148] This will slightly decrease performance.
Oct 18 16:23:31 node-1 kernel: [    0.032148] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 18 16:23:31 node-1 kernel: [    0.032581] Enabled IRQ remapping in xapic mode
Oct 18 16:23:31 node-1 kernel: [    0.032582] x2apic not enabled, IRQ remapping is in xapic mode
Oct 18 16:23:31 node-1 kernel: [    0.032586] Switched APIC routing to physical flat.
Oct 18 16:23:31 node-1 kernel: [    0.033188] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 18 16:23:31 node-1 kernel: [    0.072836] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 18 16:23:31 node-1 kernel: [    0.072842] TSC deadline timer enabled
Oct 18 16:23:31 node-1 kernel: [    0.072850] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 18 16:23:31 node-1 kernel: [    0.072856] ... version:                3
Oct 18 16:23:31 node-1 kernel: [    0.072856] ... bit width:              48
Oct 18 16:23:31 node-1 kernel: [    0.072857] ... generic registers:      4
Oct 18 16:23:31 node-1 kernel: [    0.072858] ... value mask:             0000ffffffffffff
Oct 18 16:23:31 node-1 kernel: [    0.072859] ... max period:             0000ffffffffffff
Oct 18 16:23:31 node-1 kernel: [    0.072860] ... fixed-purpose events:   3
Oct 18 16:23:31 node-1 kernel: [    0.072861] ... event mask:             000000070000000f
Oct 18 16:23:31 node-1 kernel: [    0.074287] x86: Booting SMP configuration:
Oct 18 16:23:31 node-1 kernel: [    0.088489] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 18 16:23:31 node-1 kernel: [    0.074289] .... node  #0, CPUs:        #1  #2  #3
Oct 18 16:23:31 node-1 kernel: [    0.116413] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 18 16:23:31 node-1 kernel: [    0.270560] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 18 16:23:31 node-1 kernel: [    0.326178] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 18 16:23:31 node-1 kernel: [    0.383235] x86: Booted up 2 nodes, 16 CPUs
Oct 18 16:23:31 node-1 kernel: [    0.383238] smpboot: Total of 16 processors activated (111751.51 BogoMIPS)
Oct 18 16:23:31 node-1 kernel: [    0.407854] devtmpfs: initialized
Oct 18 16:23:31 node-1 kernel: [    0.410332] EVM: security.selinux
Oct 18 16:23:31 node-1 kernel: [    0.410333] EVM: security.SMACK64
Oct 18 16:23:31 node-1 kernel: [    0.410334] EVM: security.ima
Oct 18 16:23:31 node-1 kernel: [    0.410335] EVM: security.capability
Oct 18 16:23:31 node-1 kernel: [    0.410385] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.411049] pinctrl core: initialized pinctrl subsystem
Oct 18 16:23:31 node-1 kernel: [    0.411106] regulator-dummy: no parameters
Oct 18 16:23:31 node-1 kernel: [    0.411137] RTC time: 16:22:55, date: 10/18/16
Oct 18 16:23:31 node-1 kernel: [    0.411172] NET: Registered protocol family 16
Oct 18 16:23:31 node-1 kernel: [    0.411256] cpuidle: using governor ladder
Oct 18 16:23:31 node-1 kernel: [    0.411258] cpuidle: using governor menu
Oct 18 16:23:31 node-1 kernel: [    0.411291] ACPI: bus type PCI registered
Oct 18 16:23:31 node-1 kernel: [    0.411293] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 18 16:23:31 node-1 kernel: [    0.411353] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 18 16:23:31 node-1 kernel: [    0.411356] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 18 16:23:31 node-1 kernel: [    0.425102] PCI: Using configuration type 1 for base access
Oct 18 16:23:31 node-1 kernel: [    0.426118] bio: create slab <bio-0> at 0
Oct 18 16:23:31 node-1 kernel: [    0.426429] ACPI: Added _OSI(Module Device)
Oct 18 16:23:31 node-1 kernel: [    0.426431] ACPI: Added _OSI(Processor Device)
Oct 18 16:23:31 node-1 kernel: [    0.426432] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 18 16:23:31 node-1 kernel: [    0.426433] ACPI: Added _OSI(Processor Aggregator Device)
Oct 18 16:23:31 node-1 kernel: [    0.439187] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 18 16:23:31 node-1 kernel: [    0.449913] ACPI: Interpreter enabled
Oct 18 16:23:31 node-1 kernel: [    0.449918] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 18 16:23:31 node-1 kernel: [    0.449922] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 18 16:23:31 node-1 kernel: [    0.449925] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 18 16:23:31 node-1 kernel: [    0.449932] ACPI: (supports S0 S4 S5)
Oct 18 16:23:31 node-1 kernel: [    0.449933] ACPI: Using IOAPIC for interrupt routing
Oct 18 16:23:31 node-1 kernel: [    0.449975] HEST: Table parsing has been initialized.
Oct 18 16:23:31 node-1 kernel: [    0.449978] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 18 16:23:31 node-1 kernel: [    0.450533] ACPI: No dock devices found.
Oct 18 16:23:31 node-1 kernel: [    0.462072] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 18 16:23:31 node-1 kernel: [    0.462077] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-1 kernel: [    0.462080] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 18 16:23:31 node-1 kernel: [    0.462107] PCI host bridge to bus 0000:ff
Oct 18 16:23:31 node-1 kernel: [    0.462110] pci_bus 0000:ff: root bus resource [bus ff]
Oct 18 16:23:31 node-1 kernel: [    0.462118] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462156] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.462187] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462223] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462253] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.462283] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.462314] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462344] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462375] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462404] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462431] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462458] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462486] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462513] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462540] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462567] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462597] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462624] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462651] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.462680] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462706] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.462732] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462758] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462789] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.462825] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462856] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462886] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462918] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462949] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.462980] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463012] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463043] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463074] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463107] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463141] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463174] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463208] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463239] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463267] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463298] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463331] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463372] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463408] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463440] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463470] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463500] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463532] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463563] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463594] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463624] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463656] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463685] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463714] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463743] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463773] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463803] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463835] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463892] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 18 16:23:31 node-1 kernel: [    0.463895] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-1 kernel: [    0.463898] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 18 16:23:31 node-1 kernel: [    0.463915] PCI host bridge to bus 0000:7f
Oct 18 16:23:31 node-1 kernel: [    0.463917] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 18 16:23:31 node-1 kernel: [    0.463922] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.463949] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.463981] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464011] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464033] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.464057] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.464083] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464109] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464133] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464155] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464177] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464199] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464223] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464244] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464269] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464298] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464319] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464342] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464365] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.464389] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464411] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.464433] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464456] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464483] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 18 16:23:31 node-1 kernel: [    0.464517] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464543] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464569] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464596] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464621] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464647] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464673] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464701] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464726] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464754] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464782] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464811] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464840] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464868] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464895] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464924] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464949] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.464976] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465004] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465031] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465057] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465082] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465108] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465134] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465159] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465185] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465214] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465239] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465261] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465285] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465308] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465336] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.465361] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.466603] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 18 16:23:31 node-1 kernel: [    0.466606] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-1 kernel: [    0.467729] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 18 16:23:31 node-1 kernel: [    0.468238] PCI host bridge to bus 0000:00
Oct 18 16:23:31 node-1 kernel: [    0.468240] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 18 16:23:31 node-1 kernel: [    0.468242] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 18 16:23:31 node-1 kernel: [    0.468243] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 18 16:23:31 node-1 kernel: [    0.468244] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 18 16:23:31 node-1 kernel: [    0.468246] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 18 16:23:31 node-1 kernel: [    0.468247] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 18 16:23:31 node-1 kernel: [    0.468249] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 18 16:23:31 node-1 kernel: [    0.468254] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 18 16:23:31 node-1 kernel: [    0.468335] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.468366] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.468408] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-1 kernel: [    0.468426] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.468456] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.468496] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-1 kernel: [    0.468514] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.468544] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.468587] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-1 kernel: [    0.468604] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.468674] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.468749] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.468823] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 18 16:23:31 node-1 kernel: [    0.468828] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 18 16:23:31 node-1 kernel: [    0.468914] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 18 16:23:31 node-1 kernel: [    0.469061] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 18 16:23:31 node-1 kernel: [    0.469078] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 18 16:23:31 node-1 kernel: [    0.469156] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.469209] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-1 kernel: [    0.469230] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.469286] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.469329] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-1 kernel: [    0.469356] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.469412] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.469455] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 18 16:23:31 node-1 kernel: [    0.469479] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 18 16:23:31 node-1 kernel: [    0.469496] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 18 16:23:31 node-1 kernel: [    0.469573] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.469623] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-1 kernel: [    0.469649] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 18 16:23:31 node-1 kernel: [    0.469895] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 18 16:23:31 node-1 kernel: [    0.469901] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 18 16:23:31 node-1 kernel: [    0.469907] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.469913] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.469920] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 18 16:23:31 node-1 kernel: [    0.469950] pci 0000:01:00.0: supports D1 D2
Oct 18 16:23:31 node-1 kernel: [    0.475981] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 18 16:23:31 node-1 kernel: [    0.475987] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 18 16:23:31 node-1 kernel: [    0.475991] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 18 16:23:31 node-1 kernel: [    0.476250] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.476310] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 18 16:23:31 node-1 kernel: [    0.483977] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 18 16:23:31 node-1 kernel: [    0.483983] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.483987] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-1 kernel: [    0.484068] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.484153] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.484231] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.484276] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 18 16:23:31 node-1 kernel: [    0.484279] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.484281] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-1 kernel: [    0.484333] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.484455] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.484508] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 18 16:23:31 node-1 kernel: [    0.484511] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.484513] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.484562] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.484681] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.484722] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.484841] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.484878] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.485000] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.485035] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-1 kernel: [    0.485171] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-1 kernel: [    0.485212] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 18 16:23:31 node-1 kernel: [    0.485215] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.485217] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.485276] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-1 kernel: [    0.485339] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.485391] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.485433] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 18 16:23:31 node-1 kernel: [    0.485518] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 18 16:23:31 node-1 kernel: [    0.485623] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 18 16:23:31 node-1 kernel: [    0.485625] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.485627] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.485684] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-1 kernel: [    0.485737] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.485785] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.485997] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 18 16:23:31 node-1 kernel: [    0.486001] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 18 16:23:31 node-1 kernel: [    0.486064] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-1 kernel: [    0.486116] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.486190] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.486397] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 18 16:23:31 node-1 kernel: [    0.486401] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 18 16:23:31 node-1 kernel: [    0.486460] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-1 kernel: [    0.486520] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.486575] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 18 16:23:31 node-1 kernel: [    0.486794] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 18 16:23:31 node-1 kernel: [    0.486798] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 18 16:23:31 node-1 kernel: [    0.486971] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 18 16:23:31 node-1 kernel: [    0.487009] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 18 16:23:31 node-1 kernel: [    0.487086] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 18 16:23:31 node-1 kernel: [    0.487104] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 18 16:23:31 node-1 kernel: [    0.487117] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 18 16:23:31 node-1 kernel: [    0.487131] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 18 16:23:31 node-1 kernel: [    0.487181] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 18 16:23:31 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 18 16:23:31 node-1 kernel: [    0.491985] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 18 16:23:31 node-1 kernel: [    0.491993] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 18 16:23:31 node-1 kernel: [    0.492046] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 18 16:23:31 node-1 kernel: [    0.492684] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 18 16:23:31 node-1 kernel: [    0.492687] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-1 kernel: [    0.492811] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 18 16:23:31 node-1 kernel: [    0.492916] PCI host bridge to bus 0000:80
Oct 18 16:23:31 node-1 kernel: [    0.492918] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 18 16:23:31 node-1 kernel: [    0.492920] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 18 16:23:31 node-1 kernel: [    0.492921] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 18 16:23:31 node-1 kernel: [    0.492929] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.492992] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.493059] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 18 16:23:31 node-1 kernel: [    0.493120] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 18 16:23:31 node-1 kernel: [    0.493125] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 18 16:23:31 node-1 kernel: [    0.493196] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 18 16:23:31 node-1 kernel: [    0.493494] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 18 16:23:31 node-1 kernel: [    0.493525] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 18 16:23:31 node-1 kernel: [    0.493555] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 18 16:23:31 node-1 kernel: [    0.493584] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 18 16:23:31 node-1 kernel: [    0.493613] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-1 kernel: [    0.493643] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-1 kernel: [    0.493673] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-1 kernel: [    0.493702] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-1 kernel: [    0.493786] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 18 16:23:31 node-1 kernel: [    0.493791] ACPI: \_SB_.UNC1: notify handler is installed
Oct 18 16:23:31 node-1 kernel: [    0.493792] ACPI: \_SB_.UNC0: notify handler is installed
Oct 18 16:23:31 node-1 kernel: [    0.493807] ACPI: \_SB_.PCI0: notify handler is installed
Oct 18 16:23:31 node-1 kernel: [    0.493860] ACPI: \_SB_.PCI1: notify handler is installed
Oct 18 16:23:31 node-1 kernel: [    0.493939] Found 4 acpi root devices
Oct 18 16:23:31 node-1 kernel: [    0.494045] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 18 16:23:31 node-1 kernel: [    0.494047] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 18 16:23:31 node-1 kernel: [    0.494049] vgaarb: loaded
Oct 18 16:23:31 node-1 kernel: [    0.494050] vgaarb: bridge control possible 0000:0c:00.0
Oct 18 16:23:31 node-1 kernel: [    0.494164] SCSI subsystem initialized
Oct 18 16:23:31 node-1 kernel: [    0.494227] libata version 3.00 loaded.
Oct 18 16:23:31 node-1 kernel: [    0.494241] ACPI: bus type USB registered
Oct 18 16:23:31 node-1 kernel: [    0.494251] usbcore: registered new interface driver usbfs
Oct 18 16:23:31 node-1 kernel: [    0.494256] usbcore: registered new interface driver hub
Oct 18 16:23:31 node-1 kernel: [    0.494280] usbcore: registered new device driver usb
Oct 18 16:23:31 node-1 kernel: [    0.494452] PCI: Using ACPI for IRQ routing
Oct 18 16:23:31 node-1 kernel: [    0.498037] PCI: pci_cache_line_size set to 64 bytes
Oct 18 16:23:31 node-1 kernel: [    0.498261] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 18 16:23:31 node-1 kernel: [    0.498262] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 18 16:23:31 node-1 kernel: [    0.498263] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 18 16:23:31 node-1 kernel: [    0.498326] NetLabel: Initializing
Oct 18 16:23:31 node-1 kernel: [    0.498327] NetLabel:  domain hash size = 128
Oct 18 16:23:31 node-1 kernel: [    0.498328] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 18 16:23:31 node-1 kernel: [    0.498338] NetLabel:  unlabeled traffic allowed by default
Oct 18 16:23:31 node-1 kernel: [    0.498394] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 18 16:23:31 node-1 kernel: [    0.498398] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 18 16:23:31 node-1 kernel: [    0.500456] Switched to clocksource hpet
Oct 18 16:23:31 node-1 kernel: [    0.504370] AppArmor: AppArmor Filesystem Enabled
Oct 18 16:23:31 node-1 kernel: [    0.504385] pnp: PnP ACPI init
Oct 18 16:23:31 node-1 kernel: [    0.504391] ACPI: bus type PNP registered
Oct 18 16:23:31 node-1 kernel: [    0.504513] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504521] pnp 00:01: [dma 4]
Oct 18 16:23:31 node-1 kernel: [    0.504533] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504559] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504578] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504595] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504628] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504679] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504681] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 18 16:23:31 node-1 kernel: [    0.504683] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504684] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504686] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504690] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504692] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 18 16:23:31 node-1 kernel: [    0.504694] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504695] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504697] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504698] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504700] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504701] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 18 16:23:31 node-1 kernel: [    0.504704] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504787] pnp 00:07: [dma 0 disabled]
Oct 18 16:23:31 node-1 kernel: [    0.504815] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504890] pnp 00:08: [dma 0 disabled]
Oct 18 16:23:31 node-1 kernel: [    0.504921] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 18 16:23:31 node-1 kernel: [    0.504971] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 18 16:23:31 node-1 kernel: [    0.505315] pnp: PnP ACPI: found 10 devices
Oct 18 16:23:31 node-1 kernel: [    0.505316] ACPI: bus type PNP unregistered
Oct 18 16:23:31 node-1 kernel: [    0.511591] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 18 16:23:31 node-1 kernel: [    0.511593] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 18 16:23:31 node-1 kernel: [    0.511596] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 18 16:23:31 node-1 kernel: [    0.511600] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 18 16:23:31 node-1 kernel: [    0.511602] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511617] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511646] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 18 16:23:31 node-1 kernel: [    0.511660] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511689] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 18 16:23:31 node-1 kernel: [    0.511704] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 18 16:23:31 node-1 kernel: [    0.511732] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 18 16:23:31 node-1 kernel: [    0.511750] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 18 16:23:31 node-1 kernel: [    0.511778] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 18 16:23:31 node-1 kernel: [    0.511780] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511795] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511823] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 18 16:23:31 node-1 kernel: [    0.511825] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511840] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511869] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 18 16:23:31 node-1 kernel: [    0.511870] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511873] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511877] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 18 16:23:31 node-1 kernel: [    0.511879] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511881] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511885] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 18 16:23:31 node-1 kernel: [    0.511890] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 18 16:23:31 node-1 kernel: [    0.511898] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 18 16:23:31 node-1 kernel: [    0.511901] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 18 16:23:31 node-1 kernel: [    0.511907] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 18 16:23:31 node-1 kernel: [    0.511908] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 18 16:23:31 node-1 kernel: [    0.511909] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 18 16:23:31 node-1 kernel: [    0.511910] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 18 16:23:31 node-1 kernel: [    0.511911] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 18 16:23:31 node-1 kernel: [    0.511912] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 18 16:23:31 node-1 kernel: [    0.511913] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 18 16:23:31 node-1 kernel: [    0.511914] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 18 16:23:31 node-1 kernel: [    0.511915] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511915] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511916] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511917] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511918] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511919] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511920] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511921] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511922] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-1 kernel: [    0.511923] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511924] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 18 16:23:31 node-1 kernel: [    0.511925] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 18 16:23:31 node-1 kernel: [    0.511926] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 18 16:23:31 node-1 kernel: [    0.511927] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 18 16:23:31 node-1 kernel: [    0.511929] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 18 16:23:31 node-1 kernel: [    0.511930] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 18 16:23:31 node-1 kernel: [    0.511971] NET: Registered protocol family 2
Oct 18 16:23:31 node-1 kernel: [    0.512230] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.512565] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.512706] TCP: Hash tables configured (established 262144 bind 65536)
Oct 18 16:23:31 node-1 kernel: [    0.512742] TCP: reno registered
Oct 18 16:23:31 node-1 kernel: [    0.512770] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.512864] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.513010] NET: Registered protocol family 1
Oct 18 16:23:31 node-1 kernel: [    0.552551] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 18 16:23:31 node-1 kernel: [    0.552564] PCI: CLS 64 bytes, default 64
Oct 18 16:23:31 node-1 kernel: [    0.552641] Trying to unpack rootfs image as initramfs...
Oct 18 16:23:31 node-1 kernel: [    0.772262] Freeing initrd memory: 20368K (ffff880035828000 - ffff880036c0c000)
Oct 18 16:23:31 node-1 kernel: [    0.772302] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 18 16:23:31 node-1 kernel: [    0.772304] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 18 16:23:31 node-1 kernel: [    0.772738] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772744] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772749] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772754] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772764] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772775] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772783] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772792] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772800] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772809] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772816] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772822] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772829] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772836] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772843] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772850] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-1 kernel: [    0.772893] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 18 16:23:31 node-1 kernel: [    0.772897] Scanning for low memory corruption every 60 seconds
Oct 18 16:23:31 node-1 kernel: [    0.773195] Initialise system trusted keyring
Oct 18 16:23:31 node-1 kernel: [    0.773243] audit: initializing netlink socket (disabled)
Oct 18 16:23:31 node-1 kernel: [    0.773253] type=2000 audit(1476807774.724:1): initialized
Oct 18 16:23:31 node-1 kernel: [    0.790931] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 18 16:23:31 node-1 kernel: [    0.792393] zbud: loaded
Oct 18 16:23:31 node-1 kernel: [    0.792506] VFS: Disk quotas dquot_6.5.2
Oct 18 16:23:31 node-1 kernel: [    0.792545] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 18 16:23:31 node-1 kernel: [    0.792905] fuse init (API version 7.22)
Oct 18 16:23:31 node-1 kernel: [    0.792958] msgmni has been set to 32768
Oct 18 16:23:31 node-1 kernel: [    0.793001] Key type big_key registered
Oct 18 16:23:31 node-1 kernel: [    0.793481] Key type asymmetric registered
Oct 18 16:23:31 node-1 kernel: [    0.793483] Asymmetric key parser 'x509' registered
Oct 18 16:23:31 node-1 kernel: [    0.793504] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 18 16:23:31 node-1 kernel: [    0.793564] io scheduler noop registered
Oct 18 16:23:31 node-1 kernel: [    0.793565] io scheduler deadline registered (default)
Oct 18 16:23:31 node-1 kernel: [    0.793581] io scheduler cfq registered
Oct 18 16:23:31 node-1 kernel: [    0.793876] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    0.793967] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    0.794053] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    0.794139] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    0.794233] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    0.794300] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    0.794558] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 18 16:23:31 node-1 kernel: [    0.794576] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 18 16:23:31 node-1 kernel: [    0.794588] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 18 16:23:31 node-1 kernel: [    0.794598] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794600] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794602] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-1 kernel: [    0.794606] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794607] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794608] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794610] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794611] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794612] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794614] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794615] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794616] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794618] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794619] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794621] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794623] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-1 kernel: [    0.794626] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794628] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-1 kernel: [    0.794637] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794640] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-1 kernel: [    0.794649] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794651] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-1 kernel: [    0.794653] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-1 kernel: [    0.794666] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 18 16:23:31 node-1 kernel: [    0.794754] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 18 16:23:31 node-1 kernel: [    0.794758] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 18 16:23:31 node-1 kernel: [    0.794766] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 18 16:23:31 node-1 kernel: [    0.794802] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 18 16:23:31 node-1 kernel: [    0.794803] vesafb: scrolling: redraw
Oct 18 16:23:31 node-1 kernel: [    0.794805] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 18 16:23:31 node-1 kernel: [    0.815542] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 18 16:23:31 node-1 kernel: [    0.824040] Console: switching to colour frame buffer device 80x30
Oct 18 16:23:31 node-1 kernel: [    0.832734] fb0: VESA VGA frame buffer device
Oct 18 16:23:31 node-1 kernel: [    0.832932] intel_idle: MWAIT substates: 0x2120
Oct 18 16:23:31 node-1 kernel: [    0.832933] intel_idle: v0.4 model 0x3F
Oct 18 16:23:31 node-1 kernel: [    0.832934] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 18 16:23:31 node-1 kernel: [    0.833182] ipmi message handler version 39.2
Oct 18 16:23:31 node-1 kernel: [    0.833440] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 18 16:23:31 node-1 kernel: [    0.833872] ACPI: AC Adapter [P111] (on-line)
Oct 18 16:23:31 node-1 kernel: [    0.839107] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 18 16:23:31 node-1 kernel: [    0.850129] ACPI: Power Button [PWRB]
Oct 18 16:23:31 node-1 kernel: [    0.855908] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 18 16:23:31 node-1 kernel: [    0.867537] ACPI: Power Button [PWRF]
Oct 18 16:23:31 node-1 kernel: [    0.894111] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 18 16:23:31 node-1 kernel: [    0.905794] pstore: Registered erst as persistent store backend
Oct 18 16:23:31 node-1 kernel: [    0.912005] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 18 16:23:31 node-1 kernel: [    0.923981] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 18 16:23:31 node-1 kernel: [    0.950744] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 18 16:23:31 node-1 kernel: [    0.984062] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 18 16:23:31 node-1 kernel: [    0.998215] Linux agpgart interface v0.103
Oct 18 16:23:31 node-1 kernel: [    1.005855] brd: module loaded
Oct 18 16:23:31 node-1 kernel: [    1.012889] loop: module loaded
Oct 18 16:23:31 node-1 kernel: [    1.019597] libphy: Fixed MDIO Bus: probed
Oct 18 16:23:31 node-1 kernel: [    1.026059] tun: Universal TUN/TAP device driver, 1.6
Oct 18 16:23:31 node-1 kernel: [    1.032534] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 18 16:23:31 node-1 kernel: [    1.039052] PPP generic driver version 2.4.2
Oct 18 16:23:31 node-1 kernel: [    1.045422] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 18 16:23:31 node-1 kernel: [    1.051862] ehci-pci: EHCI PCI platform driver
Oct 18 16:23:31 node-1 kernel: [    1.058443] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 18 16:23:31 node-1 kernel: [    1.064840] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 18 16:23:31 node-1 kernel: [    1.077346] ehci-pci 0000:00:1a.0: debug port 2
Oct 18 16:23:31 node-1 kernel: [    1.087532] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 18 16:23:31 node-1 kernel: [    1.087550] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 18 16:23:31 node-1 kernel: [    1.103947] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 18 16:23:31 node-1 kernel: [    1.110044] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 18 16:23:31 node-1 kernel: [    1.116230] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 18 16:23:31 node-1 kernel: [    1.128152] usb usb1: Product: EHCI Host Controller
Oct 18 16:23:31 node-1 kernel: [    1.134200] usb usb1: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 18 16:23:31 node-1 kernel: [    1.140286] usb usb1: SerialNumber: 0000:00:1a.0
Oct 18 16:23:31 node-1 kernel: [    1.146274] hub 1-0:1.0: USB hub found
Oct 18 16:23:31 node-1 kernel: [    1.152104] hub 1-0:1.0: 2 ports detected
Oct 18 16:23:31 node-1 kernel: [    1.157951] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 18 16:23:31 node-1 kernel: [    1.163620] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 18 16:23:31 node-1 kernel: [    1.174593] ehci-pci 0000:00:1d.0: debug port 2
Oct 18 16:23:31 node-1 kernel: [    1.183913] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 18 16:23:31 node-1 kernel: [    1.183916] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 18 16:23:31 node-1 kernel: [    1.199866] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 18 16:23:31 node-1 kernel: [    1.205047] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 18 16:23:31 node-1 kernel: [    1.210331] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 18 16:23:31 node-1 kernel: [    1.220886] usb usb2: Product: EHCI Host Controller
Oct 18 16:23:31 node-1 kernel: [    1.226358] usb usb2: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 18 16:23:31 node-1 kernel: [    1.231894] usb usb2: SerialNumber: 0000:00:1d.0
Oct 18 16:23:31 node-1 kernel: [    1.237404] hub 2-0:1.0: USB hub found
Oct 18 16:23:31 node-1 kernel: [    1.242749] hub 2-0:1.0: 2 ports detected
Oct 18 16:23:31 node-1 kernel: [    1.248051] ehci-platform: EHCI generic platform driver
Oct 18 16:23:31 node-1 kernel: [    1.253273] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 18 16:23:31 node-1 kernel: [    1.258587] ohci-pci: OHCI PCI platform driver
Oct 18 16:23:31 node-1 kernel: [    1.263878] ohci-platform: OHCI generic platform driver
Oct 18 16:23:31 node-1 kernel: [    1.269072] uhci_hcd: USB Universal Host Controller Interface driver
Oct 18 16:23:31 node-1 kernel: [    1.274409] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 18 16:23:31 node-1 kernel: [    1.467645] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 18 16:23:31 node-1 kernel: [    1.627858] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 18 16:23:31 node-1 kernel: [    1.633374] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 18 16:23:31 node-1 kernel: [    1.639122] hub 1-1:1.0: USB hub found
Oct 18 16:23:31 node-1 kernel: [    1.644596] hub 1-1:1.0: 6 ports detected
Oct 18 16:23:31 node-1 kernel: [    1.759389] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 18 16:23:31 node-1 kernel: [    1.771396] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 18 16:23:31 node-1 kernel: [    2.027519] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 18 16:23:31 node-1 kernel: [    2.033068] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 18 16:23:31 node-1 kernel: [    2.038912] hub 2-1:1.0: USB hub found
Oct 18 16:23:31 node-1 kernel: [    2.044631] hub 2-1:1.0: 8 ports detected
Oct 18 16:23:31 node-1 kernel: [    2.315760] i8042: No controller found
Oct 18 16:23:31 node-1 kernel: [    2.321272] mousedev: PS/2 mouse device common for all mice
Oct 18 16:23:31 node-1 kernel: [    2.326878] rtc_cmos 00:02: RTC can wake from S4
Oct 18 16:23:31 node-1 kernel: [    2.330964] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 18 16:23:31 node-1 kernel: [    2.338277] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 18 16:23:31 node-1 kernel: [    2.343983] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 18 16:23:31 node-1 kernel: [    2.355171] device-mapper: uevent: version 1.0.3
Oct 18 16:23:31 node-1 kernel: [    2.360925] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 18 16:23:31 node-1 kernel: [    2.372427] ledtrig-cpu: registered to indicate activity on CPUs
Oct 18 16:23:31 node-1 kernel: [    2.378492] TCP: cubic registered
Oct 18 16:23:31 node-1 kernel: [    2.384517] NET: Registered protocol family 10
Oct 18 16:23:31 node-1 kernel: [    2.390609] NET: Registered protocol family 17
Oct 18 16:23:31 node-1 kernel: [    2.396476] Key type dns_resolver registered
Oct 18 16:23:31 node-1 kernel: [    2.402556] Loading compiled-in X.509 certificates
Oct 18 16:23:31 node-1 kernel: [    2.408893] Loaded X.509 cert 'Magrathea: Glacier signing key: c29c39823a6b07000b1e1e4c1cabc3708bc09796'
Oct 18 16:23:31 node-1 kernel: [    2.420530] registered taskstats version 1
Oct 18 16:23:31 node-1 kernel: [    2.428593] Key type trusted registered
Oct 18 16:23:31 node-1 kernel: [    2.436230] Key type encrypted registered
Oct 18 16:23:31 node-1 kernel: [    2.441753] AppArmor: AppArmor sha1 policy hashing enabled
Oct 18 16:23:31 node-1 kernel: [    2.447292] IMA: No TPM chip found, activating TPM-bypass!
Oct 18 16:23:31 node-1 kernel: [    2.453494] regulator-dummy: disabling
Oct 18 16:23:31 node-1 kernel: [    2.459112]   Magic number: 4:896:388
Oct 18 16:23:31 node-1 kernel: [    2.464565] thermal cooling_device3: hash matches
Oct 18 16:23:31 node-1 kernel: [    2.467213] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 18 16:23:31 node-1 kernel: [    2.467214] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 18 16:23:31 node-1 kernel: [    2.467215] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 18 16:23:31 node-1 kernel: [    2.467216] usb 2-1.4: Manufacturer: Avocent
Oct 18 16:23:31 node-1 kernel: [    2.467216] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 18 16:23:31 node-1 kernel: [    2.503718] rtc_cmos 00:02: setting system clock to 2016-10-18 16:22:57 UTC (1476807777)
Oct 18 16:23:31 node-1 kernel: [    2.516280] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 18 16:23:31 node-1 kernel: [    2.521978] EDD information not available.
Oct 18 16:23:31 node-1 kernel: [    2.527573] PM: Hibernation image not present or could not be loaded.
Oct 18 16:23:31 node-1 kernel: [    2.528435] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 18 16:23:31 node-1 kernel: [    2.539828] Write protecting the kernel read-only data: 12288k
Oct 18 16:23:31 node-1 kernel: [    2.546008] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 18 16:23:31 node-1 kernel: [    2.558460] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 18 16:23:31 node-1 kernel: [    2.590881] device-mapper: multipath: version 1.6.0 loaded
Oct 18 16:23:31 node-1 kernel: [    2.598882] systemd-udevd[217]: starting version 204
Oct 18 16:23:31 node-1 kernel: [    2.622212] md: linear personality registered for level -1
Oct 18 16:23:31 node-1 kernel: [    2.636305] md: multipath personality registered for level -4
Oct 18 16:23:31 node-1 kernel: [    2.644204] md: raid0 personality registered for level 0
Oct 18 16:23:31 node-1 kernel: [    2.652491] md: raid1 personality registered for level 1
Oct 18 16:23:31 node-1 kernel: [    2.665478] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 18 16:23:31 node-1 kernel: [    2.672036] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 18 16:23:31 node-1 kernel: [    2.672286] hidraw: raw HID events driver (C) Jiri Kosina
Oct 18 16:23:31 node-1 kernel: [    2.681062] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-1 kernel: [    2.681073] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 18 16:23:31 node-1 kernel: [    2.681086] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 18 16:23:31 node-1 kernel: [    2.681695] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.681766] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.681845] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.681936] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.682212] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.697931] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-1 kernel: [    2.697966] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct 18 16:23:31 node-1 kernel: [    2.697969] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 18 16:23:31 node-1 kernel: [    2.698307] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.698439] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.698493] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.698583] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.698850] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.698950] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.699221] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.716424] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-1 kernel: [    2.716440] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 18 16:23:31 node-1 kernel: [    2.716469] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 18 16:23:31 node-1 kernel: [    2.716749] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.716827] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.716894] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.716973] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.717311] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.726673] raid6: sse2x1   11325 MB/s
Oct 18 16:23:31 node-1 kernel: [    2.731674] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-1 kernel: [    2.731696] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 18 16:23:31 node-1 kernel: [    2.731697] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 18 16:23:31 node-1 kernel: [    2.732096] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.732244] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.732350] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.732410] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.732677] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 18 16:23:31 node-1 kernel: [    2.794814] raid6: sse2x2   12618 MB/s
Oct 18 16:23:31 node-1 kernel: [    2.862716] raid6: sse2x4    9512 MB/s
Oct 18 16:23:31 node-1 kernel: [    2.930406] raid6: avx2x1   14541 MB/s
Oct 18 16:23:31 node-1 kernel: [    3.002349] raid6: avx2x2   18871 MB/s
Oct 18 16:23:31 node-1 kernel: [    3.074290] raid6: avx2x4   21346 MB/s
Oct 18 16:23:31 node-1 kernel: [    3.080156] raid6: using algorithm avx2x4 (21346 MB/s)
Oct 18 16:23:31 node-1 kernel: [    3.086202] raid6: using avx2x2 recovery algorithm
Oct 18 16:23:31 node-1 kernel: [    3.092101] Switched to clocksource tsc
Oct 18 16:23:31 node-1 kernel: [    3.092446] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 18 16:23:31 node-1 kernel: [    3.093731] megasas: FW now in Ready state
Oct 18 16:23:31 node-1 kernel: [    3.094038] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094159] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094233] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094429] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094496] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094573] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094654] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094697] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094811] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094869] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.094958] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.095017] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.095078] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.095162] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.095305] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.095421] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Oct 18 16:23:31 node-1 kernel: [    3.095926] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 18 16:23:31 node-1 kernel: [    3.120641] xor: automatically using best checksumming function:
Oct 18 16:23:31 node-1 kernel: [    3.128265] usbcore: registered new interface driver usbhid
Oct 18 16:23:31 node-1 kernel: [    3.134022] usbhid: USB HID core driver
Oct 18 16:23:31 node-1 kernel: [    3.145235] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Oct 18 16:23:31 node-1 kernel: [    3.156706] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Oct 18 16:23:31 node-1 kernel: [    3.166207]    avx       : 36436.000 MB/sec
Oct 18 16:23:31 node-1 kernel: [    3.174132] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Oct 18 16:23:31 node-1 kernel: [    3.186205] async_tx: api initialized (async)
Oct 18 16:23:31 node-1 kernel: [    3.186231] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Oct 18 16:23:31 node-1 kernel: [    3.186284] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Oct 18 16:23:31 node-1 kernel: [    3.186324] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Oct 18 16:23:31 node-1 kernel: [    3.232763] md: raid6 personality registered for level 6
Oct 18 16:23:31 node-1 kernel: [    3.239176] md: raid5 personality registered for level 5
Oct 18 16:23:31 node-1 kernel: [    3.245563] md: raid4 personality registered for level 4
Oct 18 16:23:31 node-1 kernel: [    3.254973] md: raid10 personality registered for level 10
Oct 18 16:23:31 node-1 kernel: [    3.310353] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Oct 18 16:23:31 node-1 kernel: [    3.437987] megasas:IOC Init cmd success
Oct 18 16:23:31 node-1 kernel: [    3.465996] megasas: INIT adapter done
Oct 18 16:23:31 node-1 kernel: [    3.565904] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 18 16:23:31 node-1 kernel: [    3.572847] scsi0 : LSI SAS based MegaRAID driver
Oct 18 16:23:31 node-1 kernel: [    3.580304] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 18 16:23:31 node-1 kernel: [    3.599030] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 18 16:23:31 node-1 kernel: [    3.614377] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 18 16:23:31 node-1 kernel: [    3.620915] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 18 16:23:31 node-1 kernel: [    3.633909] sd 0:2:0:0: [sda] Write Protect is off
Oct 18 16:23:31 node-1 kernel: [    3.640378] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 18 16:23:31 node-1 kernel: [    3.640398] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 18 16:23:31 node-1 kernel: [    3.679847]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 18 16:23:31 node-1 kernel: [    3.686526] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 18 16:23:31 node-1 kernel: [    3.819101] random: lvm urandom read with 29 bits of entropy available
Oct 18 16:23:31 node-1 kernel: [    3.953671] bio: create slab <bio-1> at 1
Oct 18 16:23:31 node-1 kernel: [    4.708653] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 18 16:23:31 node-1 kernel: [    5.187862] init: plymouth-upstart-bridge main process (552) terminated with status 1
Oct 18 16:23:31 node-1 kernel: [    5.200306] init: plymouth-upstart-bridge main process ended, respawning
Oct 18 16:23:31 node-1 kernel: [    5.384328] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 18 16:23:31 node-1 kernel: [    5.439199] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 18 16:23:31 node-1 kernel: [    5.543986] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 18 16:23:31 node-1 kernel: [    5.609836] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 18 16:23:31 node-1 kernel: [    5.686101] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 18 16:23:31 node-1 kernel: [    5.723644] random: nonblocking pool is initialized
Oct 18 16:23:31 node-1 kernel: [    5.862107] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 18 16:23:31 node-1 kernel: [    5.927200] XFS (dm-0): Mounting Filesystem
Oct 18 16:23:31 node-1 kernel: [    6.197223] XFS (dm-0): Ending clean mount
Oct 18 16:23:31 node-1 kernel: [    6.240693] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 18 16:23:31 node-1 kernel: [    6.265293] XFS (dm-1): Mounting Filesystem
Oct 18 16:23:31 node-1 kernel: [    6.341206] XFS (dm-1): Ending clean mount
Oct 18 16:23:31 node-1 kernel: [    8.198171] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 18 16:23:31 node-1 kernel: [    8.225550] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 18 16:23:31 node-1 kernel: [    8.424946] systemd-udevd[777]: starting version 204
Oct 18 16:23:31 node-1 kernel: [    8.721032] power_meter ACPI000D:00: Found ACPI power meter.
Oct 18 16:23:31 node-1 kernel: [    8.721041] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 18 16:23:31 node-1 kernel: [    8.744832] IPMI System Interface driver.
Oct 18 16:23:31 node-1 kernel: [    8.744868] ipmi_si: probing via ACPI
Oct 18 16:23:31 node-1 kernel: [    8.744879] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 18 16:23:31 node-1 kernel: [    8.744879] ipmi_si: Adding ACPI-specified kcs state machine
Oct 18 16:23:31 node-1 kernel: [    8.744885] ipmi_si: probing via SMBIOS
Oct 18 16:23:31 node-1 kernel: [    8.744886] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 18 16:23:31 node-1 kernel: [    8.744887] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 18 16:23:31 node-1 kernel: [    8.744888] ipmi_si: probing via SPMI
Oct 18 16:23:31 node-1 kernel: [    8.744889] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 18 16:23:31 node-1 kernel: [    8.744890] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 18 16:23:31 node-1 kernel: [    8.744891] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 18 16:23:31 node-1 kernel: [    8.745781] wmi: Mapper loaded
Oct 18 16:23:31 node-1 kernel: [    8.748816] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 18 16:23:31 node-1 kernel: [    8.748820] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 18 16:23:31 node-1 kernel: [    8.748822] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 18 16:23:31 node-1 kernel: [    8.748824] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 18 16:23:31 node-1 kernel: [    8.748835] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 18 16:23:31 node-1 kernel: [    8.765225] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 18 16:23:31 node-1 kernel: [    8.845871] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Oct 18 16:23:31 node-1 kernel: [    8.873815] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 18 16:23:31 node-1 kernel: [    8.873823] ipmi_si 00:09: IPMI kcs interface initialized
Oct 18 16:23:31 node-1 kernel: [    8.877751] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Oct 18 16:23:31 node-1 kernel: [    8.901764] systemd-udevd[799]: renamed network interface eth0 to enp6s0
Oct 18 16:23:31 node-1 kernel: [    8.921695] systemd-udevd[827]: renamed network interface eth1 to enp7s0
Oct 18 16:23:31 node-1 kernel: [    9.190121] type=1400 audit(1476807784.187:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1040 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.190276] type=1400 audit(1476807784.187:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1040 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.190409] type=1400 audit(1476807784.187:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1040 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.198769] type=1400 audit(1476807784.195:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1041 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.198917] type=1400 audit(1476807784.195:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1041 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.199042] type=1400 audit(1476807784.195:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1041 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.218308] type=1400 audit(1476807784.215:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.218455] type=1400 audit(1476807784.215:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.218573] type=1400 audit(1476807784.215:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.218734] type=1400 audit(1476807784.215:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1080 comm="apparmor_parser"
Oct 18 16:23:31 node-1 kernel: [    9.784626] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 18 16:23:31 node-1 kernel: [    9.785668] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 18 16:23:31 node-1 kernel: [    9.948001] enic 0000:06:00.0 enp6s0: Link UP
Oct 18 16:23:31 node-1 kernel: [    9.950722] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 18 16:23:31 node-1 kernel: [    9.950727] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 18 16:23:31 node-1 kernel: [   19.274513] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 18 16:23:32 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 18 16:23:32 node-1 kernel: [   37.890568] init: failsafe main process (8421) killed by TERM signal
Oct 18 16:23:33 node-1 kernel: [   38.046171] audit_printk_skb: 30 callbacks suppressed
Oct 18 16:23:33 node-1 kernel: [   38.046172] type=1400 audit(1476807813.003:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8537 comm="apparmor_parser"
Oct 18 16:23:33 node-1 kernel: [   38.050140] type=1400 audit(1476807813.007:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8536 comm="apparmor_parser"
Oct 18 16:23:33 node-1 kernel: [   38.050145] type=1400 audit(1476807813.007:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8536 comm="apparmor_parser"
Oct 18 16:23:33 node-1 kernel: [   38.050148] type=1400 audit(1476807813.007:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8536 comm="apparmor_parser"
Oct 18 16:23:33 node-1 kernel: [   38.050413] type=1400 audit(1476807813.007:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8536 comm="apparmor_parser"
Oct 18 16:23:33 node-1 kernel: [   38.050415] type=1400 audit(1476807813.007:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8536 comm="apparmor_parser"
Oct 18 16:23:33 node-1 kernel: [   38.050533] type=1400 audit(1476807813.007:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8536 comm="apparmor_parser"
Oct 18 16:23:33 node-1 dbus[8540]: [system] AppArmor D-Bus mediation is enabled
Oct 18 16:23:33 node-1 kernel: [   38.159158] type=1400 audit(1476807813.115:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8539 comm="apparmor_parser"
Oct 18 16:23:33 node-1 cron[8581]: (CRON) INFO (pidfile fd = 3)
Oct 18 16:23:33 node-1 anacron[8616]: Anacron 2.3 started on 2016-10-18
Oct 18 16:23:33 node-1 cron[8619]: (CRON) STARTUP (fork ok)
Oct 18 16:23:33 node-1 anacron[8616]: Will run job `cron.daily' in 5 min.
Oct 18 16:23:33 node-1 anacron[8616]: Will run job `cron.weekly' in 10 min.
Oct 18 16:23:33 node-1 anacron[8616]: Will run job `cron.monthly' in 15 min.
Oct 18 16:23:33 node-1 anacron[8616]: Jobs will be executed sequentially
Oct 18 16:23:33 node-1 cron[8619]: (CRON) INFO (Running @reboot jobs)
Oct 18 16:23:33 node-1 multipathd: path checkers start up
Oct 18 16:23:33 node-1 postfix/master[8760]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 18 16:23:37 node-1 puppet-agent[8944]: Reopening log files
Oct 18 16:23:38 node-1 puppet-agent[8944]: Could not request certificate: Connection refused - connect(2)
Oct 18 16:23:50 node-1 puppet-user[9023]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 18 16:23:50 node-1 puppet-user[9023]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 18 16:23:51 node-1 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 18 16:23:51 node-1 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 18 16:23:51 node-1 puppet-user[9023]: Finished catalog run in 0.94 seconds
Oct 18 16:23:53 node-1 multipathd: uevent trigger error
Oct 18 16:23:53 node-1 puppet-user[9448]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 18 16:23:53 node-1 puppet-user[9448]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 18 16:23:53 node-1 puppet-user[9448]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 18 16:23:53 node-1 puppet-user[9448]: Finished catalog run in 0.06 seconds
Oct 18 16:23:55 node-1 puppet-user[9909]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 18 16:23:55 node-1 puppet-user[9909]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 18 16:23:55 node-1 puppet-user[9909]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 18 16:23:55 node-1 puppet-user[9909]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 18 16:23:55 node-1 puppet-user[9909]: Finished catalog run in 0.03 seconds
Oct 18 16:23:57 node-1 puppet-user[10501]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 18 16:23:57 node-1 puppet-user[10501]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 18 16:23:57 node-1 puppet-user[10501]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 18 16:23:57 node-1 puppet-user[10501]: Finished catalog run in 0.03 seconds
Oct 18 16:23:58 node-1 puppet-user[10953]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 18 16:23:58 node-1 puppet-user[10953]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Oct 18 16:23:58 node-1 puppet-user[10953]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 18 16:23:59 node-1 puppet-user[10953]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Oct 18 16:23:59 node-1 puppet-user[10953]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Oct 18 16:24:00 node-1 puppet-user[10953]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/tacker-0.2/]/Exec[rsync /etc/fuel/plugins/tacker-0.2/]/returns) executed successfully
Oct 18 16:24:00 node-1 puppet-user[10953]: Finished catalog run in 1.17 seconds
Oct 18 16:24:01 node-1 CRON[11817]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct 18 16:24:01 node-1 puppet-user[11483]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 18 16:24:01 node-1 puppet-user[11483]: Compiled catalog for node-1.domain.tld in environment production in 0.25 seconds
Oct 18 16:24:01 node-1 puppet-user[11483]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Oct 18 16:24:01 node-1 puppet-user[11483]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[tacker-0.2.0]/Apt::Setting[list-tacker-0.2.0]/File[/etc/apt/sources.list.d/tacker-0.2.0.list]/ensure) created
Oct 18 16:24:01 node-1 puppet-user[11483]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 18 16:24:01 node-1 puppet-user[11483]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 18 16:24:01 node-1 puppet-user[11483]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Oct 18 16:24:02 node-1 puppet-user[11483]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 18 16:24:02 node-1 puppet-user[11483]: Finished catalog run in 0.37 seconds
Oct 18 16:24:03 node-1 puppet-user[11977]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 18 16:24:03 node-1 puppet-user[11977]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Oct 18 16:24:04 node-1 puppet-user[11977]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 18 16:24:04 node-1 kernel: [   69.129237] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 18 16:24:04 node-1 kernel: [   69.129288] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Oct 18 16:24:04 node-1 puppet-user[11977]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Oct 18 16:24:04 node-1 puppet-user[11977]: Finished catalog run in 0.05 seconds
Oct 18 16:24:05 node-1 puppet-user[12429]: (Scope(Class[main])) MODULAR: sync_time
Oct 18 16:24:05 node-1 puppet-user[12429]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 18 16:24:05 node-1 ntpdate[12845]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 18 16:24:11 node-1 ntpdate[12845]: adjust time server 10.20.0.2 offset 0.030537 sec
Oct 18 16:24:11 node-1 puppet-user[12429]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 18 16:24:11 node-1 puppet-user[12429]: Finished catalog run in 6.17 seconds
Oct 18 16:24:13 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 18 16:24:13 node-1 nailgun-agent: D, [2016-10-18T16:24:01.455714 #11820] DEBUG -- : Sleep for 12 seconds before sending request
Oct 18 16:24:13 node-1 nailgun-agent: I, [2016-10-18T16:24:13.470170 #11820]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 18 16:24:13 node-1 nailgun-agent: D, [2016-10-18T16:24:13.863923 #11820] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 18 16:24:16 node-1 puppet-user[13346]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 18 16:24:16 node-1 puppet-user[13346]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct 18 16:24:17 node-1 puppet-user[13346]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 18 16:24:17 node-1 puppet-user[13346]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight", "plugins/tacker"]'
Oct 18 16:24:17 node-1 puppet-user[13346]: Finished catalog run in 0.06 seconds
Oct 18 16:24:18 node-1 puppet-user[13799]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 18 16:24:18 node-1 puppet-user[13799]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 18 16:24:19 node-1 puppet-user[13799]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 18 16:24:19 node-1 kernel: [   84.947516] init: plymouth-upstart-bridge main process ended, respawning
Oct 18 16:24:19 node-1 puppet-user[13799]: Finished catalog run in 0.92 seconds
Oct 18 16:24:20 node-1 puppet-agent[8944]: Could not run: SIGTERM
Oct 18 16:24:20 node-1 kernel: [   85.246969] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 18 16:24:20 node-1 ec2: 
Oct 18 16:24:20 node-1 ec2: #############################################################
Oct 18 16:24:20 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 18 16:24:20 node-1 ec2: 1024 9d:a7:f5:9f:ca:42:1b:07:db:0b:b2:e9:46:3a:a5:64  root@node-1.domain.tld (DSA)
Oct 18 16:24:20 node-1 ec2: 256 eb:06:f4:dc:26:e0:34:05:10:23:3b:f2:a3:a6:69:25  root@node-1.domain.tld (ECDSA)
Oct 18 16:24:20 node-1 ec2: 256 06:c3:c7:58:f3:02:8e:c2:8d:dd:28:a4:49:0e:70:2e  root@node-1.domain.tld (ED25519)
Oct 18 16:24:20 node-1 ec2: 2048 be:bb:a5:73:25:1e:2e:5f:b8:21:7e:d0:1a:e3:ec:6b  root@node-1.domain.tld (RSA)
Oct 18 16:24:20 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 18 16:24:20 node-1 ec2: #############################################################
Oct 18 16:24:21 node-1 puppet-user[14479]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 18 16:24:21 node-1 puppet-user[14479]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct 18 16:24:24 node-1 puppet-user[14479]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.902706 #11820] DEBUG -- : Trying to find block devices
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.902835 #11820] DEBUG -- : Found block device: sda
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.902894 #11820] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.902919 #11820] DEBUG -- : Trying to get list of physical devices
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.903082 #11820] DEBUG -- : Getting udev properties for device: sda
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.905153 #11820] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Oct 18 16:24:25 node-1 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40598", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.905181 #11820] DEBUG -- : Trying to find out if device sda is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.905226 #11820] DEBUG -- : Device sda removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.905242 #11820] DEBUG -- : Device sda seems to be appropriate
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.905648 #11820] DEBUG -- : Getting udev properties for device: dm-0
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.907212 #11820] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-CjjhQZawJ3EkETqOd2AedBrhlKGHZzu3K1MsQrUySfjopTX687LKbPhxbYV3VgEu /dev/disk/by-uuid/2098b406-320f-402f-a053-7e64e4584934 /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-CjjhQZawJ3EkETqOd2AedBrhlKGHZzu3K1MsQrUySfjopTX687LKbPhxbYV3VgEu", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2098b406-320f-402f-a053-7e64e4584934", "ID_FS_UUID_ENC"=>"2098b406-320f-402f-a053-7e64e4584934", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8054", "nomdmonddf"=>"1", "nomd
Oct 18 16:24:25 node-1 nailgun-agent: monisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.907240 #11820] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.907282 #11820] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.907296 #11820] DEBUG -- : Device dm-0 seems to be appropriate
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.907339 #11820] DEBUG -- : Getting udev properties for device: dm-1
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.908904 #11820] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-6HsDeArhl4gqjDqfrY2cW0UMnTLH3uY1apE16YZGYi1sHX7h1cMFBCkOBsIclN9G /dev/disk/by-uuid/ead78ab6-0c35-4bcd-854c-442864ea43a2 /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-6HsDeArhl4gqjDqfrY2cW0UMnTLH3uY1apE16YZGYi1sHX7h1cMFBCkOBsIclN9G", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ead78ab6-0c35-4bcd-854c-442864ea43a2", "ID_FS_UUID_ENC"=>"ead78ab6-0c35-4bcd-854c-442864ea43a2", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5
Oct 18 16:24:25 node-1 nailgun-agent: 2151", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.908931 #11820] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.908974 #11820] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.908989 #11820] DEBUG -- : Device dm-1 seems to be appropriate
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.909004 #11820] DEBUG -- : Getting udev properties for device: dm-2
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.910598 #11820] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-XDLAn9NeqJ4d0cBbFAE0vgv2PSEzwVaxTgkCTKYude0jOTLwdYtG6Gj00n22yYGk /dev/disk/by-uuid/24bf604a-27c4-43e2-b8eb-59b6235700c2 /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-XDLAn9NeqJ4d0cBbFAE0vgv2PSEzwVaxTgkCTKYude0jOTLwdYtG6Gj00n22yYGk", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"24bf604a-27c4-43e2-b8eb-59b6235700c2", "ID_FS_UUID_ENC"=>"24bf604a-27c4-43e2-b8eb-59b6235700c2", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46718", "nomdmon
Oct 18 16:24:25 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.910636 #11820] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.910668 #11820] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.910710 #11820] DEBUG -- : Device dm-2 seems to be appropriate
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.910724 #11820] DEBUG -- : Getting udev properties for device: dm-3
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.912278 #11820] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-XnuqZMKKa5ZoJoqz68K25JG9JRHmTJW61Ee8rTAqDv12qQoDjvmndiC8bk8mF6bA /dev/disk/by-uuid/f751ed8a-f6df-4c20-bb54-48e0d701158e /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-XnuqZMKKa5ZoJoqz68K25JG9JRHmTJW61Ee8rTAqDv12qQoDjvmndiC8bk8mF6bA", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f751ed8a-f6df-4c20-bb54-48e0d701158e", "ID_FS_UUID_ENC"=>"f751ed8a-f6df-4c20-bb54-48e0d701158e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49095", "nomdmonddf"=>"1",
Oct 18 16:24:25 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.912307 #11820] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.912349 #11820] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.912364 #11820] DEBUG -- : Device dm-3 seems to be appropriate
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.912401 #11820] DEBUG -- : Getting udev properties for device: dm-4
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.914344 #11820] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-jM7dRrlR00XTpgYZG5PtQchQ2d7WpLZcuiI5UBQc3R3uK41REMRZ8GrDbPH4SRGZ /dev/disk/by-uuid/e5d5dd70-7afa-42cb-ad81-c1b7a3c34e21 /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-jM7dRrlR00XTpgYZG5PtQchQ2d7WpLZcuiI5UBQc3R3uK41REMRZ8GrDbPH4SRGZ", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e5d5dd70-7afa-42cb-ad81-c1b7a3c34e21", "ID_FS_UUID_ENC"=>"e5d5dd70-7afa-42cb-ad81-c1b7a3c34e21", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65898", "nomdmonddf"=>"1", "nom
Oct 18 16:24:25 node-1 nailgun-agent: dmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.914371 #11820] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.914404 #11820] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.914419 #11820] DEBUG -- : Device dm-4 seems to be appropriate
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.914434 #11820] DEBUG -- : Getting udev properties for device: dm-5
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.916481 #11820] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-jM7dRrlR00XTpgYZG5PtQchQ2d7WpLZcCe2e87qN07GQs3twDfddAjXImwPG4JC9 /dev/disk/by-uuid/14b7a2bc-f218-4b42-86ea-df94818395cc /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-jM7dRrlR00XTpgYZG5PtQchQ2d7WpLZcCe2e87qN07GQs3twDfddAjXImwPG4JC9", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"14b7a2bc-f218-4b42-86ea-df94818395cc", "ID_FS_UUID_ENC"=>"14b7a2bc-f218-4b42-86ea-df94818395cc", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"66318", "nomdmonddf"=>"1", "nomdmonisw
Oct 18 16:24:25 node-1 nailgun-agent: "=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.916532 #11820] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.916571 #11820] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.916587 #11820] DEBUG -- : Device dm-5 seems to be appropriate
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.916602 #11820] DEBUG -- : Getting udev properties for device: ram0
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.918697 #11820] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89813", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.918737 #11820] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.918780 #11820] DEBUG -- : Device ram0 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.918813 #11820] DEBUG -- : Getting udev properties for device: ram1
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.920716 #11820] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90067", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.920754 #11820] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.920797 #11820] DEBUG -- : Device ram1 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.920821 #11820] DEBUG -- : Getting udev properties for device: ram2
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.922692 #11820] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90977", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.922757 #11820] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.922807 #11820] DEBUG -- : Device ram2 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.922833 #11820] DEBUG -- : Getting udev properties for device: ram3
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.924503 #11820] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"91109", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.924530 #11820] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.924572 #11820] DEBUG -- : Device ram3 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.924594 #11820] DEBUG -- : Getting udev properties for device: ram4
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.926264 #11820] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"91275", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.926291 #11820] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.926328 #11820] DEBUG -- : Device ram4 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.926348 #11820] DEBUG -- : Getting udev properties for device: ram5
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.928011 #11820] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"91558", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.928054 #11820] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.928092 #11820] DEBUG -- : Device ram5 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.928113 #11820] DEBUG -- : Getting udev properties for device: ram6
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.930021 #11820] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"92066", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.930065 #11820] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.930105 #11820] DEBUG -- : Device ram6 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.930130 #11820] DEBUG -- : Getting udev properties for device: ram7
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.931681 #11820] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"92442", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.931705 #11820] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.931740 #11820] DEBUG -- : Device ram7 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.931759 #11820] DEBUG -- : Getting udev properties for device: ram8
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.933333 #11820] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"92713", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.933357 #11820] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.933388 #11820] DEBUG -- : Device ram8 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.933434 #11820] DEBUG -- : Getting udev properties for device: ram9
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.937114 #11820] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93301", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.937165 #11820] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.937205 #11820] DEBUG -- : Device ram9 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.937245 #11820] DEBUG -- : Getting udev properties for device: loop0
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.938850 #11820] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88921", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.938876 #11820] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.938909 #11820] DEBUG -- : Device loop0 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.938929 #11820] DEBUG -- : Getting udev properties for device: loop1
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.940941 #11820] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89044", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.940984 #11820] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.941017 #11820] DEBUG -- : Device loop1 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.941036 #11820] DEBUG -- : Getting udev properties for device: loop2
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.942502 #11820] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89124", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.942566 #11820] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.942603 #11820] DEBUG -- : Device loop2 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.942623 #11820] DEBUG -- : Getting udev properties for device: loop3
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.944114 #11820] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89222", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.944140 #11820] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.944175 #11820] DEBUG -- : Device loop3 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.944195 #11820] DEBUG -- : Getting udev properties for device: loop4
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.945895 #11820] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89329", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.945920 #11820] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.945962 #11820] DEBUG -- : Device loop4 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.945982 #11820] DEBUG -- : Getting udev properties for device: loop5
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.947534 #11820] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89412", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.947559 #11820] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.947597 #11820] DEBUG -- : Device loop5 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.947617 #11820] DEBUG -- : Getting udev properties for device: loop6
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.949079 #11820] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89546", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.949106 #11820] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.949158 #11820] DEBUG -- : Device loop6 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.949179 #11820] DEBUG -- : Getting udev properties for device: loop7
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.950836 #11820] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89653", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.950875 #11820] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.950911 #11820] DEBUG -- : Device loop7 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.950942 #11820] DEBUG -- : Getting udev properties for device: ram10
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.952898 #11820] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90078", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.952923 #11820] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.952960 #11820] DEBUG -- : Device ram10 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.953003 #11820] DEBUG -- : Getting udev properties for device: ram11
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.954597 #11820] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90166", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.954660 #11820] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.954702 #11820] DEBUG -- : Device ram11 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.954721 #11820] DEBUG -- : Getting udev properties for device: ram12
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.956417 #11820] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90447", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.956442 #11820] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.956473 #11820] DEBUG -- : Device ram12 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.956491 #11820] DEBUG -- : Getting udev properties for device: ram13
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.957963 #11820] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90645", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.957988 #11820] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.958020 #11820] DEBUG -- : Device ram13 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.958039 #11820] DEBUG -- : Getting udev properties for device: ram14
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.959702 #11820] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90766", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.959727 #11820] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.959758 #11820] DEBUG -- : Device ram14 removable parameter: "0"
Oct 18 16:24:25 node-1 nailgun-agent: D, [2016-10-18T16:24:25.959816 #11820] DEBUG -- : Getting udev properties for device: ram15
Oct 18 16:24:25 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961430 #11820] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90901", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961458 #11820] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961490 #11820] DEBUG -- : Device ram15 removable parameter: "0"
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961571 #11820] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961589 #11820] DEBUG -- : Block device seems to be physical data storage: sda
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961636 #11820] DEBUG -- : Found block device: dm-0
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961650 #11820] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961663 #11820] DEBUG -- : Found block device: dm-1
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961674 #11820] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961730 #11820] DEBUG -- : Found block device: dm-2
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961740 #11820] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961749 #11820] DEBUG -- : Found block device: dm-3
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961760 #11820] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961770 #11820] DEBUG -- : Found block device: dm-4
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961780 #11820] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961788 #11820] DEBUG -- : Found block device: dm-5
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961831 #11820] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961840 #11820] DEBUG -- : Found block device: ram0
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961850 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961858 #11820] DEBUG -- : Found block device: ram1
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961868 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961921 #11820] DEBUG -- : Found block device: ram2
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961932 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961941 #11820] DEBUG -- : Found block device: ram3
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961951 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961958 #11820] DEBUG -- : Found block device: ram4
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961968 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961976 #11820] DEBUG -- : Found block device: ram5
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.961987 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962032 #11820] DEBUG -- : Found block device: ram6
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962044 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962053 #11820] DEBUG -- : Found block device: ram7
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962062 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962070 #11820] DEBUG -- : Found block device: ram8
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962102 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962111 #11820] DEBUG -- : Found block device: ram9
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962121 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962129 #11820] DEBUG -- : Found block device: loop0
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962158 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962167 #11820] DEBUG -- : Found block device: loop1
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962176 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962214 #11820] DEBUG -- : Found block device: loop2
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962225 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962233 #11820] DEBUG -- : Found block device: loop3
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962243 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962252 #11820] DEBUG -- : Found block device: loop4
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962261 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962295 #11820] DEBUG -- : Found block device: loop5
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962305 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962313 #11820] DEBUG -- : Found block device: loop6
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962323 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962331 #11820] DEBUG -- : Found block device: loop7
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962341 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962370 #11820] DEBUG -- : Found block device: ram10
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962380 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962388 #11820] DEBUG -- : Found block device: ram11
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962397 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962404 #11820] DEBUG -- : Found block device: ram12
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962413 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962420 #11820] DEBUG -- : Found block device: ram13
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962450 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962459 #11820] DEBUG -- : Found block device: ram14
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962470 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962478 #11820] DEBUG -- : Found block device: ram15
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962487 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:25.962535 #11820] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:26.045623 #11820] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 18 16:24:26 node-1 nailgun-agent: D, [2016-10-18T16:24:26.045676 #11820] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 18 16:24:38 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270250 #11820] DEBUG -- : Trying to find block devices
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270479 #11820] DEBUG -- : Found block device: sda
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270566 #11820] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270623 #11820] DEBUG -- : Block device seems to be physical data storage: sda
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270738 #11820] DEBUG -- : Found block device: dm-0
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270780 #11820] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270813 #11820] DEBUG -- : Found block device: dm-1
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270840 #11820] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270869 #11820] DEBUG -- : Found block device: dm-2
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270899 #11820] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270924 #11820] DEBUG -- : Found block device: dm-3
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270949 #11820] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.270974 #11820] DEBUG -- : Found block device: dm-4
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271004 #11820] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271030 #11820] DEBUG -- : Found block device: dm-5
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271114 #11820] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271140 #11820] DEBUG -- : Found block device: ram0
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271166 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271190 #11820] DEBUG -- : Found block device: ram1
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271215 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271239 #11820] DEBUG -- : Found block device: ram2
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271265 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271291 #11820] DEBUG -- : Found block device: ram3
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271317 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271340 #11820] DEBUG -- : Found block device: ram4
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271383 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271464 #11820] DEBUG -- : Found block device: ram5
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271493 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271519 #11820] DEBUG -- : Found block device: ram6
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271545 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271570 #11820] DEBUG -- : Found block device: ram7
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271597 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271621 #11820] DEBUG -- : Found block device: ram8
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271647 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271673 #11820] DEBUG -- : Found block device: ram9
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271701 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271781 #11820] DEBUG -- : Found block device: loop0
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271810 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271837 #11820] DEBUG -- : Found block device: loop1
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271863 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271886 #11820] DEBUG -- : Found block device: loop2
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271912 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271934 #11820] DEBUG -- : Found block device: loop3
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271961 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.271985 #11820] DEBUG -- : Found block device: loop4
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272011 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272037 #11820] DEBUG -- : Found block device: loop5
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272104 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272128 #11820] DEBUG -- : Found block device: loop6
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272153 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272177 #11820] DEBUG -- : Found block device: loop7
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272201 #11820] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272225 #11820] DEBUG -- : Found block device: ram10
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272293 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272320 #11820] DEBUG -- : Found block device: ram11
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272348 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272372 #11820] DEBUG -- : Found block device: ram12
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272398 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272421 #11820] DEBUG -- : Found block device: ram13
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272445 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272519 #11820] DEBUG -- : Found block device: ram14
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272547 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272570 #11820] DEBUG -- : Found block device: ram15
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272595 #11820] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.272667 #11820] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct 18 16:24:38 node-1 nailgun-agent: D, [2016-10-18T16:24:38.454946 #11820] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 18 16:24:38 node-1 nailgun-agent: I, [2016-10-18T16:24:38.455321 #11820]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 18 16:24:51 node-1 puppet-user[14479]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 18 16:24:51 node-1 puppet-user[14479]: Finished catalog run in 29.82 seconds
Oct 18 16:24:53 node-1 puppet-user[17563]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 18 16:24:53 node-1 puppet-user[17563]: Compiled catalog for node-1.domain.tld in environment production in 0.61 seconds
Oct 18 16:24:54 node-1 puppet-user[17563]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 18 16:24:54 node-1 puppet-user[17563]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 18 16:24:54 node-1 puppet-user[17563]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 18 16:24:54 node-1 puppet-user[17563]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 18 16:24:54 node-1 puppet-user[17563]: Finished catalog run in 0.10 seconds
Oct 18 16:24:55 node-1 puppet-user[18021]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 18 16:24:56 node-1 puppet-user[18021]: Compiled catalog for node-1.domain.tld in environment production in 0.92 seconds
Oct 18 16:24:57 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 18 16:24:57 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 18 16:24:57 node-1 crontab[18453]: (root) LIST (root)
Oct 18 16:24:57 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 18 16:24:57 node-1 crontab[18454]: (root) REPLACE (root)
Oct 18 16:24:58 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 18 16:24:59 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 18 16:25:00 node-1 puppet-user[18021]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 18 16:25:00 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8394" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:00 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 18 16:25:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:14 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:14 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:14 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:14 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:14 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:16 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:16 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:16 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:16 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:16 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:25:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:13 node-1 ntpdate[29390]: no servers can be used, exiting
<27>Oct 18 16:26:13 node-1 ntpdate[29496]: no servers can be used, exiting
<27>Oct 18 16:26:13 node-1 ntpdate[29644]: no servers can be used, exiting
<27>Oct 18 16:26:13 node-1 ntpdate[29826]: no servers can be used, exiting
<27>Oct 18 16:26:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:26:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:04 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:04 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:04 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:04 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:04 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:27:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:05 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:05 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:05 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:05 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:05 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:08 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 18 16:28:08 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 18 16:28:14 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 18 16:28:14 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 18 16:28:19 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 18 16:28:25 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 18 16:28:25 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 18 16:28:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:28:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:20 node-1 multipathd: uevent trigger error
<129>Oct 18 16:29:22 node-1 haproxy[24075]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 88ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:22 node-1 haproxy[24075]: proxy odl-neutron-endpoint has no server available!
<129>Oct 18 16:29:23 node-1 haproxy[24081]: Server odl-jetty/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 4ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:23 node-1 haproxy[24081]: proxy odl-jetty has no server available!
<27>Oct 18 16:29:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:46 node-1 multipathd: uevent trigger error
<129>Oct 18 16:29:48 node-1 haproxy[26518]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:49 node-1 haproxy[26522]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:49 node-1 haproxy[26522]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:49 node-1 haproxy[26522]: proxy mysqld has no server available!
<27>Oct 18 16:29:52 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:52 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:52 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:52 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:52 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:55 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:55 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:55 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:55 node-1 multipathd: uevent trigger error
<27>Oct 18 16:29:55 node-1 multipathd: uevent trigger error
<129>Oct 18 16:29:57 node-1 haproxy[29081]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:58 node-1 haproxy[29085]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:58 node-1 haproxy[29085]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:58 node-1 haproxy[29085]: proxy mysqld has no server available!
<129>Oct 18 16:29:58 node-1 haproxy[29085]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:58 node-1 haproxy[29085]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:59 node-1 haproxy[29085]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:59 node-1 haproxy[29085]: proxy object-storage has no server available!
<27>Oct 18 16:30:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:00 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:03 node-1 haproxy[30460]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:03 node-1 haproxy[30460]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:03 node-1 haproxy[30460]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:03 node-1 haproxy[30460]: proxy neutron has no server available!
<129>Oct 18 16:30:03 node-1 haproxy[30460]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:03 node-1 haproxy[30460]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:04 node-1 haproxy[30464]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:04 node-1 haproxy[30464]: proxy mysqld has no server available!
<129>Oct 18 16:30:04 node-1 haproxy[30464]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:04 node-1 haproxy[30464]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:04 node-1 haproxy[30464]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:04 node-1 haproxy[30464]: proxy object-storage has no server available!
<27>Oct 18 16:30:06 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:06 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:06 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:06 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:06 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:08 node-1 haproxy[31825]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:08 node-1 haproxy[31825]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:08 node-1 haproxy[31825]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:08 node-1 haproxy[31825]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:09 node-1 haproxy[31829]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:09 node-1 haproxy[31829]: proxy neutron has no server available!
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:09 node-1 haproxy[31829]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:09 node-1 haproxy[31829]: proxy mysqld has no server available!
<129>Oct 18 16:30:10 node-1 haproxy[31829]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:10 node-1 haproxy[31829]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:10 node-1 haproxy[31829]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:10 node-1 haproxy[31829]: proxy object-storage has no server available!
<27>Oct 18 16:30:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:11 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:14 node-1 haproxy[727]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:14 node-1 haproxy[727]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:14 node-1 haproxy[727]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:14 node-1 haproxy[727]: proxy neutron has no server available!
<129>Oct 18 16:30:15 node-1 haproxy[731]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-1 haproxy[731]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-1 haproxy[731]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:15 node-1 haproxy[731]: proxy mysqld has no server available!
<129>Oct 18 16:30:15 node-1 haproxy[731]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-1 haproxy[731]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-1 haproxy[731]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:15 node-1 haproxy[731]: proxy object-storage has no server available!
<129>Oct 18 16:30:15 node-1 haproxy[731]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-1 haproxy[731]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-1 haproxy[731]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:15 node-1 haproxy[731]: proxy aodh has no server available!
<27>Oct 18 16:30:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:20 node-1 haproxy[2259]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:20 node-1 haproxy[2259]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:20 node-1 haproxy[2259]: proxy neutron has no server available!
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:20 node-1 haproxy[2259]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:20 node-1 haproxy[2259]: proxy mysqld has no server available!
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:21 node-1 haproxy[2263]: proxy object-storage has no server available!
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:21 node-1 haproxy[2263]: proxy aodh has no server available!
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-1 haproxy[2263]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:21 node-1 haproxy[2263]: proxy ceilometer has no server available!
<27>Oct 18 16:30:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:25 node-1 haproxy[3556]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:25 node-1 haproxy[3556]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:25 node-1 haproxy[3556]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:25 node-1 haproxy[3556]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:25 node-1 haproxy[3556]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:25 node-1 haproxy[3556]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:25 node-1 haproxy[3556]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:25 node-1 haproxy[3556]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:25 node-1 haproxy[3556]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:26 node-1 haproxy[3560]: proxy neutron has no server available!
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:26 node-1 haproxy[3560]: proxy mysqld has no server available!
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:26 node-1 haproxy[3560]: proxy object-storage has no server available!
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:26 node-1 haproxy[3560]: proxy aodh has no server available!
<129>Oct 18 16:30:26 node-1 haproxy[3560]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:27 node-1 haproxy[3560]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:27 node-1 haproxy[3560]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:27 node-1 haproxy[3560]: proxy ceilometer has no server available!
<27>Oct 18 16:30:28 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:28 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:28 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:28 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:28 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:30 node-1 haproxy[5133]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:30 node-1 haproxy[5133]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:30 node-1 haproxy[5133]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:30 node-1 haproxy[5133]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:30 node-1 haproxy[5133]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-1 haproxy[5137]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-1 haproxy[5137]: proxy neutron has no server available!
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-1 haproxy[5137]: proxy mysqld has no server available!
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-1 haproxy[5137]: proxy object-storage has no server available!
<129>Oct 18 16:30:31 node-1 haproxy[5137]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-1 haproxy[5137]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-1 haproxy[5137]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:32 node-1 haproxy[5137]: proxy aodh has no server available!
<129>Oct 18 16:30:32 node-1 haproxy[5137]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-1 haproxy[5137]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-1 haproxy[5137]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:32 node-1 haproxy[5137]: proxy ceilometer has no server available!
<27>Oct 18 16:30:33 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:33 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:33 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:33 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:33 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:36 node-1 haproxy[6604]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:36 node-1 haproxy[6604]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:36 node-1 haproxy[6604]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:37 node-1 haproxy[6611]: proxy glance-api has no server available!
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:37 node-1 haproxy[6611]: proxy glance-glare has no server available!
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:37 node-1 haproxy[6611]: proxy neutron has no server available!
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:37 node-1 haproxy[6611]: proxy glance-registry has no server available!
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:37 node-1 haproxy[6611]: proxy mysqld has no server available!
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:37 node-1 haproxy[6611]: proxy object-storage has no server available!
<129>Oct 18 16:30:37 node-1 haproxy[6611]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:38 node-1 haproxy[6611]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:38 node-1 haproxy[6611]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:38 node-1 haproxy[6611]: proxy aodh has no server available!
<129>Oct 18 16:30:38 node-1 haproxy[6611]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:38 node-1 haproxy[6611]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:38 node-1 haproxy[6611]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:38 node-1 haproxy[6611]: proxy ceilometer has no server available!
<27>Oct 18 16:30:39 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:39 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:39 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:39 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:42 node-1 haproxy[8105]: proxy keystone-1 has no server available!
<27>Oct 18 16:30:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:42 node-1 haproxy[8105]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:42 node-1 haproxy[8105]: proxy nova-api has no server available!
<129>Oct 18 16:30:42 node-1 haproxy[8105]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:43 node-1 haproxy[8109]: proxy nova-metadata-api has no server available!
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:43 node-1 haproxy[8109]: proxy glance-api has no server available!
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:43 node-1 haproxy[8109]: proxy glance-glare has no server available!
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:43 node-1 haproxy[8109]: proxy neutron has no server available!
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:43 node-1 haproxy[8109]: proxy glance-registry has no server available!
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:43 node-1 haproxy[8109]: proxy mysqld has no server available!
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:43 node-1 haproxy[8109]: proxy object-storage has no server available!
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:43 node-1 haproxy[8109]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:44 node-1 haproxy[8109]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:44 node-1 haproxy[8109]: proxy aodh has no server available!
<129>Oct 18 16:30:44 node-1 haproxy[8109]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:44 node-1 haproxy[8109]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:44 node-1 haproxy[8109]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:44 node-1 haproxy[8109]: proxy ceilometer has no server available!
<129>Oct 18 16:30:44 node-1 haproxy[8109]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:44 node-1 haproxy[8109]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:44 node-1 haproxy[8109]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:44 node-1 haproxy[8109]: proxy nova-novncproxy has no server available!
<27>Oct 18 16:30:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:45 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:48 node-1 haproxy[9566]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:48 node-1 haproxy[9566]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:48 node-1 haproxy[9566]: proxy nova-api has no server available!
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:48 node-1 haproxy[9566]: proxy nova-metadata-api has no server available!
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:48 node-1 haproxy[9566]: proxy cinder-api has no server available!
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:48 node-1 haproxy[9566]: proxy glance-api has no server available!
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:48 node-1 haproxy[9566]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy glance-glare has no server available!
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy neutron has no server available!
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy glance-registry has no server available!
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy mysqld has no server available!
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy object-storage has no server available!
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy aodh has no server available!
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy ceilometer has no server available!
<129>Oct 18 16:30:49 node-1 haproxy[9575]: 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.
<27>Oct 18 16:30:49 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:49 node-1 haproxy[9575]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:49 node-1 haproxy[9575]: proxy nova-novncproxy has no server available!
<27>Oct 18 16:30:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:51 node-1 multipathd: uevent trigger error
<129>Oct 18 16:30:53 node-1 haproxy[11194]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy nova-api has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy nova-metadata-api has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy cinder-api has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy glance-api has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy glance-glare has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:54 node-1 haproxy[11198]: proxy neutron has no server available!
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:54 node-1 haproxy[11198]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy glance-registry has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy mysqld has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy object-storage has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy aodh has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy ceilometer has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy heat-api has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy heat-api-cfn has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy heat-api-cloudwatch has no server available!
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:55 node-1 haproxy[11198]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:55 node-1 haproxy[11198]: proxy nova-novncproxy has no server available!
<27>Oct 18 16:30:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:30:57 node-1 multipathd: uevent trigger error
<27>Oct 18 16:31:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:31:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:31:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:31:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:31:00 node-1 multipathd: uevent trigger error
<27>Oct 18 16:31:08 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 18 16:31:32 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Oct 18 16:31:34 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 18 16:32:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:33:59 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:34:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:34:49 node-1 multipathd: uevent trigger error
<43>Oct 18 16:35:01 node-1 apache2_error [Tue Oct 18 16:34:59.684721 2016] [mpm_event:notice] [pid 22949:tid 140009296250752] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 18 16:35:01 node-1 apache2_error [Tue Oct 18 16:34:59.684864 2016] [core:notice] [pid 22949:tid 140009296250752] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:35:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:08 node-1 multipathd: uevent trigger error
<43>Oct 18 16:35:11 node-1 apache2_error [Tue Oct 18 16:35:02.597725 2016] [mpm_event:notice] [pid 22949:tid 140009296250752] AH00491: caught SIGTERM, shutting down
<43>Oct 18 16:35:11 node-1 apache2_error [Tue Oct 18 16:35:03.696026 2016] [mpm_worker:notice] [pid 23451:tid 140393365383040] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 18 16:35:11 node-1 apache2_error [Tue Oct 18 16:35:03.696088 2016] [core:notice] [pid 23451:tid 140393365383040] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:35:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:35:11 node-1 multipathd: uevent trigger error
<43>Oct 18 16:36:21 node-1 apache2_error [Tue Oct 18 16:36:12.736611 2016] [mpm_worker:notice] [pid 23451:tid 140393365383040] AH00295: caught SIGTERM, shutting down
<43>Oct 18 16:36:21 node-1 apache2_error [Tue Oct 18 16:36:13.500289 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:36:21 node-1 apache2_error [Tue Oct 18 16:36:13.500348 2016] [core:notice] [pid 3245:tid 140400918886272] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 18 16:37:01 node-1 apache2_error [Tue Oct 18 16:36:57.012252 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:37:01 node-1 apache2_error [Tue Oct 18 16:36:57.208561 2016] [mpm_worker:warn] [pid 3245:tid 140400918886272] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:37:01 node-1 apache2_error [Tue Oct 18 16:36:57.213517 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:37:01 node-1 apache2_error [Tue Oct 18 16:36:57.213548 2016] [core:notice] [pid 3245:tid 140400918886272] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:37:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:37:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:37:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:26 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:26 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:26 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:26 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:26 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:31 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:31 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:31 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:31 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:31 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:38:49 node-1 multipathd: uevent trigger error
<27>Oct 18 16:39:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:39:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:39:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:39:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:39:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:40:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:40:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:40:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:40:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:40:51 node-1 multipathd: uevent trigger error
<27>Oct 18 16:41:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:41:46 node-1 multipathd: uevent trigger error
<27>Oct 18 16:41:47 node-1 multipathd: uevent trigger error
<27>Oct 18 16:41:47 node-1 multipathd: uevent trigger error
<27>Oct 18 16:41:47 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:42:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:43:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:44:34 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:34 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:34 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:34 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:34 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:34 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:56 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:56 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:56 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:56 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:56 node-1 multipathd: uevent trigger error
<27>Oct 18 16:44:56 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:01 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:45:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:46:53 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:53 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:53 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:53 node-1 multipathd: uevent trigger error
<27>Oct 18 16:46:53 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:47:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:49:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:49:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:49:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:49:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:49:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:49:45 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:50:25 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:02 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:06 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:06 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:07 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:07 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:23 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:51:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:52:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:52:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:52:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:52:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:52:08 node-1 multipathd: uevent trigger error
<27>Oct 18 16:52:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:53:10 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:10 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:10 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:53:27 node-1 multipathd: uevent trigger error
<11>Oct 18 16:53:40 node-1 liberasurecode[18346]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:40 node-1 liberasurecode[18346]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:40 node-1 liberasurecode[18346]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:40 node-1 liberasurecode[18346]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:40 node-1 liberasurecode[18372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:40 node-1 liberasurecode[18372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:40 node-1 liberasurecode[18372]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:40 node-1 liberasurecode[18372]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:42 node-1 liberasurecode[18781]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:42 node-1 liberasurecode[18781]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:42 node-1 liberasurecode[18781]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:42 node-1 liberasurecode[18781]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19391]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19391]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19391]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19391]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19439]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19439]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19439]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19439]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:46 node-1 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19518]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19518]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19518]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19518]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19537]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19537]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19537]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19537]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:53:47 node-1 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:03 node-1 liberasurecode[22129]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:03 node-1 liberasurecode[22129]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:03 node-1 liberasurecode[22129]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:03 node-1 liberasurecode[22129]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 18 16:54:12 node-1 multipathd: uevent trigger error
<27>Oct 18 16:54:12 node-1 multipathd: uevent trigger error
<27>Oct 18 16:54:12 node-1 multipathd: uevent trigger error
<27>Oct 18 16:54:12 node-1 multipathd: uevent trigger error
<27>Oct 18 16:54:12 node-1 multipathd: uevent trigger error
<11>Oct 18 16:55:01 node-1 liberasurecode[31462]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:55:01 node-1 liberasurecode[31462]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:55:01 node-1 liberasurecode[31462]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:55:01 node-1 liberasurecode[31462]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Oct 18 16:55:02 node-1 apache2_error [Tue Oct 18 16:54:58.718262 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:55:02 node-1 apache2_error [Tue Oct 18 16:54:59.098512 2016] [mpm_worker:warn] [pid 3245:tid 140400918886272] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:55:02 node-1 apache2_error [Tue Oct 18 16:54:59.102561 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:55:02 node-1 apache2_error [Tue Oct 18 16:54:59.102588 2016] [core:notice] [pid 3245:tid 140400918886272] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:55:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 18 16:55:40 node-1 multipathd: uevent trigger error
<43>Oct 18 16:55:42 node-1 apache2_error [Tue Oct 18 16:55:35.947571 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:55:42 node-1 apache2_error [Tue Oct 18 16:55:36.140476 2016] [mpm_worker:warn] [pid 3245:tid 140400918886272] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:55:42 node-1 apache2_error [Tue Oct 18 16:55:36.148009 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:55:42 node-1 apache2_error [Tue Oct 18 16:55:36.148049 2016] [core:notice] [pid 3245:tid 140400918886272] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:56:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:11 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:24 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:24 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:24 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:24 node-1 multipathd: uevent trigger error
<27>Oct 18 16:56:24 node-1 multipathd: uevent trigger error
<43>Oct 18 16:57:02 node-1 apache2_error [Tue Oct 18 16:56:59.168923 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:57:02 node-1 apache2_error [Tue Oct 18 16:56:59.553124 2016] [mpm_worker:warn] [pid 3245:tid 140400918886272] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:57:02 node-1 apache2_error [Tue Oct 18 16:56:59.563956 2016] [mpm_worker:notice] [pid 3245:tid 140400918886272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:57:02 node-1 apache2_error [Tue Oct 18 16:56:59.563983 2016] [core:notice] [pid 3245:tid 140400918886272] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:57:03 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:03 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:03 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:03 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:03 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:03 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:15 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:19 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:29 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:57:44 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:04 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:11 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 18 16:58:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:20 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:27 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:38 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:17 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 18 16:59:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:17 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:22 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:22 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:22 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:22 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:42 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:42 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:42 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:42 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:43 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:47 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:47 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:47 node-1 multipathd: uevent trigger error
<27>Oct 18 16:59:47 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:00 node-1 multipathd: uevent trigger error
<11>Oct 18 17:00:01 node-1 liberasurecode[5152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 17:00:01 node-1 liberasurecode[5152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 17:00:01 node-1 liberasurecode[5152]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 17:00:01 node-1 liberasurecode[5152]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 18 17:00:30 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:30 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:30 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:30 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:30 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:34 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:34 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:34 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:34 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:34 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:39 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:39 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:39 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:39 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:39 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:49 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:49 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:49 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:49 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:49 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:53 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:53 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:53 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:53 node-1 multipathd: uevent trigger error
<27>Oct 18 17:00:53 node-1 multipathd: uevent trigger error
