Oct 18 16:23:31 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8426" x-info="http://www.rsyslog.com"] start
Oct 18 16:23:31 node-2 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-2 rsyslogd: rsyslogd's groupid changed to 104
Oct 18 16:23:31 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct 18 16:23:31 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 18 16:23:31 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 18 16:23:31 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 18 16:23:31 node-2 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-2 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-2 kernel: [    0.000000] KERNEL supported cpus:
Oct 18 16:23:31 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct 18 16:23:31 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct 18 16:23:31 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct 18 16:23:31 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 18 16:23:31 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 18 16:23:31 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 18 16:23:31 node-2 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-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 18 16:23:31 node-2 kernel: [    0.000000] No AGP bridge found
Oct 18 16:23:31 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 18 16:23:31 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct 18 16:23:31 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 18 16:23:31 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct 18 16:23:31 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 18 16:23:31 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 18 16:23:31 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 18 16:23:31 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 18 16:23:31 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 18 16:23:31 node-2 kernel: [    0.000000]   2 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000]   3 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000]   4 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000]   5 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000]   6 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000]   7 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000]   8 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000]   9 disabled
Oct 18 16:23:31 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 18 16:23:31 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 18 16:23:31 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 18 16:23:31 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 18 16:23:31 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 18 16:23:31 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 18 16:23:31 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 18 16:23:31 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 18 16:23:31 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 18 16:23:31 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 18 16:23:31 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 18 16:23:31 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35828000-0x36c0bfff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 18 16:23:31 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 18 16:23:31 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 18 16:23:31 node-2 kernel: [    0.000000] Zone ranges:
Oct 18 16:23:31 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] Movable zone start for each node
Oct 18 16:23:31 node-2 kernel: [    0.000000] Early memory node ranges
Oct 18 16:23:31 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 18 16:23:31 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 18 16:23:31 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 18 16:23:31 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 18 16:23:31 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 18 16:23:31 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 18 16:23:31 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 18 16:23:31 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 18 16:23:31 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 18 16:23:31 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 18 16:23:31 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 18 16:23:31 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 18 16:23:31 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 18 16:23:31 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 18 16:23:31 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 18 16:23:31 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 18 16:23:31 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 18 16:23:31 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 18 16:23:31 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 18 16:23:31 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 18 16:23:31 node-2 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-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 18 16:23:31 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 18 16:23:31 node-2 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-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 18 16:23:31 node-2 kernel: [    0.000000] Policy zone: Normal
Oct 18 16:23:31 node-2 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-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 18 16:23:31 node-2 kernel: [    0.000000] Checking aperture...
Oct 18 16:23:31 node-2 kernel: [    0.000000] No AGP bridge found
Oct 18 16:23:31 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 18 16:23:31 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 18 16:23:31 node-2 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-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 18 16:23:31 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 18 16:23:31 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 18 16:23:31 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 18 16:23:31 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 18 16:23:31 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 18 16:23:31 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 18 16:23:31 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 18 16:23:31 node-2 kernel: [    0.000000] console [tty0] enabled
Oct 18 16:23:31 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 18 16:23:31 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 18 16:23:31 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 18 16:23:31 node-2 kernel: [    0.000000] hpet clockevent registered
Oct 18 16:23:31 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 18 16:23:31 node-2 kernel: [    0.004000] tsc: Detected 3492.026 MHz processor
Oct 18 16:23:31 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.05 BogoMIPS (lpj=13968104)
Oct 18 16:23:31 node-2 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 18 16:23:31 node-2 kernel: [    0.000045] Security Framework initialized
Oct 18 16:23:31 node-2 kernel: [    0.000064] AppArmor: AppArmor initialized
Oct 18 16:23:31 node-2 kernel: [    0.000065] Yama: becoming mindful.
Oct 18 16:23:31 node-2 kernel: [    0.001477] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.006419] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.008340] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.008368] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.008644] Initializing cgroup subsys memory
Oct 18 16:23:31 node-2 kernel: [    0.008652] Initializing cgroup subsys devices
Oct 18 16:23:31 node-2 kernel: [    0.008654] Initializing cgroup subsys freezer
Oct 18 16:23:31 node-2 kernel: [    0.008655] Initializing cgroup subsys blkio
Oct 18 16:23:31 node-2 kernel: [    0.008657] Initializing cgroup subsys perf_event
Oct 18 16:23:31 node-2 kernel: [    0.008659] Initializing cgroup subsys hugetlb
Oct 18 16:23:31 node-2 kernel: [    0.008678] CPU: Physical Processor ID: 0
Oct 18 16:23:31 node-2 kernel: [    0.008679] CPU: Processor Core ID: 0
Oct 18 16:23:31 node-2 kernel: [    0.008683] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 18 16:23:31 node-2 kernel: [    0.008683] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 18 16:23:31 node-2 kernel: [    0.009377] mce: CPU supports 22 MCE banks
Oct 18 16:23:31 node-2 kernel: [    0.009404] CPU0: Thermal monitoring enabled (TM1)
Oct 18 16:23:31 node-2 kernel: [    0.009425] process: using mwait in idle threads
Oct 18 16:23:31 node-2 kernel: [    0.009428] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 18 16:23:31 node-2 kernel: [    0.009428] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 18 16:23:31 node-2 kernel: [    0.009428] tlb_flushall_shift: 6
Oct 18 16:23:31 node-2 kernel: [    0.009517] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 18 16:23:31 node-2 kernel: [    0.010239] ACPI: Core revision 20131115
Oct 18 16:23:31 node-2 kernel: [    0.023077] ACPI: All ACPI Tables successfully acquired
Oct 18 16:23:31 node-2 kernel: [    0.023237] ftrace: allocating 28622 entries in 112 pages
Oct 18 16:23:31 node-2 kernel: [    0.032003] dmar: Host address width 46
Oct 18 16:23:31 node-2 kernel: [    0.032005] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 18 16:23:31 node-2 kernel: [    0.032011] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 18 16:23:31 node-2 kernel: [    0.032013] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 18 16:23:31 node-2 kernel: [    0.032017] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 18 16:23:31 node-2 kernel: [    0.032018] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 18 16:23:31 node-2 kernel: [    0.032020] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 18 16:23:31 node-2 kernel: [    0.032021] dmar: ATSR flags: 0x0
Oct 18 16:23:31 node-2 kernel: [    0.032022] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 18 16:23:31 node-2 kernel: [    0.032023] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 18 16:23:31 node-2 kernel: [    0.032139] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 18 16:23:31 node-2 kernel: [    0.032140] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 18 16:23:31 node-2 kernel: [    0.032141] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 18 16:23:31 node-2 kernel: [    0.032142] HPET id 0 under DRHD base 0xc7ffc000
Oct 18 16:23:31 node-2 kernel: [    0.032143] Your BIOS is broken and requested that x2apic be disabled.
Oct 18 16:23:31 node-2 kernel: [    0.032143] This will slightly decrease performance.
Oct 18 16:23:31 node-2 kernel: [    0.032143] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 18 16:23:31 node-2 kernel: [    0.032577] Enabled IRQ remapping in xapic mode
Oct 18 16:23:31 node-2 kernel: [    0.032578] x2apic not enabled, IRQ remapping is in xapic mode
Oct 18 16:23:31 node-2 kernel: [    0.032582] Switched APIC routing to physical flat.
Oct 18 16:23:31 node-2 kernel: [    0.033189] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 18 16:23:31 node-2 kernel: [    0.072840] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 18 16:23:31 node-2 kernel: [    0.072846] TSC deadline timer enabled
Oct 18 16:23:31 node-2 kernel: [    0.072854] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 18 16:23:31 node-2 kernel: [    0.072860] ... version:                3
Oct 18 16:23:31 node-2 kernel: [    0.072861] ... bit width:              48
Oct 18 16:23:31 node-2 kernel: [    0.072861] ... generic registers:      4
Oct 18 16:23:31 node-2 kernel: [    0.072862] ... value mask:             0000ffffffffffff
Oct 18 16:23:31 node-2 kernel: [    0.072863] ... max period:             0000ffffffffffff
Oct 18 16:23:31 node-2 kernel: [    0.072864] ... fixed-purpose events:   3
Oct 18 16:23:31 node-2 kernel: [    0.072865] ... event mask:             000000070000000f
Oct 18 16:23:31 node-2 kernel: [    0.074280] x86: Booting SMP configuration:
Oct 18 16:23:31 node-2 kernel: [    0.088482] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 18 16:23:31 node-2 kernel: [    0.074282] .... node  #0, CPUs:        #1  #2  #3
Oct 18 16:23:31 node-2 kernel: [    0.116391] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 18 16:23:31 node-2 kernel: [    0.270563] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 18 16:23:31 node-2 kernel: [    0.326184] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 18 16:23:31 node-2 kernel: [    0.383253] x86: Booted up 2 nodes, 16 CPUs
Oct 18 16:23:31 node-2 kernel: [    0.383256] smpboot: Total of 16 processors activated (111757.71 BogoMIPS)
Oct 18 16:23:31 node-2 kernel: [    0.407879] devtmpfs: initialized
Oct 18 16:23:31 node-2 kernel: [    0.410370] EVM: security.selinux
Oct 18 16:23:31 node-2 kernel: [    0.410371] EVM: security.SMACK64
Oct 18 16:23:31 node-2 kernel: [    0.410372] EVM: security.ima
Oct 18 16:23:31 node-2 kernel: [    0.410373] EVM: security.capability
Oct 18 16:23:31 node-2 kernel: [    0.410422] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.411056] pinctrl core: initialized pinctrl subsystem
Oct 18 16:23:31 node-2 kernel: [    0.411113] regulator-dummy: no parameters
Oct 18 16:23:31 node-2 kernel: [    0.411144] RTC time: 16:22:55, date: 10/18/16
Oct 18 16:23:31 node-2 kernel: [    0.411178] NET: Registered protocol family 16
Oct 18 16:23:31 node-2 kernel: [    0.411263] cpuidle: using governor ladder
Oct 18 16:23:31 node-2 kernel: [    0.411265] cpuidle: using governor menu
Oct 18 16:23:31 node-2 kernel: [    0.411299] ACPI: bus type PCI registered
Oct 18 16:23:31 node-2 kernel: [    0.411301] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 18 16:23:31 node-2 kernel: [    0.411347] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 18 16:23:31 node-2 kernel: [    0.411357] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 18 16:23:31 node-2 kernel: [    0.425088] PCI: Using configuration type 1 for base access
Oct 18 16:23:31 node-2 kernel: [    0.426096] bio: create slab <bio-0> at 0
Oct 18 16:23:31 node-2 kernel: [    0.426379] ACPI: Added _OSI(Module Device)
Oct 18 16:23:31 node-2 kernel: [    0.426380] ACPI: Added _OSI(Processor Device)
Oct 18 16:23:31 node-2 kernel: [    0.426382] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 18 16:23:31 node-2 kernel: [    0.426383] ACPI: Added _OSI(Processor Aggregator Device)
Oct 18 16:23:31 node-2 kernel: [    0.439135] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 18 16:23:31 node-2 kernel: [    0.450888] ACPI: Interpreter enabled
Oct 18 16:23:31 node-2 kernel: [    0.450893] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 18 16:23:31 node-2 kernel: [    0.450898] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 18 16:23:31 node-2 kernel: [    0.450900] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 18 16:23:31 node-2 kernel: [    0.450907] ACPI: (supports S0 S4 S5)
Oct 18 16:23:31 node-2 kernel: [    0.450908] ACPI: Using IOAPIC for interrupt routing
Oct 18 16:23:31 node-2 kernel: [    0.450950] HEST: Table parsing has been initialized.
Oct 18 16:23:31 node-2 kernel: [    0.450953] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 18 16:23:31 node-2 kernel: [    0.451509] ACPI: No dock devices found.
Oct 18 16:23:31 node-2 kernel: [    0.463009] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 18 16:23:31 node-2 kernel: [    0.463013] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-2 kernel: [    0.463017] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 18 16:23:31 node-2 kernel: [    0.463046] PCI host bridge to bus 0000:ff
Oct 18 16:23:31 node-2 kernel: [    0.463048] pci_bus 0000:ff: root bus resource [bus ff]
Oct 18 16:23:31 node-2 kernel: [    0.463056] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463094] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.463125] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463161] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463190] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.463220] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.463252] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463281] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463312] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463340] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463367] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463393] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463422] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463448] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463474] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463501] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463530] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463558] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463586] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.463614] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463640] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.463666] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463692] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463723] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.463758] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463789] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463819] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463849] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463880] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463911] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463942] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.463972] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464003] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464036] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464069] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464102] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464136] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464167] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464194] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464225] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464258] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464295] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464329] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464362] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464392] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464421] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464451] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464483] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464516] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464548] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464580] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464610] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464642] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464672] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464702] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464734] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464767] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464824] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 18 16:23:31 node-2 kernel: [    0.464827] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-2 kernel: [    0.464830] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 18 16:23:31 node-2 kernel: [    0.464848] PCI host bridge to bus 0000:7f
Oct 18 16:23:31 node-2 kernel: [    0.464850] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 18 16:23:31 node-2 kernel: [    0.464855] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464883] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.464911] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464939] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.464965] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.464990] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.465016] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465043] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465068] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465091] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465113] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465136] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465160] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465182] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465206] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465231] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465253] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465276] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465298] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.465322] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465344] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.465366] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465388] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465416] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 18 16:23:31 node-2 kernel: [    0.465450] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465478] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465509] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465537] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465562] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465590] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465618] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465648] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465675] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465703] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465731] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465759] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465788] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465815] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465842] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465870] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465895] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465921] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465949] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.465976] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466003] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466028] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466054] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466081] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466108] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466134] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466164] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466189] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466211] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466234] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466259] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466290] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.466316] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.467570] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 18 16:23:31 node-2 kernel: [    0.467574] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-2 kernel: [    0.468704] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 18 16:23:31 node-2 kernel: [    0.469222] PCI host bridge to bus 0000:00
Oct 18 16:23:31 node-2 kernel: [    0.469224] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 18 16:23:31 node-2 kernel: [    0.469226] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 18 16:23:31 node-2 kernel: [    0.469227] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 18 16:23:31 node-2 kernel: [    0.469228] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 18 16:23:31 node-2 kernel: [    0.469230] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 18 16:23:31 node-2 kernel: [    0.469231] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 18 16:23:31 node-2 kernel: [    0.469232] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 18 16:23:31 node-2 kernel: [    0.469238] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 18 16:23:31 node-2 kernel: [    0.469321] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.469351] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.469393] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-2 kernel: [    0.469412] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.469442] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.469482] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-2 kernel: [    0.469499] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.469528] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.469568] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-2 kernel: [    0.469586] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.469655] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.469733] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.469810] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 18 16:23:31 node-2 kernel: [    0.469815] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 18 16:23:31 node-2 kernel: [    0.469900] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 18 16:23:31 node-2 kernel: [    0.470049] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 18 16:23:31 node-2 kernel: [    0.470067] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 18 16:23:31 node-2 kernel: [    0.470145] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.470198] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-2 kernel: [    0.470220] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.470276] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.470319] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-2 kernel: [    0.470348] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.470404] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.470447] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 18 16:23:31 node-2 kernel: [    0.470472] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 18 16:23:31 node-2 kernel: [    0.470489] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 18 16:23:31 node-2 kernel: [    0.470567] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.470617] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 18 16:23:31 node-2 kernel: [    0.470644] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 18 16:23:31 node-2 kernel: [    0.470893] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 18 16:23:31 node-2 kernel: [    0.470898] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 18 16:23:31 node-2 kernel: [    0.470905] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.470910] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.470918] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 18 16:23:31 node-2 kernel: [    0.470948] pci 0000:01:00.0: supports D1 D2
Oct 18 16:23:31 node-2 kernel: [    0.476965] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 18 16:23:31 node-2 kernel: [    0.476968] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 18 16:23:31 node-2 kernel: [    0.476970] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 18 16:23:31 node-2 kernel: [    0.477077] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.477110] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 18 16:23:31 node-2 kernel: [    0.484971] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 18 16:23:31 node-2 kernel: [    0.484977] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.484981] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-2 kernel: [    0.485065] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.485137] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.485232] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.485314] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 18 16:23:31 node-2 kernel: [    0.485322] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.485326] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-2 kernel: [    0.485415] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.485537] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.485591] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 18 16:23:31 node-2 kernel: [    0.485594] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.485596] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.485645] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.485763] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.485806] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.485927] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.485965] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.486088] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.486126] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 18 16:23:31 node-2 kernel: [    0.486245] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 18 16:23:31 node-2 kernel: [    0.486288] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 18 16:23:31 node-2 kernel: [    0.486291] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.486293] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.486351] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-2 kernel: [    0.486414] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.486466] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.486508] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 18 16:23:31 node-2 kernel: [    0.486592] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 18 16:23:31 node-2 kernel: [    0.486698] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 18 16:23:31 node-2 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-2 kernel: [    0.486701] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.486703] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.486759] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-2 kernel: [    0.486836] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.486885] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.487095] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 18 16:23:31 node-2 kernel: [    0.487099] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 18 16:23:31 node-2 kernel: [    0.487163] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-2 kernel: [    0.487216] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.487264] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.487472] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 18 16:23:31 node-2 kernel: [    0.487476] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 18 16:23:31 node-2 kernel: [    0.487536] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 18 16:23:31 node-2 kernel: [    0.487598] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.487650] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 18 16:23:31 node-2 kernel: [    0.487892] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 18 16:23:31 node-2 kernel: [    0.487896] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 18 16:23:31 node-2 kernel: [    0.488070] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 18 16:23:31 node-2 kernel: [    0.488108] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 18 16:23:31 node-2 kernel: [    0.488186] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 18 16:23:31 node-2 kernel: [    0.488206] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 18 16:23:31 node-2 kernel: [    0.488219] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 18 16:23:31 node-2 kernel: [    0.488232] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 18 16:23:31 node-2 kernel: [    0.488283] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 18 16:23:31 node-2 kernel: [    0.492976] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 18 16:23:31 node-2 kernel: [    0.492986] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 18 16:23:31 node-2 kernel: [    0.493038] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 18 16:23:31 node-2 kernel: [    0.493782] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 18 16:23:31 node-2 kernel: [    0.493785] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 18 16:23:31 node-2 kernel: [    0.493905] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 18 16:23:31 node-2 kernel: [    0.494013] PCI host bridge to bus 0000:80
Oct 18 16:23:31 node-2 kernel: [    0.494015] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 18 16:23:31 node-2 kernel: [    0.494017] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 18 16:23:31 node-2 kernel: [    0.494018] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 18 16:23:31 node-2 kernel: [    0.494026] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.494089] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.494157] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 18 16:23:31 node-2 kernel: [    0.494220] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 18 16:23:31 node-2 kernel: [    0.494226] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 18 16:23:31 node-2 kernel: [    0.494296] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 18 16:23:31 node-2 kernel: [    0.494591] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 18 16:23:31 node-2 kernel: [    0.494622] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 18 16:23:31 node-2 kernel: [    0.494652] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 18 16:23:31 node-2 kernel: [    0.494681] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 18 16:23:31 node-2 kernel: [    0.494711] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-2 kernel: [    0.494741] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-2 kernel: [    0.494770] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-2 kernel: [    0.494800] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 18 16:23:31 node-2 kernel: [    0.494885] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 18 16:23:31 node-2 kernel: [    0.494890] ACPI: \_SB_.UNC1: notify handler is installed
Oct 18 16:23:31 node-2 kernel: [    0.494891] ACPI: \_SB_.UNC0: notify handler is installed
Oct 18 16:23:31 node-2 kernel: [    0.494906] ACPI: \_SB_.PCI0: notify handler is installed
Oct 18 16:23:31 node-2 kernel: [    0.494958] ACPI: \_SB_.PCI1: notify handler is installed
Oct 18 16:23:31 node-2 kernel: [    0.495037] Found 4 acpi root devices
Oct 18 16:23:31 node-2 kernel: [    0.495146] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 18 16:23:31 node-2 kernel: [    0.495148] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 18 16:23:31 node-2 kernel: [    0.495150] vgaarb: loaded
Oct 18 16:23:31 node-2 kernel: [    0.495151] vgaarb: bridge control possible 0000:0c:00.0
Oct 18 16:23:31 node-2 kernel: [    0.495276] SCSI subsystem initialized
Oct 18 16:23:31 node-2 kernel: [    0.495342] libata version 3.00 loaded.
Oct 18 16:23:31 node-2 kernel: [    0.495358] ACPI: bus type USB registered
Oct 18 16:23:31 node-2 kernel: [    0.495368] usbcore: registered new interface driver usbfs
Oct 18 16:23:31 node-2 kernel: [    0.495373] usbcore: registered new interface driver hub
Oct 18 16:23:31 node-2 kernel: [    0.495396] usbcore: registered new device driver usb
Oct 18 16:23:31 node-2 kernel: [    0.495562] PCI: Using ACPI for IRQ routing
Oct 18 16:23:31 node-2 kernel: [    0.499161] PCI: pci_cache_line_size set to 64 bytes
Oct 18 16:23:31 node-2 kernel: [    0.499364] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 18 16:23:31 node-2 kernel: [    0.499366] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 18 16:23:31 node-2 kernel: [    0.499366] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 18 16:23:31 node-2 kernel: [    0.499430] NetLabel: Initializing
Oct 18 16:23:31 node-2 kernel: [    0.499432] NetLabel:  domain hash size = 128
Oct 18 16:23:31 node-2 kernel: [    0.499433] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 18 16:23:31 node-2 kernel: [    0.499443] NetLabel:  unlabeled traffic allowed by default
Oct 18 16:23:31 node-2 kernel: [    0.499500] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 18 16:23:31 node-2 kernel: [    0.499504] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 18 16:23:31 node-2 kernel: [    0.501560] Switched to clocksource hpet
Oct 18 16:23:31 node-2 kernel: [    0.505424] AppArmor: AppArmor Filesystem Enabled
Oct 18 16:23:31 node-2 kernel: [    0.505439] pnp: PnP ACPI init
Oct 18 16:23:31 node-2 kernel: [    0.505446] ACPI: bus type PNP registered
Oct 18 16:23:31 node-2 kernel: [    0.505570] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505578] pnp 00:01: [dma 4]
Oct 18 16:23:31 node-2 kernel: [    0.505590] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505616] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505636] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505654] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505687] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505741] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505743] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 18 16:23:31 node-2 kernel: [    0.505744] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505746] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505748] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505753] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505755] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 18 16:23:31 node-2 kernel: [    0.505757] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505758] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505760] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505761] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505763] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505764] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 18 16:23:31 node-2 kernel: [    0.505766] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505849] pnp 00:07: [dma 0 disabled]
Oct 18 16:23:31 node-2 kernel: [    0.505877] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 18 16:23:31 node-2 kernel: [    0.505951] pnp 00:08: [dma 0 disabled]
Oct 18 16:23:31 node-2 kernel: [    0.505982] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 18 16:23:31 node-2 kernel: [    0.506032] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 18 16:23:31 node-2 kernel: [    0.506381] pnp: PnP ACPI: found 10 devices
Oct 18 16:23:31 node-2 kernel: [    0.506382] ACPI: bus type PNP unregistered
Oct 18 16:23:31 node-2 kernel: [    0.512622] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 18 16:23:31 node-2 kernel: [    0.512625] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 18 16:23:31 node-2 kernel: [    0.512627] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 18 16:23:31 node-2 kernel: [    0.512631] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 18 16:23:31 node-2 kernel: [    0.512633] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512648] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512677] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 18 16:23:31 node-2 kernel: [    0.512692] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512720] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 18 16:23:31 node-2 kernel: [    0.512738] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 18 16:23:31 node-2 kernel: [    0.512781] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 18 16:23:31 node-2 kernel: [    0.512796] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 18 16:23:31 node-2 kernel: [    0.512824] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 18 16:23:31 node-2 kernel: [    0.512826] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512840] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512869] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 18 16:23:31 node-2 kernel: [    0.512871] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512886] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512915] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 18 16:23:31 node-2 kernel: [    0.512916] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512919] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512923] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 18 16:23:31 node-2 kernel: [    0.512925] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512927] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512931] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 18 16:23:31 node-2 kernel: [    0.512936] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 18 16:23:31 node-2 kernel: [    0.512944] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 18 16:23:31 node-2 kernel: [    0.512947] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 18 16:23:31 node-2 kernel: [    0.512954] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 18 16:23:31 node-2 kernel: [    0.512954] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 18 16:23:31 node-2 kernel: [    0.512955] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 18 16:23:31 node-2 kernel: [    0.512956] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 18 16:23:31 node-2 kernel: [    0.512957] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 18 16:23:31 node-2 kernel: [    0.512958] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 18 16:23:31 node-2 kernel: [    0.512959] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 18 16:23:31 node-2 kernel: [    0.512960] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 18 16:23:31 node-2 kernel: [    0.512961] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512962] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512962] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512963] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512964] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512965] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512966] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512967] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512968] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 18 16:23:31 node-2 kernel: [    0.512969] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512970] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 18 16:23:31 node-2 kernel: [    0.512971] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 18 16:23:31 node-2 kernel: [    0.512972] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 18 16:23:31 node-2 kernel: [    0.512973] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 18 16:23:31 node-2 kernel: [    0.512975] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 18 16:23:31 node-2 kernel: [    0.512976] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 18 16:23:31 node-2 kernel: [    0.513012] NET: Registered protocol family 2
Oct 18 16:23:31 node-2 kernel: [    0.513285] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.513624] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.513768] TCP: Hash tables configured (established 262144 bind 65536)
Oct 18 16:23:31 node-2 kernel: [    0.513805] TCP: reno registered
Oct 18 16:23:31 node-2 kernel: [    0.513833] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.513927] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.514074] NET: Registered protocol family 1
Oct 18 16:23:31 node-2 kernel: [    0.549659] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 18 16:23:31 node-2 kernel: [    0.549673] PCI: CLS 64 bytes, default 64
Oct 18 16:23:31 node-2 kernel: [    0.549748] Trying to unpack rootfs image as initramfs...
Oct 18 16:23:31 node-2 kernel: [    0.769165] Freeing initrd memory: 20368K (ffff880035828000 - ffff880036c0c000)
Oct 18 16:23:31 node-2 kernel: [    0.769206] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 18 16:23:31 node-2 kernel: [    0.769208] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 18 16:23:31 node-2 kernel: [    0.769630] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769636] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769641] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769647] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769659] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769676] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769691] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769706] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769717] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769727] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769733] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769739] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769748] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769760] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769773] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769785] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 18 16:23:31 node-2 kernel: [    0.769891] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 18 16:23:31 node-2 kernel: [    0.769898] Scanning for low memory corruption every 60 seconds
Oct 18 16:23:31 node-2 kernel: [    0.770351] Initialise system trusted keyring
Oct 18 16:23:31 node-2 kernel: [    0.770404] audit: initializing netlink socket (disabled)
Oct 18 16:23:31 node-2 kernel: [    0.770420] type=2000 audit(1476807774.720:1): initialized
Oct 18 16:23:31 node-2 kernel: [    0.788157] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 18 16:23:31 node-2 kernel: [    0.789729] zbud: loaded
Oct 18 16:23:31 node-2 kernel: [    0.789855] VFS: Disk quotas dquot_6.5.2
Oct 18 16:23:31 node-2 kernel: [    0.789899] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 18 16:23:31 node-2 kernel: [    0.790277] fuse init (API version 7.22)
Oct 18 16:23:31 node-2 kernel: [    0.790340] msgmni has been set to 32768
Oct 18 16:23:31 node-2 kernel: [    0.790393] Key type big_key registered
Oct 18 16:23:31 node-2 kernel: [    0.790877] Key type asymmetric registered
Oct 18 16:23:31 node-2 kernel: [    0.790879] Asymmetric key parser 'x509' registered
Oct 18 16:23:31 node-2 kernel: [    0.790901] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 18 16:23:31 node-2 kernel: [    0.790977] io scheduler noop registered
Oct 18 16:23:31 node-2 kernel: [    0.790978] io scheduler deadline registered (default)
Oct 18 16:23:31 node-2 kernel: [    0.790998] io scheduler cfq registered
Oct 18 16:23:31 node-2 kernel: [    0.791405] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    0.791549] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    0.791662] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    0.791785] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    0.791901] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    0.791998] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    0.792385] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 18 16:23:31 node-2 kernel: [    0.792411] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 18 16:23:31 node-2 kernel: [    0.792427] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 18 16:23:31 node-2 kernel: [    0.792436] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792438] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792441] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-2 kernel: [    0.792446] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792447] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792449] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792450] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792451] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792453] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792454] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792456] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792457] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792458] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792460] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792461] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792464] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-2 kernel: [    0.792469] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792471] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-2 kernel: [    0.792485] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792489] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-2 kernel: [    0.792499] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792501] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 18 16:23:31 node-2 kernel: [    0.792504] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 18 16:23:31 node-2 kernel: [    0.792553] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 18 16:23:31 node-2 kernel: [    0.792559] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 18 16:23:31 node-2 kernel: [    0.792563] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 18 16:23:31 node-2 kernel: [    0.792572] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 18 16:23:31 node-2 kernel: [    0.792613] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 18 16:23:31 node-2 kernel: [    0.792614] vesafb: scrolling: redraw
Oct 18 16:23:31 node-2 kernel: [    0.792616] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 18 16:23:31 node-2 kernel: [    0.813203] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 18 16:23:31 node-2 kernel: [    0.821711] Console: switching to colour frame buffer device 80x30
Oct 18 16:23:31 node-2 kernel: [    0.830390] fb0: VESA VGA frame buffer device
Oct 18 16:23:31 node-2 kernel: [    0.830587] intel_idle: MWAIT substates: 0x2120
Oct 18 16:23:31 node-2 kernel: [    0.830588] intel_idle: v0.4 model 0x3F
Oct 18 16:23:31 node-2 kernel: [    0.830589] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 18 16:23:31 node-2 kernel: [    0.830823] ipmi message handler version 39.2
Oct 18 16:23:31 node-2 kernel: [    0.831098] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 18 16:23:31 node-2 kernel: [    0.831530] ACPI: AC Adapter [P111] (on-line)
Oct 18 16:23:31 node-2 kernel: [    0.836757] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 18 16:23:31 node-2 kernel: [    0.847784] ACPI: Power Button [PWRB]
Oct 18 16:23:31 node-2 kernel: [    0.853546] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 18 16:23:31 node-2 kernel: [    0.865195] ACPI: Power Button [PWRF]
Oct 18 16:23:31 node-2 kernel: [    0.891112] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 18 16:23:31 node-2 kernel: [    0.902785] pstore: Registered erst as persistent store backend
Oct 18 16:23:31 node-2 kernel: [    0.908983] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 18 16:23:31 node-2 kernel: [    0.920942] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 18 16:23:31 node-2 kernel: [    0.947685] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 18 16:23:31 node-2 kernel: [    0.980979] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 18 16:23:31 node-2 kernel: [    0.994991] Linux agpgart interface v0.103
Oct 18 16:23:31 node-2 kernel: [    1.002619] brd: module loaded
Oct 18 16:23:31 node-2 kernel: [    1.009679] loop: module loaded
Oct 18 16:23:31 node-2 kernel: [    1.016388] libphy: Fixed MDIO Bus: probed
Oct 18 16:23:31 node-2 kernel: [    1.022850] tun: Universal TUN/TAP device driver, 1.6
Oct 18 16:23:31 node-2 kernel: [    1.029328] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 18 16:23:31 node-2 kernel: [    1.035844] PPP generic driver version 2.4.2
Oct 18 16:23:31 node-2 kernel: [    1.042223] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 18 16:23:31 node-2 kernel: [    1.048659] ehci-pci: EHCI PCI platform driver
Oct 18 16:23:31 node-2 kernel: [    1.055175] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 18 16:23:31 node-2 kernel: [    1.061583] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 18 16:23:31 node-2 kernel: [    1.074100] ehci-pci 0000:00:1a.0: debug port 2
Oct 18 16:23:31 node-2 kernel: [    1.084305] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 18 16:23:31 node-2 kernel: [    1.084324] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 18 16:23:31 node-2 kernel: [    1.101056] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 18 16:23:31 node-2 kernel: [    1.107133] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 18 16:23:31 node-2 kernel: [    1.113312] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 18 16:23:31 node-2 kernel: [    1.125201] usb usb1: Product: EHCI Host Controller
Oct 18 16:23:31 node-2 kernel: [    1.131223] usb usb1: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 18 16:23:31 node-2 kernel: [    1.137267] usb usb1: SerialNumber: 0000:00:1a.0
Oct 18 16:23:31 node-2 kernel: [    1.143217] hub 1-0:1.0: USB hub found
Oct 18 16:23:31 node-2 kernel: [    1.149055] hub 1-0:1.0: 2 ports detected
Oct 18 16:23:31 node-2 kernel: [    1.154930] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 18 16:23:31 node-2 kernel: [    1.160507] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 18 16:23:31 node-2 kernel: [    1.171401] ehci-pci 0000:00:1d.0: debug port 2
Oct 18 16:23:31 node-2 kernel: [    1.180715] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 18 16:23:31 node-2 kernel: [    1.180718] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 18 16:23:31 node-2 kernel: [    1.196974] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 18 16:23:31 node-2 kernel: [    1.202179] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 18 16:23:31 node-2 kernel: [    1.207480] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 18 16:23:31 node-2 kernel: [    1.218066] usb usb2: Product: EHCI Host Controller
Oct 18 16:23:31 node-2 kernel: [    1.223537] usb usb2: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 18 16:23:31 node-2 kernel: [    1.229092] usb usb2: SerialNumber: 0000:00:1d.0
Oct 18 16:23:31 node-2 kernel: [    1.234615] hub 2-0:1.0: USB hub found
Oct 18 16:23:31 node-2 kernel: [    1.239972] hub 2-0:1.0: 2 ports detected
Oct 18 16:23:31 node-2 kernel: [    1.245280] ehci-platform: EHCI generic platform driver
Oct 18 16:23:31 node-2 kernel: [    1.250511] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 18 16:23:31 node-2 kernel: [    1.255831] ohci-pci: OHCI PCI platform driver
Oct 18 16:23:31 node-2 kernel: [    1.261128] ohci-platform: OHCI generic platform driver
Oct 18 16:23:31 node-2 kernel: [    1.266346] uhci_hcd: USB Universal Host Controller Interface driver
Oct 18 16:23:31 node-2 kernel: [    1.271705] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 18 16:23:31 node-2 kernel: [    1.464754] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 18 16:23:31 node-2 kernel: [    1.764531] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 18 16:23:31 node-2 kernel: [    1.780845] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 18 16:23:31 node-2 kernel: [    1.786456] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 18 16:23:31 node-2 kernel: [    1.792237] hub 1-1:1.0: USB hub found
Oct 18 16:23:31 node-2 kernel: [    1.797831] hub 1-1:1.0: 6 ports detected
Oct 18 16:23:31 node-2 kernel: [    1.912366] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 18 16:23:31 node-2 kernel: [    2.310575] i8042: No controller found
Oct 18 16:23:31 node-2 kernel: [    2.316117] mousedev: PS/2 mouse device common for all mice
Oct 18 16:23:31 node-2 kernel: [    2.321829] rtc_cmos 00:02: RTC can wake from S4
Oct 18 16:23:31 node-2 kernel: [    2.324825] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 18 16:23:31 node-2 kernel: [    2.324826] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 18 16:23:31 node-2 kernel: [    2.325584] hub 2-1:1.0: USB hub found
Oct 18 16:23:31 node-2 kernel: [    2.325821] hub 2-1:1.0: 8 ports detected
Oct 18 16:23:31 node-2 kernel: [    2.350226] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 18 16:23:31 node-2 kernel: [    2.355994] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 18 16:23:31 node-2 kernel: [    2.367313] device-mapper: uevent: version 1.0.3
Oct 18 16:23:31 node-2 kernel: [    2.373036] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 18 16:23:31 node-2 kernel: [    2.384466] ledtrig-cpu: registered to indicate activity on CPUs
Oct 18 16:23:31 node-2 kernel: [    2.390473] TCP: cubic registered
Oct 18 16:23:31 node-2 kernel: [    2.396377] NET: Registered protocol family 10
Oct 18 16:23:31 node-2 kernel: [    2.402483] NET: Registered protocol family 17
Oct 18 16:23:31 node-2 kernel: [    2.408279] Key type dns_resolver registered
Oct 18 16:23:31 node-2 kernel: [    2.414357] Loading compiled-in X.509 certificates
Oct 18 16:23:31 node-2 kernel: [    2.420576] Loaded X.509 cert 'Magrathea: Glacier signing key: c29c39823a6b07000b1e1e4c1cabc3708bc09796'
Oct 18 16:23:31 node-2 kernel: [    2.432252] registered taskstats version 1
Oct 18 16:23:31 node-2 kernel: [    2.440389] Key type trusted registered
Oct 18 16:23:31 node-2 kernel: [    2.448058] Key type encrypted registered
Oct 18 16:23:31 node-2 kernel: [    2.453583] AppArmor: AppArmor sha1 policy hashing enabled
Oct 18 16:23:31 node-2 kernel: [    2.459129] IMA: No TPM chip found, activating TPM-bypass!
Oct 18 16:23:31 node-2 kernel: [    2.465212] regulator-dummy: disabling
Oct 18 16:23:31 node-2 kernel: [    2.470746]   Magic number: 4:896:388
Oct 18 16:23:31 node-2 kernel: [    2.476251] thermal cooling_device3: hash matches
Oct 18 16:23:31 node-2 kernel: [    2.482020] rtc_cmos 00:02: setting system clock to 2016-10-18 16:22:57 UTC (1476807777)
Oct 18 16:23:31 node-2 kernel: [    2.494596] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 18 16:23:31 node-2 kernel: [    2.500315] EDD information not available.
Oct 18 16:23:31 node-2 kernel: [    2.506002] PM: Hibernation image not present or could not be loaded.
Oct 18 16:23:31 node-2 kernel: [    2.506863] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 18 16:23:31 node-2 kernel: [    2.518344] Write protecting the kernel read-only data: 12288k
Oct 18 16:23:31 node-2 kernel: [    2.524837] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 18 16:23:31 node-2 kernel: [    2.537827] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 18 16:23:31 node-2 kernel: [    2.569981] device-mapper: multipath: version 1.6.0 loaded
Oct 18 16:23:31 node-2 kernel: [    2.577779] systemd-udevd[215]: starting version 204
Oct 18 16:23:31 node-2 kernel: [    2.601557] md: linear personality registered for level -1
Oct 18 16:23:31 node-2 kernel: [    2.607920] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 18 16:23:31 node-2 kernel: [    2.622806] md: multipath personality registered for level -4
Oct 18 16:23:31 node-2 kernel: [    2.631002] md: raid0 personality registered for level 0
Oct 18 16:23:31 node-2 kernel: [    2.639345] md: raid1 personality registered for level 1
Oct 18 16:23:31 node-2 kernel: [    2.645764] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 18 16:23:31 node-2 kernel: [    2.652040] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 18 16:23:31 node-2 kernel: [    2.658320] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 18 16:23:31 node-2 kernel: [    2.659189] megasas: FW now in Ready state
Oct 18 16:23:31 node-2 kernel: [    2.659256] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659300] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659345] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659373] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659412] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659452] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659500] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659541] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659589] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659624] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659662] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659693] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659868] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659903] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659943] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.659983] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.660167] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 18 16:23:31 node-2 kernel: [    2.691724] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-2 kernel: [    2.704978] 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-2 kernel: [    2.718857] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 18 16:23:31 node-2 kernel: [    2.723751] raid6: sse2x1    6810 MB/s
Oct 18 16:23:31 node-2 kernel: [    2.732700] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.732704] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.732708] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.732712] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    2.732750] 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-2 kernel: [    2.756826] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-2 kernel: [    2.770579] 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-2 kernel: [    2.784562] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 18 16:23:31 node-2 kernel: [    2.791631] raid6: sse2x2   12237 MB/s
Oct 18 16:23:31 node-2 kernel: [    2.863576] raid6: sse2x4   10129 MB/s
Oct 18 16:23:31 node-2 kernel: [    2.935509] raid6: avx2x1   14932 MB/s
Oct 18 16:23:31 node-2 kernel: [    3.007446] raid6: avx2x2   18870 MB/s
Oct 18 16:23:31 node-2 kernel: [    3.079396] raid6: avx2x4   21371 MB/s
Oct 18 16:23:31 node-2 kernel: [    3.085708] raid6: using algorithm avx2x4 (21371 MB/s)
Oct 18 16:23:31 node-2 kernel: [    3.091958] raid6: using avx2x2 recovery algorithm
Oct 18 16:23:31 node-2 kernel: [    3.098040] megasas:IOC Init cmd success
Oct 18 16:23:31 node-2 kernel: [    3.098042] Switched to clocksource tsc
Oct 18 16:23:31 node-2 kernel: [    3.098081] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.098124] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.098166] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.098204] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.098235] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.098275] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.098381] 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-2 kernel: [    3.110486] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-2 kernel: [    3.110487] 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-2 kernel: [    3.110488] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 18 16:23:31 node-2 kernel: [    3.110552] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.110658] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.110696] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.110795] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.110916] 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-2 kernel: [    3.112880] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 18 16:23:31 node-2 kernel: [    3.112892] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 18 16:23:31 node-2 kernel: [    3.112892] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 18 16:23:31 node-2 kernel: [    3.112893] usb 2-1.4: Manufacturer: Avocent
Oct 18 16:23:31 node-2 kernel: [    3.112894] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 18 16:23:31 node-2 kernel: [    3.119445] megasas: INIT adapter done
Oct 18 16:23:31 node-2 kernel: [    3.120828] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct 18 16:23:31 node-2 kernel: [    3.120829] 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-2 kernel: [    3.120830] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 18 16:23:31 node-2 kernel: [    3.120888] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.120921] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.120950] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.120986] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 18 16:23:31 node-2 kernel: [    3.121070] 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-2 kernel: [    3.191301] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 18 16:23:31 node-2 kernel: [    3.191644] scsi0 : LSI SAS based MegaRAID driver
Oct 18 16:23:31 node-2 kernel: [    3.196438] xor: automatically using best checksumming function:
Oct 18 16:23:31 node-2 kernel: [    3.198893] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 18 16:23:31 node-2 kernel: [    3.208046] hidraw: raw HID events driver (C) Jiri Kosina
Oct 18 16:23:31 node-2 kernel: [    3.210024] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 18 16:23:31 node-2 kernel: [    3.213766] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 18 16:23:31 node-2 kernel: [    3.213923] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 18 16:23:31 node-2 kernel: [    3.214077] sd 0:2:0:0: [sda] Write Protect is off
Oct 18 16:23:31 node-2 kernel: [    3.214078] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 18 16:23:31 node-2 kernel: [    3.214163] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 18 16:23:31 node-2 kernel: [    3.243043]    avx       : 69551.000 MB/sec
Oct 18 16:23:31 node-2 kernel: [    3.243249]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 18 16:23:31 node-2 kernel: [    3.244814] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 18 16:23:31 node-2 kernel: [    3.288662] usbcore: registered new interface driver usbhid
Oct 18 16:23:31 node-2 kernel: [    3.288662] usbhid: USB HID core driver
Oct 18 16:23:31 node-2 kernel: [    3.362495] async_tx: api initialized (async)
Oct 18 16:23:31 node-2 kernel: [    3.368802] 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-2 kernel: [    3.369685] 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-2 kernel: [    3.369763] 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-2 kernel: [    3.370272] 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-2 kernel: [    3.370327] 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-2 kernel: [    3.370655] 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-2 kernel: [    3.444562] random: lvm urandom read with 30 bits of entropy available
Oct 18 16:23:31 node-2 kernel: [    3.464948] md: raid6 personality registered for level 6
Oct 18 16:23:31 node-2 kernel: [    3.472035] md: raid5 personality registered for level 5
Oct 18 16:23:31 node-2 kernel: [    3.478962] md: raid4 personality registered for level 4
Oct 18 16:23:31 node-2 kernel: [    3.488658] md: raid10 personality registered for level 10
Oct 18 16:23:31 node-2 kernel: [    3.544183] multipathd (372): /proc/372/oom_adj is deprecated, please use /proc/372/oom_score_adj instead.
Oct 18 16:23:31 node-2 kernel: [    3.635801] bio: create slab <bio-1> at 1
Oct 18 16:23:31 node-2 kernel: [    4.567832] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Oct 18 16:23:31 node-2 kernel: [    5.054121] random: nonblocking pool is initialized
Oct 18 16:23:31 node-2 kernel: [    5.211981] init: plymouth-upstart-bridge main process (574) terminated with status 1
Oct 18 16:23:31 node-2 kernel: [    5.224579] init: plymouth-upstart-bridge main process ended, respawning
Oct 18 16:23:31 node-2 kernel: [    5.349248] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Oct 18 16:23:31 node-2 kernel: [    5.399781] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 18 16:23:31 node-2 kernel: [    5.507059] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 18 16:23:31 node-2 kernel: [    5.548968] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 18 16:23:31 node-2 kernel: [    5.636642] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 18 16:23:31 node-2 kernel: [    5.835172] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 18 16:23:31 node-2 kernel: [    5.873268] XFS (dm-1): Mounting Filesystem
Oct 18 16:23:31 node-2 kernel: [    6.182791] XFS (dm-1): Ending clean mount
Oct 18 16:23:31 node-2 kernel: [    6.241320] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 18 16:23:31 node-2 kernel: [    6.266560] XFS (dm-2): Mounting Filesystem
Oct 18 16:23:31 node-2 kernel: [    6.370986] XFS (dm-2): Ending clean mount
Oct 18 16:23:31 node-2 kernel: [    6.509090] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Oct 18 16:23:31 node-2 kernel: [    8.184665] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 18 16:23:31 node-2 kernel: [    8.210956] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 18 16:23:31 node-2 kernel: [    8.372313] systemd-udevd[804]: starting version 204
Oct 18 16:23:31 node-2 kernel: [    8.560444] IPMI System Interface driver.
Oct 18 16:23:31 node-2 kernel: [    8.560502] ipmi_si: probing via ACPI
Oct 18 16:23:31 node-2 kernel: [    8.560519] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 18 16:23:31 node-2 kernel: [    8.560520] ipmi_si: Adding ACPI-specified kcs state machine
Oct 18 16:23:31 node-2 kernel: [    8.560534] ipmi_si: probing via SMBIOS
Oct 18 16:23:31 node-2 kernel: [    8.560535] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 18 16:23:31 node-2 kernel: [    8.560536] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 18 16:23:31 node-2 kernel: [    8.560539] ipmi_si: probing via SPMI
Oct 18 16:23:31 node-2 kernel: [    8.560540] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 18 16:23:31 node-2 kernel: [    8.560541] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 18 16:23:31 node-2 kernel: [    8.560542] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 18 16:23:31 node-2 kernel: [    8.564246] power_meter ACPI000D:00: Found ACPI power meter.
Oct 18 16:23:31 node-2 kernel: [    8.564254] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 18 16:23:31 node-2 kernel: [    8.573476] wmi: Mapper loaded
Oct 18 16:23:31 node-2 kernel: [    8.606363] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 18 16:23:31 node-2 kernel: [    8.606368] 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-2 kernel: [    8.606371] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 18 16:23:31 node-2 kernel: [    8.606372] 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-2 kernel: [    8.606387] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 18 16:23:31 node-2 kernel: [    8.622762] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 18 16:23:31 node-2 kernel: [    8.699114] systemd-udevd[833]: renamed network interface eth1 to enp7s0
Oct 18 16:23:31 node-2 kernel: [    8.703475] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 18 16:23:31 node-2 kernel: [    8.703486] ipmi_si 00:09: IPMI kcs interface initialized
Oct 18 16:23:31 node-2 kernel: [    8.727004] systemd-udevd[824]: renamed network interface eth0 to enp6s0
Oct 18 16:23:31 node-2 kernel: [    8.762923] systemd-udevd[853]: renamed network interface eth2 to enp8s0
Oct 18 16:23:31 node-2 kernel: [    8.790913] systemd-udevd[822]: renamed network interface eth3 to enp9s0
Oct 18 16:23:31 node-2 kernel: [    9.060426] type=1400 audit(1476807784.081:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1085 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.060576] type=1400 audit(1476807784.081:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1085 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.060699] type=1400 audit(1476807784.081:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1085 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.062702] type=1400 audit(1476807784.085:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1084 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.062822] type=1400 audit(1476807784.085:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1084 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.062936] type=1400 audit(1476807784.085:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1084 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.066379] type=1400 audit(1476807784.089:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1086 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.066525] type=1400 audit(1476807784.089:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1086 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.066659] type=1400 audit(1476807784.089:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1086 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.074905] type=1400 audit(1476807784.097:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1087 comm="apparmor_parser"
Oct 18 16:23:31 node-2 kernel: [    9.578164] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 18 16:23:31 node-2 kernel: [    9.578915] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 18 16:23:31 node-2 kernel: [    9.746545] enic 0000:06:00.0 enp6s0: Link UP
Oct 18 16:23:31 node-2 kernel: [    9.747661] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 18 16:23:31 node-2 kernel: [    9.747770] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 18 16:23:31 node-2 kernel: [   19.435848] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 18 16:23:32 node-2 failsafe: Failsafe of 120 seconds reached.
Oct 18 16:23:33 node-2 kernel: [   37.949848] init: failsafe main process (8454) killed by TERM signal
Oct 18 16:23:33 node-2 dbus[8487]: [system] AppArmor D-Bus mediation is enabled
Oct 18 16:23:33 node-2 kernel: [   38.227405] audit_printk_skb: 30 callbacks suppressed
Oct 18 16:23:33 node-2 kernel: [   38.227408] type=1400 audit(1476807813.297:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8580 comm="apparmor_parser"
Oct 18 16:23:33 node-2 kernel: [   38.227692] type=1400 audit(1476807813.297:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8579 comm="apparmor_parser"
Oct 18 16:23:33 node-2 kernel: [   38.227697] type=1400 audit(1476807813.297:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8579 comm="apparmor_parser"
Oct 18 16:23:33 node-2 kernel: [   38.227700] type=1400 audit(1476807813.297:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Oct 18 16:23:33 node-2 kernel: [   38.227933] type=1400 audit(1476807813.297:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8579 comm="apparmor_parser"
Oct 18 16:23:33 node-2 kernel: [   38.227935] type=1400 audit(1476807813.297:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Oct 18 16:23:33 node-2 kernel: [   38.228048] type=1400 audit(1476807813.297:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Oct 18 16:23:33 node-2 kernel: [   38.303801] type=1400 audit(1476807813.373:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8582 comm="apparmor_parser"
Oct 18 16:23:33 node-2 anacron[8647]: Anacron 2.3 started on 2016-10-18
Oct 18 16:23:33 node-2 cron[8612]: (CRON) INFO (pidfile fd = 3)
Oct 18 16:23:33 node-2 anacron[8647]: Will run job `cron.daily' in 5 min.
Oct 18 16:23:33 node-2 anacron[8647]: Will run job `cron.weekly' in 10 min.
Oct 18 16:23:33 node-2 anacron[8647]: Will run job `cron.monthly' in 15 min.
Oct 18 16:23:33 node-2 anacron[8647]: Jobs will be executed sequentially
Oct 18 16:23:33 node-2 cron[8655]: (CRON) STARTUP (fork ok)
Oct 18 16:23:33 node-2 multipathd: path checkers start up
Oct 18 16:23:33 node-2 cron[8655]: (CRON) INFO (Running @reboot jobs)
Oct 18 16:23:33 node-2 postfix/master[8791]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 18 16:23:37 node-2 puppet-agent[8975]: Reopening log files
Oct 18 16:23:38 node-2 puppet-agent[8975]: Could not request certificate: Connection refused - connect(2)
Oct 18 16:23:51 node-2 puppet-user[9054]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 18 16:23:51 node-2 puppet-user[9054]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct 18 16:23:51 node-2 puppet-user[9054]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 18 16:23:51 node-2 puppet-user[9054]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 18 16:23:52 node-2 puppet-user[9054]: Finished catalog run in 0.47 seconds
Oct 18 16:23:53 node-2 multipathd: uevent trigger error
Oct 18 16:23:53 node-2 puppet-user[9474]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 18 16:23:53 node-2 puppet-user[9474]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Oct 18 16:23:53 node-2 puppet-user[9474]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 18 16:23:53 node-2 puppet-user[9474]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 18 16:23:53 node-2 puppet-user[9474]: (/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-2 puppet-user[9474]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 18 16:23:53 node-2 puppet-user[9474]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 18 16:23:53 node-2 puppet-user[9474]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 18 16:23:53 node-2 puppet-user[9474]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 18 16:23:53 node-2 puppet-user[9474]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 18 16:23:53 node-2 puppet-user[9474]: Finished catalog run in 0.06 seconds
Oct 18 16:23:54 node-2 puppet-user[9937]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 18 16:23:54 node-2 puppet-user[9937]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Oct 18 16:23:55 node-2 puppet-user[9937]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 18 16:23:55 node-2 puppet-user[9937]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 18 16:23:55 node-2 puppet-user[9937]: Finished catalog run in 0.03 seconds
Oct 18 16:23:56 node-2 puppet-user[10397]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 18 16:23:56 node-2 puppet-user[10397]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct 18 16:23:56 node-2 puppet-user[10397]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 18 16:23:56 node-2 puppet-user[10397]: Finished catalog run in 0.04 seconds
Oct 18 16:23:58 node-2 puppet-user[10855]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 18 16:23:58 node-2 puppet-user[10855]: Compiled catalog for node-2.domain.tld in environment production in 0.22 seconds
Oct 18 16:23:58 node-2 puppet-user[10855]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 18 16:23:59 node-2 puppet-user[10855]: (/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-2 puppet-user[10855]: (/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:23:59 node-2 puppet-user[10855]: (/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:23:59 node-2 puppet-user[10855]: Finished catalog run in 1.23 seconds
Oct 18 16:24:01 node-2 puppet-user[11392]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 18 16:24:01 node-2 puppet-user[11392]: Compiled catalog for node-2.domain.tld in environment production in 0.26 seconds
Oct 18 16:24:01 node-2 CRON[11810]: (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-2 puppet-user[11392]: (/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-2 puppet-user[11392]: (/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-2 puppet-user[11392]: (/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-2 puppet-user[11392]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 18 16:24:01 node-2 puppet-user[11392]: (/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-2 puppet-user[11392]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 18 16:24:02 node-2 puppet-user[11392]: Finished catalog run in 0.40 seconds
Oct 18 16:24:03 node-2 puppet-user[11883]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 18 16:24:03 node-2 puppet-user[11883]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Oct 18 16:24:03 node-2 puppet-user[11883]: (/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:03 node-2 kernel: [   68.625101] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 18 16:24:03 node-2 kernel: [   68.625151] 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:03 node-2 puppet-user[11883]: (/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:03 node-2 puppet-user[11883]: Finished catalog run in 0.06 seconds
Oct 18 16:24:05 node-2 puppet-user[12471]: (Scope(Class[main])) MODULAR: sync_time
Oct 18 16:24:05 node-2 puppet-user[12471]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 18 16:24:05 node-2 ntpdate[12889]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 18 16:24:10 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 18 16:24:10 node-2 nailgun-agent: D, [2016-10-18T16:24:01.706421 #11814] DEBUG -- : Sleep for 9 seconds before sending request
Oct 18 16:24:10 node-2 nailgun-agent: I, [2016-10-18T16:24:10.720661 #11814]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 18 16:24:11 node-2 nailgun-agent: D, [2016-10-18T16:24:11.091190 #11814] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 18 16:24:11 node-2 ntpdate[12889]: adjust time server 10.20.0.2 offset -0.012132 sec
Oct 18 16:24:11 node-2 puppet-user[12471]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 18 16:24:11 node-2 puppet-user[12471]: Finished catalog run in 6.18 seconds
Oct 18 16:24:17 node-2 puppet-user[13305]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 18 16:24:17 node-2 puppet-user[13305]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Oct 18 16:24:17 node-2 puppet-user[13305]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 18 16:24:17 node-2 puppet-user[13305]: (/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-2 puppet-user[13305]: Finished catalog run in 0.07 seconds
Oct 18 16:24:18 node-2 puppet-user[13847]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 18 16:24:19 node-2 puppet-user[13847]: Compiled catalog for node-2.domain.tld in environment production in 0.58 seconds
Oct 18 16:24:19 node-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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-2 puppet-user[13847]: (/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:20 node-2 puppet-user[13847]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 18 16:24:20 node-2 puppet-user[13847]: Finished catalog run in 0.94 seconds
Oct 18 16:24:22 node-2 puppet-user[14364]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 18 16:24:22 node-2 puppet-user[14364]: Compiled catalog for node-2.domain.tld in environment production in 0.12 seconds
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.022152 #11814] DEBUG -- : Trying to find block devices
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.022290 #11814] DEBUG -- : Found block device: sda
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.022334 #11814] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.022361 #11814] DEBUG -- : Trying to get list of physical devices
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.022523 #11814] DEBUG -- : Getting udev properties for device: sda
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.024281 #11814] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Oct 18 16:24:23 node-2 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97272", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.024304 #11814] DEBUG -- : Trying to find out if device sda is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.024347 #11814] DEBUG -- : Device sda removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.024362 #11814] DEBUG -- : Device sda seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.024830 #11814] DEBUG -- : Getting udev properties for device: dm-0
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.026376 #11814] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-umbgRJ5oPu1AFSO6LqR3A1RyBJrqiPp6mH6VxMvFrTbcI3dJuG91Ps2QHucuItD6 /dev/disk/by-uuid/4d0e8a76-dfcf-4a79-8e2a-ac2517217f7c /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-umbgRJ5oPu1AFSO6LqR3A1RyBJrqiPp6mH6VxMvFrTbcI3dJuG91Ps2QHucuItD6", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4d0e8a76-dfcf-4a79-8e2a-ac2517217f7c", "ID_FS_UUID_ENC"=>"4d0e8a76-dfcf-4a79-8e2a-ac2517217f7c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8
Oct 18 16:24:23 node-2 nailgun-agent: 8792", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.026400 #11814] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.026439 #11814] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.026452 #11814] DEBUG -- : Device dm-0 seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.026467 #11814] DEBUG -- : Getting udev properties for device: dm-1
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.028087 #11814] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-9cuebDnfvCdUqSbccT8ozuLINCeUtvMA9fSjtxIfL8Mezbj7roUd8X7ROCeieJSK /dev/disk/by-uuid/36fa5afe-8f23-49c0-9446-235fcf40e85f /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-9cuebDnfvCdUqSbccT8ozuLINCeUtvMA9fSjtxIfL8Mezbj7roUd8X7ROCeieJSK", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"36fa5afe-8f23-49c0-9446-235fcf40e85f", "ID_FS_UUID_ENC"=>"36fa5afe-8f23-49c0-9446-235fcf40e85f", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37009", "nomdmonddf"=>"1", "nom
Oct 18 16:24:23 node-2 nailgun-agent: dmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.028120 #11814] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.028146 #11814] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.028159 #11814] DEBUG -- : Device dm-1 seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.028172 #11814] DEBUG -- : Getting udev properties for device: dm-2
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.029706 #11814] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-FyUY2ePuzJZWInbh5e1eBIEFQl8YKTAx1z9LaamFqFRjANSuEPbKWUOGP5cMNdq8 /dev/disk/by-uuid/c7a412eb-ac8a-463e-8233-2a7995e84c51 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-FyUY2ePuzJZWInbh5e1eBIEFQl8YKTAx1z9LaamFqFRjANSuEPbKWUOGP5cMNdq8", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c7a412eb-ac8a-463e-8233-2a7995e84c51", "ID_FS_UUID_ENC"=>"c7a412eb-ac8a-463e-8233-2a7995e84c51", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6
Oct 18 16:24:23 node-2 nailgun-agent: 2498", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.029727 #11814] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.029826 #11814] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.029854 #11814] DEBUG -- : Device dm-2 seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.029869 #11814] DEBUG -- : Getting udev properties for device: dm-3
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.031474 #11814] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-XQ4ptzuzgFBH6uePsQMAgl3JbMdFdsxlUY8RcI070T0AcdD1QofiPXlTQFJiuUDc /dev/disk/by-uuid/8ad8e5f1-06e9-4009-beea-b1c6afdc76c0 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-XQ4ptzuzgFBH6uePsQMAgl3JbMdFdsxlUY8RcI070T0AcdD1QofiPXlTQFJiuUDc", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8ad8e5f1-06e9-4009-beea-b1c6afdc76c0", "ID_FS_UUID_ENC"=>"8ad8e5f1-06e9-4009-beea-b1c6afdc76c0", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"66206", "nomdmon
Oct 18 16:24:23 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.031503 #11814] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.031569 #11814] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.031595 #11814] DEBUG -- : Device dm-3 seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.031610 #11814] DEBUG -- : Getting udev properties for device: dm-4
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.033187 #11814] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-8JjCXtuF8pSaD5SrOzDKldJy6jAmxA6vpN8LBW4KfuOzgS15CWmRbK42V3CP239g /dev/disk/by-uuid/d0bb1dae-bc03-4fcd-b21d-9b5a35eb6c05 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-8JjCXtuF8pSaD5SrOzDKldJy6jAmxA6vpN8LBW4KfuOzgS15CWmRbK42V3CP239g", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d0bb1dae-bc03-4fcd-b21d-9b5a35eb6c05", "ID_FS_UUID_ENC"=>"d0bb1dae-bc03-4fcd-b21d-9b5a35eb6c05", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69496", "nomdmonddf"=>"1",
Oct 18 16:24:23 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.033209 #11814] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.033248 #11814] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.033260 #11814] DEBUG -- : Device dm-4 seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.033275 #11814] DEBUG -- : Getting udev properties for device: dm-5
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.034796 #11814] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-qoqY0049ReaP3UuPJDM8XCwdIqZP8wIFQalezG57ArkibWXKRtS230N32vB8bcQr /dev/disk/by-uuid/e5d5dd70-7afa-42cb-ad81-c1b7a3c34e21 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-qoqY0049ReaP3UuPJDM8XCwdIqZP8wIFQalezG57ArkibWXKRtS230N32vB8bcQr", "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"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65361", "nomdmonddf"=>"1", "nom
Oct 18 16:24:23 node-2 nailgun-agent: dmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.034885 #11814] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.034913 #11814] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.034926 #11814] DEBUG -- : Device dm-5 seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.034940 #11814] DEBUG -- : Getting udev properties for device: dm-6
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.036548 #11814] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-qoqY0049ReaP3UuPJDM8XCwdIqZP8wIFRCFUYvxt2HELjKQVp0NcQmlB3JLdsQj9 /dev/disk/by-uuid/a9a2ef88-b789-46fe-9b69-a2c6aecc0aa8 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-qoqY0049ReaP3UuPJDM8XCwdIqZP8wIFRCFUYvxt2HELjKQVp0NcQmlB3JLdsQj9", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"a9a2ef88-b789-46fe-9b69-a2c6aecc0aa8", "ID_FS_UUID_ENC"=>"a9a2ef88-b789-46fe-9b69-a2c6aecc0aa8", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65843", "nomdmonddf"=>"1", "nomdmonisw
Oct 18 16:24:23 node-2 nailgun-agent: "=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.036582 #11814] DEBUG -- : Trying to find out if device dm-6 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.036699 #11814] DEBUG -- : Device dm-6 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.036723 #11814] DEBUG -- : Device dm-6 seems to be appropriate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.036747 #11814] DEBUG -- : Getting udev properties for device: ram0
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.038632 #11814] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42945", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.038655 #11814] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.038692 #11814] DEBUG -- : Device ram0 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.038711 #11814] DEBUG -- : Getting udev properties for device: ram1
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.040123 #11814] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42956", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.040154 #11814] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.040185 #11814] DEBUG -- : Device ram1 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.040202 #11814] DEBUG -- : Getting udev properties for device: ram2
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.041612 #11814] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43055", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.041635 #11814] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.041668 #11814] DEBUG -- : Device ram2 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.041687 #11814] DEBUG -- : Getting udev properties for device: ram3
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.043088 #11814] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43072", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.043109 #11814] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.043167 #11814] DEBUG -- : Device ram3 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.043186 #11814] DEBUG -- : Getting udev properties for device: ram4
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.044539 #11814] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43090", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.044559 #11814] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.044590 #11814] DEBUG -- : Device ram4 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.044626 #11814] DEBUG -- : Getting udev properties for device: ram5
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.045988 #11814] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43108", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.046009 #11814] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.046038 #11814] DEBUG -- : Device ram5 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.046079 #11814] DEBUG -- : Getting udev properties for device: ram6
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.047415 #11814] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43126", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.047435 #11814] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.047500 #11814] DEBUG -- : Device ram6 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.047518 #11814] DEBUG -- : Getting udev properties for device: ram7
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.048937 #11814] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43142", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.048973 #11814] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.049007 #11814] DEBUG -- : Device ram7 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.049025 #11814] DEBUG -- : Getting udev properties for device: ram8
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.050432 #11814] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43160", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.050451 #11814] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.050484 #11814] DEBUG -- : Device ram8 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.050502 #11814] DEBUG -- : Getting udev properties for device: ram9
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.051888 #11814] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43176", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.051911 #11814] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.051942 #11814] DEBUG -- : Device ram9 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.051995 #11814] DEBUG -- : Getting udev properties for device: loop0
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.053377 #11814] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42853", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.053431 #11814] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.053467 #11814] DEBUG -- : Device loop0 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.053486 #11814] DEBUG -- : Getting udev properties for device: loop1
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.055063 #11814] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42865", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.055096 #11814] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.055127 #11814] DEBUG -- : Device loop1 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.055147 #11814] DEBUG -- : Getting udev properties for device: loop2
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.056585 #11814] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42878", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.056622 #11814] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.056659 #11814] DEBUG -- : Device loop2 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.056681 #11814] DEBUG -- : Getting udev properties for device: loop3
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.058082 #11814] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42889", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.058103 #11814] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.058135 #11814] DEBUG -- : Device loop3 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.058168 #11814] DEBUG -- : Getting udev properties for device: loop4
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.059553 #11814] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42901", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.059578 #11814] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.059610 #11814] DEBUG -- : Device loop4 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.059666 #11814] DEBUG -- : Getting udev properties for device: loop5
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.061047 #11814] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42912", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.061068 #11814] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.061124 #11814] DEBUG -- : Device loop5 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.061142 #11814] DEBUG -- : Getting udev properties for device: loop6
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.062516 #11814] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42923", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.062536 #11814] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.062582 #11814] DEBUG -- : Device loop6 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.062599 #11814] DEBUG -- : Getting udev properties for device: loop7
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.063979 #11814] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42933", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.063999 #11814] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.064033 #11814] DEBUG -- : Device loop7 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.064050 #11814] DEBUG -- : Getting udev properties for device: ram10
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.065477 #11814] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42966", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.065497 #11814] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.065542 #11814] DEBUG -- : Device ram10 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.065560 #11814] DEBUG -- : Getting udev properties for device: ram11
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.066948 #11814] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42977", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.066973 #11814] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.067030 #11814] DEBUG -- : Device ram11 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.067048 #11814] DEBUG -- : Getting udev properties for device: ram12
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.068549 #11814] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42990", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.068575 #11814] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.068622 #11814] DEBUG -- : Device ram12 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.068642 #11814] DEBUG -- : Getting udev properties for device: ram13
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.070073 #11814] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43006", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.070098 #11814] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.070141 #11814] DEBUG -- : Device ram13 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.070200 #11814] DEBUG -- : Getting udev properties for device: ram14
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.071553 #11814] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43022", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.071611 #11814] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.071656 #11814] DEBUG -- : Device ram14 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.071676 #11814] DEBUG -- : Getting udev properties for device: ram15
Oct 18 16:24:23 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073130 #11814] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43037", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073151 #11814] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073193 #11814] DEBUG -- : Device ram15 removable parameter: "0"
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073229 #11814] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073243 #11814] DEBUG -- : Block device seems to be physical data storage: sda
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073337 #11814] DEBUG -- : Found block device: dm-0
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073352 #11814] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073365 #11814] DEBUG -- : Found block device: dm-1
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073376 #11814] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073384 #11814] DEBUG -- : Found block device: dm-2
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073395 #11814] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073404 #11814] DEBUG -- : Found block device: dm-3
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073452 #11814] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073461 #11814] DEBUG -- : Found block device: dm-4
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073471 #11814] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073479 #11814] DEBUG -- : Found block device: dm-5
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073490 #11814] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073498 #11814] DEBUG -- : Found block device: dm-6
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073508 #11814] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073558 #11814] DEBUG -- : Found block device: ram0
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073568 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073577 #11814] DEBUG -- : Found block device: ram1
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073588 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073597 #11814] DEBUG -- : Found block device: ram2
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073607 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073616 #11814] DEBUG -- : Found block device: ram3
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073657 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073666 #11814] DEBUG -- : Found block device: ram4
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073677 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073686 #11814] DEBUG -- : Found block device: ram5
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073697 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073705 #11814] DEBUG -- : Found block device: ram6
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073740 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073748 #11814] DEBUG -- : Found block device: ram7
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073759 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073767 #11814] DEBUG -- : Found block device: ram8
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073776 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073784 #11814] DEBUG -- : Found block device: ram9
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073795 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073804 #11814] DEBUG -- : Found block device: loop0
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073829 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073851 #11814] DEBUG -- : Found block device: loop1
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073862 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073873 #11814] DEBUG -- : Found block device: loop2
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073882 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073890 #11814] DEBUG -- : Found block device: loop3
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073899 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073924 #11814] DEBUG -- : Found block device: loop4
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073934 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073942 #11814] DEBUG -- : Found block device: loop5
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073951 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073968 #11814] DEBUG -- : Found block device: loop6
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073978 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.073986 #11814] DEBUG -- : Found block device: loop7
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074025 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074034 #11814] DEBUG -- : Found block device: ram10
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074043 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074052 #11814] DEBUG -- : Found block device: ram11
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074062 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074070 #11814] DEBUG -- : Found block device: ram12
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074080 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074101 #11814] DEBUG -- : Found block device: ram13
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074112 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074120 #11814] DEBUG -- : Found block device: ram14
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074129 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074138 #11814] DEBUG -- : Found block device: ram15
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074148 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.074205 #11814] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.166938 #11814] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 18 16:24:23 node-2 nailgun-agent: D, [2016-10-18T16:24:23.166984 #11814] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 18 16:24:26 node-2 puppet-user[14364]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 18 16:24:28 node-2 kernel: [   93.329665] init: plymouth-upstart-bridge main process ended, respawning
Oct 18 16:24:28 node-2 puppet-agent[8975]: Could not run: SIGTERM
Oct 18 16:24:28 node-2 kernel: [   93.610847] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 18 16:24:28 node-2 ec2: 
Oct 18 16:24:28 node-2 ec2: #############################################################
Oct 18 16:24:28 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 18 16:24:28 node-2 ec2: 1024 f1:37:97:81:33:46:8a:11:a8:69:79:c7:95:91:9b:de  root@node-2.domain.tld (DSA)
Oct 18 16:24:28 node-2 ec2: 256 9c:2f:55:83:a2:17:0a:78:d5:6a:40:20:4e:97:d5:70  root@node-2.domain.tld (ECDSA)
Oct 18 16:24:28 node-2 ec2: 256 af:ae:12:56:6f:19:1b:fa:98:91:20:6d:f5:89:c7:7e  root@node-2.domain.tld (ED25519)
Oct 18 16:24:28 node-2 ec2: 2048 c8:4b:5b:80:90:2b:dc:a2:47:e2:05:5a:dc:cd:6e:3d  root@node-2.domain.tld (RSA)
Oct 18 16:24:28 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 18 16:24:28 node-2 ec2: #############################################################
Oct 18 16:24:35 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367041 #11814] DEBUG -- : Trying to find block devices
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367271 #11814] DEBUG -- : Found block device: sda
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367348 #11814] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367400 #11814] DEBUG -- : Block device seems to be physical data storage: sda
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367459 #11814] DEBUG -- : Found block device: dm-0
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367498 #11814] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367603 #11814] DEBUG -- : Found block device: dm-1
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367635 #11814] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367661 #11814] DEBUG -- : Found block device: dm-2
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367689 #11814] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367715 #11814] DEBUG -- : Found block device: dm-3
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367741 #11814] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367764 #11814] DEBUG -- : Found block device: dm-4
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367791 #11814] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367816 #11814] DEBUG -- : Found block device: dm-5
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367845 #11814] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367869 #11814] DEBUG -- : Found block device: dm-6
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367950 #11814] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.367977 #11814] DEBUG -- : Found block device: ram0
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368005 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368028 #11814] DEBUG -- : Found block device: ram1
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368056 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368081 #11814] DEBUG -- : Found block device: ram2
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368108 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368132 #11814] DEBUG -- : Found block device: ram3
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368158 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368182 #11814] DEBUG -- : Found block device: ram4
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368208 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368291 #11814] DEBUG -- : Found block device: ram5
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368319 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368344 #11814] DEBUG -- : Found block device: ram6
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368372 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368396 #11814] DEBUG -- : Found block device: ram7
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368422 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368446 #11814] DEBUG -- : Found block device: ram8
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368472 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368495 #11814] DEBUG -- : Found block device: ram9
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368520 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368586 #11814] DEBUG -- : Found block device: loop0
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368613 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368637 #11814] DEBUG -- : Found block device: loop1
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368662 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368684 #11814] DEBUG -- : Found block device: loop2
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368711 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368786 #11814] DEBUG -- : Found block device: loop3
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368814 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368837 #11814] DEBUG -- : Found block device: loop4
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368863 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368888 #11814] DEBUG -- : Found block device: loop5
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368913 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368935 #11814] DEBUG -- : Found block device: loop6
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.368960 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369033 #11814] DEBUG -- : Found block device: loop7
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369059 #11814] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369082 #11814] DEBUG -- : Found block device: ram10
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369107 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369131 #11814] DEBUG -- : Found block device: ram11
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369157 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369181 #11814] DEBUG -- : Found block device: ram12
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369206 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369229 #11814] DEBUG -- : Found block device: ram13
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369254 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369327 #11814] DEBUG -- : Found block device: ram14
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369354 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369378 #11814] DEBUG -- : Found block device: ram15
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369403 #11814] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.369477 #11814] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct 18 16:24:35 node-2 nailgun-agent: D, [2016-10-18T16:24:35.634419 #11814] DEBUG -- : Response: status: 200 body: {"id": 2}
Oct 18 16:24:35 node-2 nailgun-agent: I, [2016-10-18T16:24:35.634797 #11814]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 18 16:24:57 node-2 puppet-user[14364]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 18 16:24:57 node-2 puppet-user[14364]: Finished catalog run in 34.61 seconds
Oct 18 16:24:58 node-2 puppet-user[17709]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 18 16:24:59 node-2 puppet-user[17709]: Compiled catalog for node-2.domain.tld in environment production in 0.58 seconds
Oct 18 16:24:59 node-2 puppet-user[17709]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 18 16:24:59 node-2 puppet-user[17709]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 18 16:24:59 node-2 puppet-user[17709]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 18 16:24:59 node-2 puppet-user[17709]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 18 16:24:59 node-2 puppet-user[17709]: Finished catalog run in 0.09 seconds
Oct 18 16:25:01 node-2 puppet-user[18183]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 18 16:25:01 node-2 CRON[18592]: (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:25:02 node-2 puppet-user[18183]: Compiled catalog for node-2.domain.tld in environment production in 0.91 seconds
Oct 18 16:25:02 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 18 16:25:02 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 18 16:25:02 node-2 crontab[18617]: (root) LIST (root)
Oct 18 16:25:02 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 18 16:25:02 node-2 crontab[18618]: (root) REPLACE (root)
Oct 18 16:25:04 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 18 16:25:04 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:25:05 node-2 puppet-user[18183]: (/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:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:25:05 node-2 puppet-user[18183]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/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:05 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 18 16:25:05 node-2 nailgun-agent: I, [2016-10-18T16:25:05.815665 #18595]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 18 16:25:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/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:05 node-2 puppet-user[18183]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 18 16:25:06 node-2 puppet-user[18183]: (/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:06 node-2 puppet-user[18183]: (/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:06 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8426" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 18 16:25:06 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 18 16:25:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:20 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:20 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:20 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:20 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:20 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:22 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:22 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:25:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:19 node-2 ntpdate[29307]: no servers can be used, exiting
<27>Oct 18 16:26:19 node-2 ntpdate[29556]: no servers can be used, exiting
<27>Oct 18 16:26:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:53 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:53 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:53 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:53 node-2 multipathd: uevent trigger error
<27>Oct 18 16:26:53 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:08 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:08 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:08 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:08 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:08 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:08 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:08 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:13 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:13 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:13 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:13 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:13 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:27:54 node-2 multipathd: uevent trigger error
<43>Oct 18 16:28:07 node-2 apache2_error [Tue Oct 18 16:28:05.570163 2016] [mpm_event:notice] [pid 9801:tid 140597907507072] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 18 16:28:07 node-2 apache2_error [Tue Oct 18 16:28:05.570250 2016] [core:notice] [pid 9801:tid 140597907507072] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:28:13 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:14 node-2 multipathd: uevent trigger error
<43>Oct 18 16:28:17 node-2 apache2_error [Tue Oct 18 16:28:08.678661 2016] [mpm_event:notice] [pid 9801:tid 140597907507072] AH00491: caught SIGTERM, shutting down
<43>Oct 18 16:28:17 node-2 apache2_error [Tue Oct 18 16:28:09.763323 2016] [mpm_worker:notice] [pid 10109:tid 140071199324032] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 18 16:28:17 node-2 apache2_error [Tue Oct 18 16:28:09.763374 2016] [core:notice] [pid 10109:tid 140071199324032] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:28:48 node-2 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Oct 18 16:28:52 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:52 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:52 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:52 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:52 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:28:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:02 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:02 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:02 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:02 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:02 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:02 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:10 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:13 node-2 haproxy[20750]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:19 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:19 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:19 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:19 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:19 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:21 node-2 haproxy[22942]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:22 node-2 haproxy[22946]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:24 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:27 node-2 haproxy[24289]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:27 node-2 haproxy[24289]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:30 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:30 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:30 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:30 node-2 haproxy[24289]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:30 node-2 haproxy[24289]: proxy odl-jetty has no server available!
<129>Oct 18 16:29:32 node-2 haproxy[25424]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:32 node-2 haproxy[25424]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:33 node-2 haproxy[25430]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:35 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:35 node-2 haproxy[25430]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:35 node-2 haproxy[25430]: proxy odl-jetty has no server available!
<129>Oct 18 16:29:37 node-2 haproxy[26779]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:37 node-2 haproxy[26779]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:38 node-2 haproxy[26783]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:38 node-2 haproxy[26783]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:39 node-2 haproxy[26783]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:40 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:41 node-2 haproxy[26783]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:41 node-2 haproxy[26783]: proxy odl-jetty has no server available!
<129>Oct 18 16:29:42 node-2 haproxy[27888]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:43 node-2 haproxy[27892]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:43 node-2 haproxy[27892]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:43 node-2 haproxy[27892]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:44 node-2 haproxy[27892]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:44 node-2 haproxy[27892]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:45 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:46 node-2 haproxy[27892]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:46 node-2 haproxy[27892]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:46 node-2 haproxy[27892]: proxy aodh has no server available!
<129>Oct 18 16:29:46 node-2 haproxy[27892]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:46 node-2 haproxy[27892]: proxy odl-jetty has no server available!
<129>Oct 18 16:29:48 node-2 haproxy[29027]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:48 node-2 haproxy[29027]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:48 node-2 haproxy[29027]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:48 node-2 haproxy[29027]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:49 node-2 haproxy[29027]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:49 node-2 haproxy[29027]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:49 node-2 haproxy[29027]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:51 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:51 node-2 haproxy[29027]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:51 node-2 haproxy[29027]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:51 node-2 haproxy[29027]: proxy aodh has no server available!
<129>Oct 18 16:29:51 node-2 haproxy[29027]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:51 node-2 haproxy[29027]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:51 node-2 haproxy[29027]: proxy ceilometer has no server available!
<129>Oct 18 16:29:51 node-2 haproxy[29027]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:51 node-2 haproxy[29027]: proxy odl-jetty has no server available!
<129>Oct 18 16:29:53 node-2 haproxy[30150]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:53 node-2 haproxy[30150]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:53 node-2 haproxy[30150]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:54 node-2 haproxy[30154]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:54 node-2 haproxy[30154]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:54 node-2 haproxy[30154]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:54 node-2 haproxy[30154]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:29:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:56 node-2 multipathd: uevent trigger error
<27>Oct 18 16:29:56 node-2 multipathd: uevent trigger error
<129>Oct 18 16:29:56 node-2 haproxy[30154]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:56 node-2 haproxy[30154]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:56 node-2 haproxy[30154]: proxy aodh has no server available!
<129>Oct 18 16:29:56 node-2 haproxy[30154]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:56 node-2 haproxy[30154]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:56 node-2 haproxy[30154]: proxy ceilometer has no server available!
<129>Oct 18 16:29:57 node-2 haproxy[30154]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:29:57 node-2 haproxy[30154]: proxy odl-jetty has no server available!
<129>Oct 18 16:29:58 node-2 haproxy[31305]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[31305]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:59 node-2 haproxy[31309]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:59 node-2 haproxy[31309]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:59 node-2 haproxy[31309]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:29:59 node-2 haproxy[31309]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:00 node-2 haproxy[31309]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:00 node-2 haproxy[31309]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:00 node-2 haproxy[31309]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:30:01 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:01 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:01 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:01 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:01 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:01 node-2 multipathd: uevent trigger error
<129>Oct 18 16:30:01 node-2 haproxy[31309]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:01 node-2 haproxy[31309]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:01 node-2 haproxy[31309]: proxy aodh has no server available!
<129>Oct 18 16:30:02 node-2 haproxy[31309]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:02 node-2 haproxy[31309]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:02 node-2 haproxy[31309]: proxy ceilometer has no server available!
<129>Oct 18 16:30:02 node-2 haproxy[31309]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:02 node-2 haproxy[31309]: proxy odl-jetty has no server available!
<129>Oct 18 16:30:04 node-2 haproxy[32637]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[32637]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[32637]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:04 node-2 haproxy[32637]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:05 node-2 haproxy[32641]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:05 node-2 haproxy[32641]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:05 node-2 haproxy[32641]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:05 node-2 haproxy[32641]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:05 node-2 haproxy[32641]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:05 node-2 haproxy[32641]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:06 node-2 haproxy[32641]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:06 node-2 haproxy[32641]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:30:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:07 node-2 multipathd: uevent trigger error
<129>Oct 18 16:30:07 node-2 haproxy[32641]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:30:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:07 node-2 multipathd: uevent trigger error
<129>Oct 18 16:30:07 node-2 haproxy[32641]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:07 node-2 haproxy[32641]: proxy glance-registry has no server available!
<129>Oct 18 16:30:07 node-2 haproxy[32641]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:07 node-2 haproxy[32641]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:07 node-2 haproxy[32641]: proxy aodh has no server available!
<129>Oct 18 16:30:07 node-2 haproxy[32641]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:07 node-2 haproxy[32641]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:07 node-2 haproxy[32641]: proxy ceilometer has no server available!
<129>Oct 18 16:30:08 node-2 haproxy[32641]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:08 node-2 haproxy[32641]: proxy odl-jetty has no server available!
<129>Oct 18 16:30:09 node-2 haproxy[1410]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[1414]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[1414]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:10 node-2 haproxy[1414]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:10 node-2 haproxy[1414]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:10 node-2 haproxy[1414]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:10 node-2 haproxy[1414]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:10 node-2 haproxy[1414]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:11 node-2 haproxy[1414]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:11 node-2 haproxy[1414]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:11 node-2 haproxy[1414]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:11 node-2 haproxy[1414]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:11 node-2 haproxy[1414]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:11 node-2 haproxy[1414]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:11 node-2 haproxy[1414]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:30:12 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:12 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:12 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:12 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:12 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:12 node-2 multipathd: uevent trigger error
<129>Oct 18 16:30:12 node-2 haproxy[1414]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:12 node-2 haproxy[1414]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:12 node-2 haproxy[1414]: proxy glance-registry has no server available!
<129>Oct 18 16:30:13 node-2 haproxy[1414]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:13 node-2 haproxy[1414]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:13 node-2 haproxy[1414]: proxy aodh has no server available!
<129>Oct 18 16:30:13 node-2 haproxy[1414]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:13 node-2 haproxy[1414]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:13 node-2 haproxy[1414]: proxy ceilometer has no server available!
<129>Oct 18 16:30:13 node-2 haproxy[1414]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:13 node-2 haproxy[1414]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:13 node-2 haproxy[1414]: proxy nova-novncproxy has no server available!
<129>Oct 18 16:30:13 node-2 haproxy[1414]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:13 node-2 haproxy[1414]: proxy odl-jetty has no server available!
<129>Oct 18 16:30:15 node-2 haproxy[2695]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[2695]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[2695]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-2 haproxy[2695]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-2 haproxy[2695]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-2 haproxy[2695]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-2 haproxy[2695]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:15 node-2 haproxy[2695]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:16 node-2 haproxy[2695]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:30:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:17 node-2 multipathd: uevent trigger error
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:18 node-2 haproxy[2695]: proxy glance-registry has no server available!
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:18 node-2 haproxy[2695]: proxy aodh has no server available!
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:18 node-2 haproxy[2695]: proxy ceilometer has no server available!
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:18 node-2 haproxy[2695]: proxy nova-novncproxy has no server available!
<129>Oct 18 16:30:18 node-2 haproxy[2695]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:18 node-2 haproxy[2695]: proxy odl-jetty has no server available!
<129>Oct 18 16:30:20 node-2 haproxy[3896]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[3900]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-2 haproxy[3900]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-2 haproxy[3900]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-2 haproxy[3900]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-2 haproxy[3900]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-2 haproxy[3900]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-2 haproxy[3900]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-2 haproxy[3900]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:21 node-2 haproxy[3900]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:22 node-2 haproxy[3900]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 18 16:30:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:23 node-2 multipathd: uevent trigger error
<129>Oct 18 16:30:23 node-2 haproxy[3900]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:23 node-2 haproxy[3900]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:23 node-2 haproxy[3900]: proxy glance-registry has no server available!
<129>Oct 18 16:30:24 node-2 haproxy[3900]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:24 node-2 haproxy[3900]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:24 node-2 haproxy[3900]: proxy aodh has no server available!
<129>Oct 18 16:30:24 node-2 haproxy[3900]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:24 node-2 haproxy[3900]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:24 node-2 haproxy[3900]: proxy ceilometer has no server available!
<129>Oct 18 16:30:24 node-2 haproxy[3900]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:24 node-2 haproxy[3900]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:24 node-2 haproxy[3900]: proxy nova-novncproxy has no server available!
<129>Oct 18 16:30:24 node-2 haproxy[3900]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:24 node-2 haproxy[3900]: proxy odl-jetty has no server available!
<27>Oct 18 16:30:26 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:26 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:26 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:26 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:26 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:26 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:30 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:30 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:30 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:30 node-2 multipathd: uevent trigger error
<27>Oct 18 16:30:30 node-2 multipathd: uevent trigger error
<129>Oct 18 16:30:30 node-2 haproxy[3900]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:30 node-2 haproxy[3900]: proxy odl-neutron-endpoint has no server available!
<129>Oct 18 16:30:30 node-2 haproxy[3900]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server keystone-1/node-4 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy keystone-1 has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server keystone-2/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy keystone-2 has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server nova-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy nova-api has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy nova-metadata-api has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 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-2 haproxy[3900]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy cinder-api has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server glance-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy glance-api has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server glance-glare/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy glance-glare has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server neutron/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy neutron has no server available!
<129>Oct 18 16:30:31 node-2 haproxy[3900]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 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-2 haproxy[3900]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:31 node-2 haproxy[3900]: proxy mysqld has no server available!
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server object-storage/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:32 node-2 haproxy[3900]: proxy object-storage has no server available!
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server heat-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:32 node-2 haproxy[3900]: proxy heat-api has no server available!
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:32 node-2 haproxy[3900]: proxy heat-api-cfn has no server available!
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:30:32 node-2 haproxy[3900]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:30:32 node-2 haproxy[3900]: proxy heat-api-cloudwatch has no server available!
<27>Oct 18 16:30:42 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 18 16:31:06 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:06 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:06 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:06 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:06 node-2 multipathd: uevent trigger error
<43>Oct 18 16:31:07 node-2 apache2_error [Tue Oct 18 16:31:03.516505 2016] [mpm_worker:notice] [pid 10109:tid 140071199324032] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:31:07 node-2 apache2_error [Tue Oct 18 16:31:03.525621 2016] [mpm_worker:warn] [pid 10109:tid 140071199324032] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:31:07 node-2 apache2_error [Tue Oct 18 16:31:03.526416 2016] [mpm_worker:notice] [pid 10109:tid 140071199324032] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 18 16:31:07 node-2 apache2_error [Tue Oct 18 16:31:03.526431 2016] [core:notice] [pid 10109:tid 140071199324032] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:31:08 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 18 16:31:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:31:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:00 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 18 16:32:01 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 18 16:32:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:05 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:05 node-2 multipathd: uevent trigger error
<129>Oct 18 16:32:08 node-2 haproxy[20914]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:08 node-2 haproxy[20914]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:08 node-2 haproxy[20914]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:08 node-2 haproxy[20914]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:09 node-2 haproxy[20925]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:10 node-2 haproxy[20925]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:10 node-2 haproxy[20925]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:10 node-2 haproxy[20925]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:10 node-2 haproxy[20925]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:10 node-2 haproxy[20925]: Server tacker/node-2 is DOWN, reason: Layer4 connection problem, 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:32:10 node-2 haproxy[20925]: proxy tacker has no server available!
<129>Oct 18 16:32:10 node-2 haproxy[20925]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:10 node-2 haproxy[20925]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:11 node-2 haproxy[20925]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:11 node-2 haproxy[20925]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:11 node-2 haproxy[20925]: proxy glance-registry has no server available!
<27>Oct 18 16:32:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:11 node-2 multipathd: uevent trigger error
<129>Oct 18 16:32:11 node-2 haproxy[20925]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:11 node-2 haproxy[20925]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:11 node-2 haproxy[20925]: proxy aodh has no server available!
<129>Oct 18 16:32:11 node-2 haproxy[20925]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:11 node-2 haproxy[20925]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:11 node-2 haproxy[20925]: proxy ceilometer has no server available!
<129>Oct 18 16:32:12 node-2 haproxy[20925]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:12 node-2 haproxy[20925]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:12 node-2 haproxy[20925]: proxy nova-novncproxy has no server available!
<129>Oct 18 16:32:12 node-2 haproxy[20925]: Server odl-jetty/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:12 node-2 haproxy[20925]: proxy odl-jetty has no server available!
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 timeout, check duration: 5000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:18 node-2 haproxy[20925]: proxy odl-neutron-endpoint has no server available!
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server keystone-1/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:18 node-2 haproxy[20925]: proxy keystone-1 has no server available!
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server keystone-2/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:18 node-2 haproxy[20925]: proxy keystone-2 has no server available!
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server nova-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:18 node-2 haproxy[20925]: proxy nova-api has no server available!
<129>Oct 18 16:32:18 node-2 haproxy[20925]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:19 node-2 haproxy[20925]: proxy nova-metadata-api has no server available!
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:19 node-2 haproxy[20925]: proxy cinder-api has no server available!
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server glance-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:19 node-2 haproxy[20925]: proxy glance-api has no server available!
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server glance-glare/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:19 node-2 haproxy[20925]: proxy glance-glare has no server available!
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server neutron/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:19 node-2 haproxy[20925]: proxy neutron has no server available!
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:19 node-2 haproxy[20925]: proxy mysqld has no server available!
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:19 node-2 haproxy[20925]: Server object-storage/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:19 node-2 haproxy[20925]: proxy object-storage has no server available!
<129>Oct 18 16:32:20 node-2 haproxy[20925]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:20 node-2 haproxy[20925]: Server heat-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:20 node-2 haproxy[20925]: proxy heat-api has no server available!
<129>Oct 18 16:32:20 node-2 haproxy[20925]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:20 node-2 haproxy[20925]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:20 node-2 haproxy[20925]: proxy heat-api-cfn has no server available!
<129>Oct 18 16:32:20 node-2 haproxy[20925]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 18 16:32:20 node-2 haproxy[20925]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 18 16:32:20 node-2 haproxy[20925]: proxy heat-api-cloudwatch has no server available!
<27>Oct 18 16:32:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:32:33 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 18 16:33:27 node-2 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:33:29 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 18 16:34:43 node-2 multipathd: uevent trigger error
<27>Oct 18 16:34:43 node-2 multipathd: uevent trigger error
<27>Oct 18 16:34:43 node-2 multipathd: uevent trigger error
<27>Oct 18 16:34:43 node-2 multipathd: uevent trigger error
<27>Oct 18 16:34:43 node-2 multipathd: uevent trigger error
<27>Oct 18 16:34:43 node-2 multipathd: uevent trigger error
<27>Oct 18 16:34:43 node-2 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-2 multipathd: uevent trigger error
<27>Oct 18 16:37:40 node-2 multipathd: uevent trigger error
<43>Oct 18 16:38:57 node-2 apache2_error [Tue Oct 18 16:38:50.443589 2016] [mpm_worker:notice] [pid 10109:tid 140071199324032] AH00295: caught SIGTERM, shutting down
<43>Oct 18 16:38:57 node-2 apache2_error [Tue Oct 18 16:38:51.190841 2016] [mpm_worker:notice] [pid 12303:tid 139827442407296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:38:57 node-2 apache2_error [Tue Oct 18 16:38:51.190887 2016] [core:notice] [pid 12303:tid 139827442407296] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 18 16:39:27 node-2 apache2_error [Tue Oct 18 16:39:23.076039 2016] [mpm_worker:notice] [pid 12303:tid 139827442407296] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:39:27 node-2 apache2_error [Tue Oct 18 16:39:23.086423 2016] [mpm_worker:warn] [pid 12303:tid 139827442407296] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:39:27 node-2 apache2_error [Tue Oct 18 16:39:23.091412 2016] [mpm_worker:notice] [pid 12303:tid 139827442407296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:39:27 node-2 apache2_error [Tue Oct 18 16:39:23.091442 2016] [core:notice] [pid 12303:tid 139827442407296] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:39:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:39:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:39:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:39:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:39:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:39:29 node-2 multipathd: uevent trigger error
<27>Oct 18 16:40:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:40:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:40:24 node-2 multipathd: uevent trigger error
<27>Oct 18 16:40:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:40:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:40:25 node-2 multipathd: uevent trigger error
<27>Oct 18 16:41:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:41:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:41:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:41:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:41:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:45:23 node-2 multipathd: uevent trigger error
<27>Oct 18 16:47:28 node-2 multipathd: uevent trigger error
<27>Oct 18 16:47:28 node-2 multipathd: uevent trigger error
<27>Oct 18 16:47:28 node-2 multipathd: uevent trigger error
<27>Oct 18 16:47:28 node-2 multipathd: uevent trigger error
<27>Oct 18 16:47:28 node-2 multipathd: uevent trigger error
<27>Oct 18 16:47:28 node-2 multipathd: uevent trigger error
<27>Oct 18 16:48:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:48:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:48:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:48:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:48:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:48:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:48:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:07 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:15 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:21 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:21 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:21 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:21 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:21 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:21 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:36 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:42 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:42 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:42 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:42 node-2 multipathd: uevent trigger error
<27>Oct 18 16:49:42 node-2 multipathd: uevent trigger error
<43>Oct 18 16:50:28 node-2 apache2_error [Tue Oct 18 16:50:28.442821 2016] [mpm_worker:notice] [pid 12303:tid 139827442407296] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:50:38 node-2 apache2_error [Tue Oct 18 16:50:28.828507 2016] [mpm_worker:warn] [pid 12303:tid 139827442407296] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:50:38 node-2 apache2_error [Tue Oct 18 16:50:28.832720 2016] [mpm_worker:notice] [pid 12303:tid 139827442407296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:50:38 node-2 apache2_error [Tue Oct 18 16:50:28.832740 2016] [core:notice] [pid 12303:tid 139827442407296] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 18 16:51:08 node-2 apache2_error [Tue Oct 18 16:51:05.482234 2016] [mpm_worker:notice] [pid 12303:tid 139827442407296] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 18 16:51:08 node-2 apache2_error [Tue Oct 18 16:51:05.863358 2016] [mpm_worker:warn] [pid 12303:tid 139827442407296] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 18 16:51:08 node-2 apache2_error [Tue Oct 18 16:51:05.874564 2016] [mpm_worker:notice] [pid 12303:tid 139827442407296] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 18 16:51:08 node-2 apache2_error [Tue Oct 18 16:51:05.874594 2016] [core:notice] [pid 12303:tid 139827442407296] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 18 16:51:09 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:09 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:09 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:09 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:09 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:09 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:51:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:10 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:57 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:57 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:57 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:57 node-2 multipathd: uevent trigger error
<27>Oct 18 16:53:57 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:11 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:11 node-2 multipathd: uevent trigger error
<11>Oct 18 16:54:20 node-2 liberasurecode[27682]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:20 node-2 liberasurecode[27682]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:20 node-2 liberasurecode[27682]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:20 node-2 liberasurecode[27682]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:20 node-2 liberasurecode[27711]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:20 node-2 liberasurecode[27711]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:20 node-2 liberasurecode[27711]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:20 node-2 liberasurecode[27711]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:21 node-2 liberasurecode[28195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:21 node-2 liberasurecode[28195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:21 node-2 liberasurecode[28195]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:21 node-2 liberasurecode[28195]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28695]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28695]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28695]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28695]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28734]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28734]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28734]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28734]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28787]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28787]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28787]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[28787]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29062]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29062]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29062]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29062]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29083]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29083]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29083]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29083]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29117]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29117]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29117]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:26 node-2 liberasurecode[29117]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:27 node-2 liberasurecode[29172]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:27 node-2 liberasurecode[29172]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:27 node-2 liberasurecode[29172]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:54:27 node-2 liberasurecode[29172]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 18 16:54:33 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:33 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:33 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:33 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:33 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:54:37 node-2 multipathd: uevent trigger error
<11>Oct 18 16:55:02 node-2 liberasurecode[3538]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:55:02 node-2 liberasurecode[3538]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:55:02 node-2 liberasurecode[3538]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 18 16:55:02 node-2 liberasurecode[3538]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 18 16:56:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:17 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:56:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:32 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:37 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:50 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:58:54 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:14 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:27 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:31 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:35 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:39 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:45 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:49 node-2 multipathd: uevent trigger error
<27>Oct 18 16:59:49 node-2 multipathd: uevent trigger error
<11>Oct 18 17:00:01 node-2 liberasurecode[25815]: 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-2 liberasurecode[25815]: 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-2 liberasurecode[25815]: 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-2 liberasurecode[25815]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 18 17:00:12 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 18 17:00:12 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
