Nov  7 20:56:19 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8430" x-info="http://www.rsyslog.com"] start
Nov  7 20:56:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  7 20:56:19 node-2 rsyslogd: rsyslogd's groupid changed to 104
Nov  7 20:56:19 node-2 rsyslogd: rsyslogd's userid changed to 101
Nov  7 20:56:19 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  7 20:56:19 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  7 20:56:19 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  7 20:56:19 node-2 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Nov  7 20:56:19 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=9fc91301-5dc4-4fdc-8130-eef4fe18c38a nomdmonddf nomdmonisw
Nov  7 20:56:19 node-2 kernel: [    0.000000] KERNEL supported cpus:
Nov  7 20:56:19 node-2 kernel: [    0.000000]   Intel GenuineIntel
Nov  7 20:56:19 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Nov  7 20:56:19 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Nov  7 20:56:19 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov  7 20:56:19 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  7 20:56:19 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  7 20:56:19 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
Nov  7 20:56:19 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  7 20:56:19 node-2 kernel: [    0.000000] No AGP bridge found
Nov  7 20:56:19 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov  7 20:56:19 node-2 kernel: [    0.000000] MTRR default type: write-back
Nov  7 20:56:19 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  7 20:56:19 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Nov  7 20:56:19 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  7 20:56:19 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov  7 20:56:19 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  7 20:56:19 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  7 20:56:19 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov  7 20:56:19 node-2 kernel: [    0.000000]   2 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000]   3 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000]   4 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000]   5 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000]   6 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000]   7 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000]   8 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000]   9 disabled
Nov  7 20:56:19 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  7 20:56:19 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov  7 20:56:19 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov  7 20:56:19 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  7 20:56:19 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov  7 20:56:19 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  7 20:56:19 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  7 20:56:19 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  7 20:56:19 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov  7 20:56:19 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov  7 20:56:19 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov  7 20:56:19 node-2 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  7 20:56:19 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov  7 20:56:19 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov  7 20:56:19 node-2 kernel: [    0.000000] Zone ranges:
Nov  7 20:56:19 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] Movable zone start for each node
Nov  7 20:56:19 node-2 kernel: [    0.000000] Early memory node ranges
Nov  7 20:56:19 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Nov  7 20:56:19 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  7 20:56:19 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  7 20:56:19 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov  7 20:56:19 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Nov  7 20:56:19 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Nov  7 20:56:19 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov  7 20:56:19 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov  7 20:56:19 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov  7 20:56:19 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov  7 20:56:19 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  7 20:56:19 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  7 20:56:19 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  7 20:56:19 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  7 20:56:19 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  7 20:56:19 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  7 20:56:19 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov  7 20:56:19 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov  7 20:56:19 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov  7 20:56:19 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  7 20:56:19 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov  7 20:56:19 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov  7 20:56:19 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov  7 20:56:19 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 
Nov  7 20:56:19 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Nov  7 20:56:19 node-2 kernel: [    0.000000] Policy zone: Normal
Nov  7 20:56:19 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=9fc91301-5dc4-4fdc-8130-eef4fe18c38a nomdmonddf nomdmonisw
Nov  7 20:56:19 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  7 20:56:19 node-2 kernel: [    0.000000] Checking aperture...
Nov  7 20:56:19 node-2 kernel: [    0.000000] No AGP bridge found
Nov  7 20:56:19 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  7 20:56:19 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  7 20:56:19 node-2 kernel: [    0.000000] Memory: 32653308K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627188K reserved)
Nov  7 20:56:19 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov  7 20:56:19 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  7 20:56:19 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  7 20:56:19 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov  7 20:56:19 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  7 20:56:19 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov  7 20:56:19 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov  7 20:56:19 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  7 20:56:19 node-2 kernel: [    0.000000] console [tty0] enabled
Nov  7 20:56:19 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov  7 20:56:19 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  7 20:56:19 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  7 20:56:19 node-2 kernel: [    0.000000] hpet clockevent registered
Nov  7 20:56:19 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  7 20:56:19 node-2 kernel: [    0.004000] tsc: Detected 3491.920 MHz processor
Nov  7 20:56:19 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.84 BogoMIPS (lpj=13967680)
Nov  7 20:56:19 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov  7 20:56:19 node-2 kernel: [    0.000052] Security Framework initialized
Nov  7 20:56:19 node-2 kernel: [    0.000070] AppArmor: AppArmor initialized
Nov  7 20:56:19 node-2 kernel: [    0.000071] Yama: becoming mindful.
Nov  7 20:56:19 node-2 kernel: [    0.001474] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.006398] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.008324] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.008352] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.008641] Initializing cgroup subsys memory
Nov  7 20:56:19 node-2 kernel: [    0.008650] Initializing cgroup subsys devices
Nov  7 20:56:19 node-2 kernel: [    0.008651] Initializing cgroup subsys freezer
Nov  7 20:56:19 node-2 kernel: [    0.008653] Initializing cgroup subsys blkio
Nov  7 20:56:19 node-2 kernel: [    0.008655] Initializing cgroup subsys perf_event
Nov  7 20:56:19 node-2 kernel: [    0.008657] Initializing cgroup subsys hugetlb
Nov  7 20:56:19 node-2 kernel: [    0.008676] CPU: Physical Processor ID: 0
Nov  7 20:56:19 node-2 kernel: [    0.008678] CPU: Processor Core ID: 0
Nov  7 20:56:19 node-2 kernel: [    0.008682] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov  7 20:56:19 node-2 kernel: [    0.008682] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov  7 20:56:19 node-2 kernel: [    0.009375] mce: CPU supports 22 MCE banks
Nov  7 20:56:19 node-2 kernel: [    0.009403] CPU0: Thermal monitoring enabled (TM1)
Nov  7 20:56:19 node-2 kernel: [    0.009424] process: using mwait in idle threads
Nov  7 20:56:19 node-2 kernel: [    0.009427] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  7 20:56:19 node-2 kernel: [    0.009427] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  7 20:56:19 node-2 kernel: [    0.009427] tlb_flushall_shift: 6
Nov  7 20:56:19 node-2 kernel: [    0.009515] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  7 20:56:19 node-2 kernel: [    0.010236] ACPI: Core revision 20131115
Nov  7 20:56:19 node-2 kernel: [    0.023042] ACPI: All ACPI Tables successfully acquired
Nov  7 20:56:19 node-2 kernel: [    0.023202] ftrace: allocating 28622 entries in 112 pages
Nov  7 20:56:19 node-2 kernel: [    0.031961] dmar: Host address width 46
Nov  7 20:56:19 node-2 kernel: [    0.031963] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  7 20:56:19 node-2 kernel: [    0.031969] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  7 20:56:19 node-2 kernel: [    0.031971] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  7 20:56:19 node-2 kernel: [    0.031975] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  7 20:56:19 node-2 kernel: [    0.031977] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov  7 20:56:19 node-2 kernel: [    0.031978] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov  7 20:56:19 node-2 kernel: [    0.031979] dmar: ATSR flags: 0x0
Nov  7 20:56:19 node-2 kernel: [    0.031980] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov  7 20:56:19 node-2 kernel: [    0.031981] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov  7 20:56:19 node-2 kernel: [    0.032097] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  7 20:56:19 node-2 kernel: [    0.032098] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  7 20:56:19 node-2 kernel: [    0.032099] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  7 20:56:19 node-2 kernel: [    0.032100] HPET id 0 under DRHD base 0xc7ffc000
Nov  7 20:56:19 node-2 kernel: [    0.032101] Your BIOS is broken and requested that x2apic be disabled.
Nov  7 20:56:19 node-2 kernel: [    0.032101] This will slightly decrease performance.
Nov  7 20:56:19 node-2 kernel: [    0.032101] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov  7 20:56:19 node-2 kernel: [    0.032533] Enabled IRQ remapping in xapic mode
Nov  7 20:56:19 node-2 kernel: [    0.032534] x2apic not enabled, IRQ remapping is in xapic mode
Nov  7 20:56:19 node-2 kernel: [    0.032538] Switched APIC routing to physical flat.
Nov  7 20:56:19 node-2 kernel: [    0.033163] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  7 20:56:19 node-2 kernel: [    0.072812] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  7 20:56:19 node-2 kernel: [    0.072818] TSC deadline timer enabled
Nov  7 20:56:19 node-2 kernel: [    0.072825] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov  7 20:56:19 node-2 kernel: [    0.072831] ... version:                3
Nov  7 20:56:19 node-2 kernel: [    0.072832] ... bit width:              48
Nov  7 20:56:19 node-2 kernel: [    0.072833] ... generic registers:      4
Nov  7 20:56:19 node-2 kernel: [    0.072834] ... value mask:             0000ffffffffffff
Nov  7 20:56:19 node-2 kernel: [    0.072835] ... max period:             0000ffffffffffff
Nov  7 20:56:19 node-2 kernel: [    0.072836] ... fixed-purpose events:   3
Nov  7 20:56:19 node-2 kernel: [    0.072837] ... event mask:             000000070000000f
Nov  7 20:56:19 node-2 kernel: [    0.074261] x86: Booting SMP configuration:
Nov  7 20:56:19 node-2 kernel: [    0.088364] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  7 20:56:19 node-2 kernel: [    0.074263] .... node  #0, CPUs:        #1  #2  #3
Nov  7 20:56:19 node-2 kernel: [    0.116285] .... node  #1, CPUs:    #4  #5  #6  #7
Nov  7 20:56:19 node-2 kernel: [    0.270427] .... node  #0, CPUs:    #8  #9 #10 #11
Nov  7 20:56:19 node-2 kernel: [    0.326042] .... node  #1, CPUs:   #12 #13 #14 #15
Nov  7 20:56:19 node-2 kernel: [    0.383100] x86: Booted up 2 nodes, 16 CPUs
Nov  7 20:56:19 node-2 kernel: [    0.383103] smpboot: Total of 16 processors activated (111753.54 BogoMIPS)
Nov  7 20:56:19 node-2 kernel: [    0.407858] devtmpfs: initialized
Nov  7 20:56:19 node-2 kernel: [    0.410611] EVM: security.selinux
Nov  7 20:56:19 node-2 kernel: [    0.410613] EVM: security.SMACK64
Nov  7 20:56:19 node-2 kernel: [    0.410614] EVM: security.ima
Nov  7 20:56:19 node-2 kernel: [    0.410615] EVM: security.capability
Nov  7 20:56:19 node-2 kernel: [    0.410664] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.411354] pinctrl core: initialized pinctrl subsystem
Nov  7 20:56:19 node-2 kernel: [    0.411419] regulator-dummy: no parameters
Nov  7 20:56:19 node-2 kernel: [    0.411451] RTC time: 20:55:41, date: 11/07/16
Nov  7 20:56:19 node-2 kernel: [    0.411485] NET: Registered protocol family 16
Nov  7 20:56:19 node-2 kernel: [    0.411569] cpuidle: using governor ladder
Nov  7 20:56:19 node-2 kernel: [    0.411570] cpuidle: using governor menu
Nov  7 20:56:19 node-2 kernel: [    0.411604] ACPI: bus type PCI registered
Nov  7 20:56:19 node-2 kernel: [    0.411606] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  7 20:56:19 node-2 kernel: [    0.411651] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  7 20:56:19 node-2 kernel: [    0.411654] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  7 20:56:19 node-2 kernel: [    0.425391] PCI: Using configuration type 1 for base access
Nov  7 20:56:19 node-2 kernel: [    0.426392] bio: create slab <bio-0> at 0
Nov  7 20:56:19 node-2 kernel: [    0.426681] ACPI: Added _OSI(Module Device)
Nov  7 20:56:19 node-2 kernel: [    0.426683] ACPI: Added _OSI(Processor Device)
Nov  7 20:56:19 node-2 kernel: [    0.426684] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  7 20:56:19 node-2 kernel: [    0.426685] ACPI: Added _OSI(Processor Aggregator Device)
Nov  7 20:56:19 node-2 kernel: [    0.439385] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov  7 20:56:19 node-2 kernel: [    0.449945] ACPI: Interpreter enabled
Nov  7 20:56:19 node-2 kernel: [    0.449951] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  7 20:56:19 node-2 kernel: [    0.449955] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  7 20:56:19 node-2 kernel: [    0.449958] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  7 20:56:19 node-2 kernel: [    0.449964] ACPI: (supports S0 S4 S5)
Nov  7 20:56:19 node-2 kernel: [    0.449966] ACPI: Using IOAPIC for interrupt routing
Nov  7 20:56:19 node-2 kernel: [    0.450007] HEST: Table parsing has been initialized.
Nov  7 20:56:19 node-2 kernel: [    0.450010] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  7 20:56:19 node-2 kernel: [    0.450566] ACPI: No dock devices found.
Nov  7 20:56:19 node-2 kernel: [    0.462144] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  7 20:56:19 node-2 kernel: [    0.462148] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  7 20:56:19 node-2 kernel: [    0.462152] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  7 20:56:19 node-2 kernel: [    0.462181] PCI host bridge to bus 0000:ff
Nov  7 20:56:19 node-2 kernel: [    0.462183] pci_bus 0000:ff: root bus resource [bus ff]
Nov  7 20:56:19 node-2 kernel: [    0.462191] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462230] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.462261] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462297] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462327] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.462357] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.462389] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462418] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462449] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462478] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462505] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462532] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462560] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462587] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462614] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462640] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462669] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462696] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462723] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.462752] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462777] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.462803] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462829] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462860] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.462895] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462926] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462956] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.462987] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463018] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463049] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463080] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463111] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463144] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463177] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463210] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463243] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463276] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463307] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463335] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463369] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463403] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463441] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463480] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463513] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463544] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463573] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463603] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463634] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463666] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463697] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463729] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463758] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463787] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463816] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463846] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463879] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463911] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.463968] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  7 20:56:19 node-2 kernel: [    0.463970] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  7 20:56:19 node-2 kernel: [    0.463973] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  7 20:56:19 node-2 kernel: [    0.463991] PCI host bridge to bus 0000:7f
Nov  7 20:56:19 node-2 kernel: [    0.463993] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  7 20:56:19 node-2 kernel: [    0.463998] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464025] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.464053] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464082] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464103] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.464128] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.464153] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464182] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464206] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464230] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464254] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464278] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464304] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464327] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464352] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464378] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464400] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464422] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464445] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.464468] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464490] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.464512] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464534] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464560] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  7 20:56:19 node-2 kernel: [    0.464592] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464618] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464646] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464673] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464698] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464725] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464752] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464779] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464803] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464829] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464855] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464881] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464907] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464933] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464959] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.464987] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465012] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465038] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465068] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465095] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465121] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465146] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465171] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465197] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465224] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465250] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465279] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465304] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465326] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465351] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465375] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465404] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.465430] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.466673] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  7 20:56:19 node-2 kernel: [    0.466676] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  7 20:56:19 node-2 kernel: [    0.467796] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  7 20:56:19 node-2 kernel: [    0.468310] PCI host bridge to bus 0000:00
Nov  7 20:56:19 node-2 kernel: [    0.468312] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  7 20:56:19 node-2 kernel: [    0.468314] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  7 20:56:19 node-2 kernel: [    0.468315] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  7 20:56:19 node-2 kernel: [    0.468317] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov  7 20:56:19 node-2 kernel: [    0.468318] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov  7 20:56:19 node-2 kernel: [    0.468319] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  7 20:56:19 node-2 kernel: [    0.468321] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  7 20:56:19 node-2 kernel: [    0.468327] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  7 20:56:19 node-2 kernel: [    0.468409] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.468440] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.468481] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  7 20:56:19 node-2 kernel: [    0.468500] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.468530] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.468570] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  7 20:56:19 node-2 kernel: [    0.468588] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.468617] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.468659] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  7 20:56:19 node-2 kernel: [    0.468674] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.468744] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.468821] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.468896] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  7 20:56:19 node-2 kernel: [    0.468901] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov  7 20:56:19 node-2 kernel: [    0.468985] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  7 20:56:19 node-2 kernel: [    0.469133] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  7 20:56:19 node-2 kernel: [    0.469151] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov  7 20:56:19 node-2 kernel: [    0.469229] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.469283] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov  7 20:56:19 node-2 kernel: [    0.469305] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.469361] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.469404] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov  7 20:56:19 node-2 kernel: [    0.469431] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.469487] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.469530] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov  7 20:56:19 node-2 kernel: [    0.469554] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  7 20:56:19 node-2 kernel: [    0.469572] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov  7 20:56:19 node-2 kernel: [    0.469649] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.469699] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov  7 20:56:19 node-2 kernel: [    0.469725] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  7 20:56:19 node-2 kernel: [    0.469971] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov  7 20:56:19 node-2 kernel: [    0.469977] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov  7 20:56:19 node-2 kernel: [    0.469983] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.469989] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.469996] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov  7 20:56:19 node-2 kernel: [    0.470027] pci 0000:01:00.0: supports D1 D2
Nov  7 20:56:19 node-2 kernel: [    0.480180] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  7 20:56:19 node-2 kernel: [    0.480186] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  7 20:56:19 node-2 kernel: [    0.480191] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  7 20:56:19 node-2 kernel: [    0.480439] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.480472] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov  7 20:56:19 node-2 kernel: [    0.488195] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  7 20:56:19 node-2 kernel: [    0.488197] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.488199] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  7 20:56:19 node-2 kernel: [    0.488254] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.488322] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.488398] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.488443] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  7 20:56:19 node-2 kernel: [    0.488446] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.488448] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  7 20:56:19 node-2 kernel: [    0.488500] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.488627] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.488680] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  7 20:56:19 node-2 kernel: [    0.488682] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.488684] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.488733] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.488852] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.488897] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.489020] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.489057] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.489177] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.489213] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov  7 20:56:19 node-2 kernel: [    0.489332] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov  7 20:56:19 node-2 kernel: [    0.489374] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  7 20:56:19 node-2 kernel: [    0.489377] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.489379] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.489436] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov  7 20:56:19 node-2 kernel: [    0.489500] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.489552] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.489593] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov  7 20:56:19 node-2 kernel: [    0.489675] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov  7 20:56:19 node-2 kernel: [    0.489780] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  7 20:56:19 node-2 kernel: [    0.489783] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.489785] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.489841] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov  7 20:56:19 node-2 kernel: [    0.489918] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.489967] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.490182] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  7 20:56:19 node-2 kernel: [    0.490185] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  7 20:56:19 node-2 kernel: [    0.490251] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov  7 20:56:19 node-2 kernel: [    0.490304] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.490353] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.490564] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  7 20:56:19 node-2 kernel: [    0.490568] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  7 20:56:19 node-2 kernel: [    0.490627] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov  7 20:56:19 node-2 kernel: [    0.490687] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.490739] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov  7 20:56:19 node-2 kernel: [    0.490984] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  7 20:56:19 node-2 kernel: [    0.490988] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  7 20:56:19 node-2 kernel: [    0.491165] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  7 20:56:19 node-2 kernel: [    0.491204] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  7 20:56:19 node-2 kernel: [    0.491279] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov  7 20:56:19 node-2 kernel: [    0.491298] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov  7 20:56:19 node-2 kernel: [    0.491311] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov  7 20:56:19 node-2 kernel: [    0.491324] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov  7 20:56:19 node-2 kernel: [    0.491374] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov  7 20:56:19 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  7 20:56:19 node-2 kernel: [    0.496184] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  7 20:56:19 node-2 kernel: [    0.496189] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  7 20:56:19 node-2 kernel: [    0.496221] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  7 20:56:19 node-2 kernel: [    0.496708] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  7 20:56:19 node-2 kernel: [    0.496711] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  7 20:56:19 node-2 kernel: [    0.496837] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  7 20:56:19 node-2 kernel: [    0.496943] PCI host bridge to bus 0000:80
Nov  7 20:56:19 node-2 kernel: [    0.496945] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  7 20:56:19 node-2 kernel: [    0.496947] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov  7 20:56:19 node-2 kernel: [    0.496948] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  7 20:56:19 node-2 kernel: [    0.496956] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.497020] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.497087] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  7 20:56:19 node-2 kernel: [    0.497150] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  7 20:56:19 node-2 kernel: [    0.497155] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov  7 20:56:19 node-2 kernel: [    0.497228] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  7 20:56:19 node-2 kernel: [    0.497528] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov  7 20:56:19 node-2 kernel: [    0.497560] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov  7 20:56:19 node-2 kernel: [    0.497589] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov  7 20:56:19 node-2 kernel: [    0.497618] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov  7 20:56:19 node-2 kernel: [    0.497648] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  7 20:56:19 node-2 kernel: [    0.497678] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  7 20:56:19 node-2 kernel: [    0.497707] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  7 20:56:19 node-2 kernel: [    0.497737] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  7 20:56:19 node-2 kernel: [    0.497823] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov  7 20:56:19 node-2 kernel: [    0.497827] ACPI: \_SB_.UNC1: notify handler is installed
Nov  7 20:56:19 node-2 kernel: [    0.497828] ACPI: \_SB_.UNC0: notify handler is installed
Nov  7 20:56:19 node-2 kernel: [    0.497843] ACPI: \_SB_.PCI0: notify handler is installed
Nov  7 20:56:19 node-2 kernel: [    0.497896] ACPI: \_SB_.PCI1: notify handler is installed
Nov  7 20:56:19 node-2 kernel: [    0.497974] Found 4 acpi root devices
Nov  7 20:56:19 node-2 kernel: [    0.498083] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov  7 20:56:19 node-2 kernel: [    0.498085] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov  7 20:56:19 node-2 kernel: [    0.498087] vgaarb: loaded
Nov  7 20:56:19 node-2 kernel: [    0.498088] vgaarb: bridge control possible 0000:0c:00.0
Nov  7 20:56:19 node-2 kernel: [    0.498211] SCSI subsystem initialized
Nov  7 20:56:19 node-2 kernel: [    0.498281] libata version 3.00 loaded.
Nov  7 20:56:19 node-2 kernel: [    0.498297] ACPI: bus type USB registered
Nov  7 20:56:19 node-2 kernel: [    0.498307] usbcore: registered new interface driver usbfs
Nov  7 20:56:19 node-2 kernel: [    0.498312] usbcore: registered new interface driver hub
Nov  7 20:56:19 node-2 kernel: [    0.498334] usbcore: registered new device driver usb
Nov  7 20:56:19 node-2 kernel: [    0.498514] PCI: Using ACPI for IRQ routing
Nov  7 20:56:19 node-2 kernel: [    0.502115] PCI: pci_cache_line_size set to 64 bytes
Nov  7 20:56:19 node-2 kernel: [    0.502316] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov  7 20:56:19 node-2 kernel: [    0.502317] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Nov  7 20:56:19 node-2 kernel: [    0.502318] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov  7 20:56:19 node-2 kernel: [    0.502383] NetLabel: Initializing
Nov  7 20:56:19 node-2 kernel: [    0.502385] NetLabel:  domain hash size = 128
Nov  7 20:56:19 node-2 kernel: [    0.502386] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  7 20:56:19 node-2 kernel: [    0.502396] NetLabel:  unlabeled traffic allowed by default
Nov  7 20:56:19 node-2 kernel: [    0.502451] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  7 20:56:19 node-2 kernel: [    0.502456] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  7 20:56:19 node-2 kernel: [    0.504513] Switched to clocksource hpet
Nov  7 20:56:19 node-2 kernel: [    0.508374] AppArmor: AppArmor Filesystem Enabled
Nov  7 20:56:19 node-2 kernel: [    0.508388] pnp: PnP ACPI init
Nov  7 20:56:19 node-2 kernel: [    0.508395] ACPI: bus type PNP registered
Nov  7 20:56:19 node-2 kernel: [    0.508517] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508526] pnp 00:01: [dma 4]
Nov  7 20:56:19 node-2 kernel: [    0.508537] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508563] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508583] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508600] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508633] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508685] system 00:06: [io  0x0500-0x057f] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508687] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov  7 20:56:19 node-2 kernel: [    0.508689] system 00:06: [io  0x0580-0x059f] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508691] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508692] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508697] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508699] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov  7 20:56:19 node-2 kernel: [    0.508701] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508703] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508704] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508706] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508707] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508709] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  7 20:56:19 node-2 kernel: [    0.508711] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508794] pnp 00:07: [dma 0 disabled]
Nov  7 20:56:19 node-2 kernel: [    0.508822] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508897] pnp 00:08: [dma 0 disabled]
Nov  7 20:56:19 node-2 kernel: [    0.508929] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  7 20:56:19 node-2 kernel: [    0.508979] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  7 20:56:19 node-2 kernel: [    0.509323] pnp: PnP ACPI: found 10 devices
Nov  7 20:56:19 node-2 kernel: [    0.509325] ACPI: bus type PNP unregistered
Nov  7 20:56:19 node-2 kernel: [    0.515641] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  7 20:56:19 node-2 kernel: [    0.515644] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  7 20:56:19 node-2 kernel: [    0.515647] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  7 20:56:19 node-2 kernel: [    0.515651] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  7 20:56:19 node-2 kernel: [    0.515653] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515671] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515700] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  7 20:56:19 node-2 kernel: [    0.515715] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515744] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  7 20:56:19 node-2 kernel: [    0.515758] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  7 20:56:19 node-2 kernel: [    0.515787] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  7 20:56:19 node-2 kernel: [    0.515802] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  7 20:56:19 node-2 kernel: [    0.515831] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  7 20:56:19 node-2 kernel: [    0.515833] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515847] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515892] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  7 20:56:19 node-2 kernel: [    0.515894] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515909] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515938] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  7 20:56:19 node-2 kernel: [    0.515939] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515942] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515946] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  7 20:56:19 node-2 kernel: [    0.515948] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515950] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515954] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  7 20:56:19 node-2 kernel: [    0.515959] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  7 20:56:19 node-2 kernel: [    0.515967] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  7 20:56:19 node-2 kernel: [    0.515970] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  7 20:56:19 node-2 kernel: [    0.515976] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  7 20:56:19 node-2 kernel: [    0.515977] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  7 20:56:19 node-2 kernel: [    0.515978] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov  7 20:56:19 node-2 kernel: [    0.515979] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov  7 20:56:19 node-2 kernel: [    0.515980] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  7 20:56:19 node-2 kernel: [    0.515981] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov  7 20:56:19 node-2 kernel: [    0.515982] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov  7 20:56:19 node-2 kernel: [    0.515983] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov  7 20:56:19 node-2 kernel: [    0.515984] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515985] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515986] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515986] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515987] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515988] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515989] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515990] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515991] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov  7 20:56:19 node-2 kernel: [    0.515992] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515993] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov  7 20:56:19 node-2 kernel: [    0.515994] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov  7 20:56:19 node-2 kernel: [    0.515995] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov  7 20:56:19 node-2 kernel: [    0.515996] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov  7 20:56:19 node-2 kernel: [    0.515998] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov  7 20:56:19 node-2 kernel: [    0.515999] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  7 20:56:19 node-2 kernel: [    0.516040] NET: Registered protocol family 2
Nov  7 20:56:19 node-2 kernel: [    0.516302] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.516633] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.516775] TCP: Hash tables configured (established 262144 bind 65536)
Nov  7 20:56:19 node-2 kernel: [    0.516818] TCP: reno registered
Nov  7 20:56:19 node-2 kernel: [    0.516847] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.516943] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.517090] NET: Registered protocol family 1
Nov  7 20:56:19 node-2 kernel: [    0.552612] pci 0000:0c:00.0: Video device with shadowed ROM
Nov  7 20:56:19 node-2 kernel: [    0.552626] PCI: CLS 64 bytes, default 64
Nov  7 20:56:19 node-2 kernel: [    0.552700] Trying to unpack rootfs image as initramfs...
Nov  7 20:56:19 node-2 kernel: [    0.772209] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Nov  7 20:56:19 node-2 kernel: [    0.772243] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  7 20:56:19 node-2 kernel: [    0.772245] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Nov  7 20:56:19 node-2 kernel: [    0.772656] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772662] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772667] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772673] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772685] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772701] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772716] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772732] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772744] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772753] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772759] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772765] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772774] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772787] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772799] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772813] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov  7 20:56:19 node-2 kernel: [    0.772921] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  7 20:56:19 node-2 kernel: [    0.772927] Scanning for low memory corruption every 60 seconds
Nov  7 20:56:19 node-2 kernel: [    0.773351] Initialise system trusted keyring
Nov  7 20:56:19 node-2 kernel: [    0.773404] audit: initializing netlink socket (disabled)
Nov  7 20:56:19 node-2 kernel: [    0.773420] type=2000 audit(1478552140.728:1): initialized
Nov  7 20:56:19 node-2 kernel: [    0.791168] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  7 20:56:19 node-2 kernel: [    0.792706] zbud: loaded
Nov  7 20:56:19 node-2 kernel: [    0.792833] VFS: Disk quotas dquot_6.5.2
Nov  7 20:56:19 node-2 kernel: [    0.792869] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  7 20:56:19 node-2 kernel: [    0.793243] fuse init (API version 7.22)
Nov  7 20:56:19 node-2 kernel: [    0.793302] msgmni has been set to 32768
Nov  7 20:56:19 node-2 kernel: [    0.793349] Key type big_key registered
Nov  7 20:56:19 node-2 kernel: [    0.793865] Key type asymmetric registered
Nov  7 20:56:19 node-2 kernel: [    0.793867] Asymmetric key parser 'x509' registered
Nov  7 20:56:19 node-2 kernel: [    0.793889] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  7 20:56:19 node-2 kernel: [    0.793964] io scheduler noop registered
Nov  7 20:56:19 node-2 kernel: [    0.793966] io scheduler deadline registered (default)
Nov  7 20:56:19 node-2 kernel: [    0.793985] io scheduler cfq registered
Nov  7 20:56:19 node-2 kernel: [    0.794528] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    0.794691] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    0.794808] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    0.794918] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    0.795045] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    0.795136] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    0.795551] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov  7 20:56:19 node-2 kernel: [    0.795577] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov  7 20:56:19 node-2 kernel: [    0.795593] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov  7 20:56:19 node-2 kernel: [    0.795602] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795605] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795607] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  7 20:56:19 node-2 kernel: [    0.795612] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795614] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795615] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795617] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795618] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795620] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795621] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795623] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795624] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795626] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795627] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795629] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795631] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  7 20:56:19 node-2 kernel: [    0.795636] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795638] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  7 20:56:19 node-2 kernel: [    0.795659] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795662] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  7 20:56:19 node-2 kernel: [    0.795673] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795675] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov  7 20:56:19 node-2 kernel: [    0.795678] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  7 20:56:19 node-2 kernel: [    0.795717] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  7 20:56:19 node-2 kernel: [    0.795723] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  7 20:56:19 node-2 kernel: [    0.795727] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  7 20:56:19 node-2 kernel: [    0.795736] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  7 20:56:19 node-2 kernel: [    0.795777] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  7 20:56:19 node-2 kernel: [    0.795779] vesafb: scrolling: redraw
Nov  7 20:56:19 node-2 kernel: [    0.795780] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  7 20:56:19 node-2 kernel: [    0.816466] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov  7 20:56:19 node-2 kernel: [    0.825070] Console: switching to colour frame buffer device 80x30
Nov  7 20:56:19 node-2 kernel: [    0.833750] fb0: VESA VGA frame buffer device
Nov  7 20:56:19 node-2 kernel: [    0.833948] intel_idle: MWAIT substates: 0x2120
Nov  7 20:56:19 node-2 kernel: [    0.833949] intel_idle: v0.4 model 0x3F
Nov  7 20:56:19 node-2 kernel: [    0.833950] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  7 20:56:19 node-2 kernel: [    0.834180] ipmi message handler version 39.2
Nov  7 20:56:19 node-2 kernel: [    0.834457] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov  7 20:56:19 node-2 kernel: [    0.834893] ACPI: AC Adapter [P111] (on-line)
Nov  7 20:56:19 node-2 kernel: [    0.840117] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov  7 20:56:19 node-2 kernel: [    0.851117] ACPI: Power Button [PWRB]
Nov  7 20:56:19 node-2 kernel: [    0.856878] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov  7 20:56:19 node-2 kernel: [    0.868488] ACPI: Power Button [PWRF]
Nov  7 20:56:19 node-2 kernel: [    0.886010] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  7 20:56:19 node-2 kernel: [    0.897707] pstore: Registered erst as persistent store backend
Nov  7 20:56:19 node-2 kernel: [    0.903975] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov  7 20:56:19 node-2 kernel: [    0.916007] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  7 20:56:19 node-2 kernel: [    0.942759] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  7 20:56:19 node-2 kernel: [    0.976042] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  7 20:56:19 node-2 kernel: [    0.990061] Linux agpgart interface v0.103
Nov  7 20:56:19 node-2 kernel: [    0.997733] brd: module loaded
Nov  7 20:56:19 node-2 kernel: [    1.004761] loop: module loaded
Nov  7 20:56:19 node-2 kernel: [    1.011469] libphy: Fixed MDIO Bus: probed
Nov  7 20:56:19 node-2 kernel: [    1.017930] tun: Universal TUN/TAP device driver, 1.6
Nov  7 20:56:19 node-2 kernel: [    1.024395] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  7 20:56:19 node-2 kernel: [    1.030901] PPP generic driver version 2.4.2
Nov  7 20:56:19 node-2 kernel: [    1.037291] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  7 20:56:19 node-2 kernel: [    1.043725] ehci-pci: EHCI PCI platform driver
Nov  7 20:56:19 node-2 kernel: [    1.050242] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  7 20:56:19 node-2 kernel: [    1.056657] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  7 20:56:19 node-2 kernel: [    1.069258] ehci-pci 0000:00:1a.0: debug port 2
Nov  7 20:56:19 node-2 kernel: [    1.079536] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  7 20:56:19 node-2 kernel: [    1.079554] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov  7 20:56:19 node-2 kernel: [    1.096015] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  7 20:56:19 node-2 kernel: [    1.102089] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  7 20:56:19 node-2 kernel: [    1.108258] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  7 20:56:19 node-2 kernel: [    1.120156] usb usb1: Product: EHCI Host Controller
Nov  7 20:56:19 node-2 kernel: [    1.126193] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  7 20:56:19 node-2 kernel: [    1.132248] usb usb1: SerialNumber: 0000:00:1a.0
Nov  7 20:56:19 node-2 kernel: [    1.138204] hub 1-0:1.0: USB hub found
Nov  7 20:56:19 node-2 kernel: [    1.143978] hub 1-0:1.0: 2 ports detected
Nov  7 20:56:19 node-2 kernel: [    1.149814] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  7 20:56:19 node-2 kernel: [    1.155393] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  7 20:56:19 node-2 kernel: [    1.166284] ehci-pci 0000:00:1d.0: debug port 2
Nov  7 20:56:19 node-2 kernel: [    1.175579] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  7 20:56:19 node-2 kernel: [    1.175586] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov  7 20:56:19 node-2 kernel: [    1.191933] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  7 20:56:19 node-2 kernel: [    1.197133] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  7 20:56:19 node-2 kernel: [    1.202441] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  7 20:56:19 node-2 kernel: [    1.213016] usb usb2: Product: EHCI Host Controller
Nov  7 20:56:19 node-2 kernel: [    1.218500] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  7 20:56:19 node-2 kernel: [    1.224046] usb usb2: SerialNumber: 0000:00:1d.0
Nov  7 20:56:19 node-2 kernel: [    1.229562] hub 2-0:1.0: USB hub found
Nov  7 20:56:19 node-2 kernel: [    1.234910] hub 2-0:1.0: 2 ports detected
Nov  7 20:56:19 node-2 kernel: [    1.240219] ehci-platform: EHCI generic platform driver
Nov  7 20:56:19 node-2 kernel: [    1.245458] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  7 20:56:19 node-2 kernel: [    1.250780] ohci-pci: OHCI PCI platform driver
Nov  7 20:56:19 node-2 kernel: [    1.256086] ohci-platform: OHCI generic platform driver
Nov  7 20:56:19 node-2 kernel: [    1.261286] uhci_hcd: USB Universal Host Controller Interface driver
Nov  7 20:56:19 node-2 kernel: [    1.266627] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  7 20:56:19 node-2 kernel: [    1.459712] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  7 20:56:19 node-2 kernel: [    1.771466] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov  7 20:56:19 node-2 kernel: [    1.787820] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  7 20:56:19 node-2 kernel: [    1.793431] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  7 20:56:19 node-2 kernel: [    1.799212] hub 1-1:1.0: USB hub found
Nov  7 20:56:19 node-2 kernel: [    1.804806] hub 1-1:1.0: 6 ports detected
Nov  7 20:56:19 node-2 kernel: [    1.919340] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  7 20:56:19 node-2 kernel: [    2.305201] i8042: No controller found
Nov  7 20:56:19 node-2 kernel: [    2.310741] mousedev: PS/2 mouse device common for all mice
Nov  7 20:56:19 node-2 kernel: [    2.316487] rtc_cmos 00:02: RTC can wake from S4
Nov  7 20:56:19 node-2 kernel: [    2.319816] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  7 20:56:19 node-2 kernel: [    2.319817] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  7 20:56:19 node-2 kernel: [    2.320328] hub 2-1:1.0: USB hub found
Nov  7 20:56:19 node-2 kernel: [    2.320558] hub 2-1:1.0: 8 ports detected
Nov  7 20:56:19 node-2 kernel: [    2.344909] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  7 20:56:19 node-2 kernel: [    2.350663] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  7 20:56:19 node-2 kernel: [    2.361996] device-mapper: uevent: version 1.0.3
Nov  7 20:56:19 node-2 kernel: [    2.367717] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  7 20:56:19 node-2 kernel: [    2.379111] ledtrig-cpu: registered to indicate activity on CPUs
Nov  7 20:56:19 node-2 kernel: [    2.385107] TCP: cubic registered
Nov  7 20:56:19 node-2 kernel: [    2.390976] NET: Registered protocol family 10
Nov  7 20:56:19 node-2 kernel: [    2.397041] NET: Registered protocol family 17
Nov  7 20:56:19 node-2 kernel: [    2.402816] Key type dns_resolver registered
Nov  7 20:56:19 node-2 kernel: [    2.408893] Loading compiled-in X.509 certificates
Nov  7 20:56:19 node-2 kernel: [    2.415124] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  7 20:56:19 node-2 kernel: [    2.426782] registered taskstats version 1
Nov  7 20:56:19 node-2 kernel: [    2.434844] Key type trusted registered
Nov  7 20:56:19 node-2 kernel: [    2.442488] Key type encrypted registered
Nov  7 20:56:19 node-2 kernel: [    2.448034] AppArmor: AppArmor sha1 policy hashing enabled
Nov  7 20:56:19 node-2 kernel: [    2.453591] IMA: No TPM chip found, activating TPM-bypass!
Nov  7 20:56:19 node-2 kernel: [    2.459704] regulator-dummy: disabling
Nov  7 20:56:19 node-2 kernel: [    2.465214]   Magic number: 8:569:952
Nov  7 20:56:19 node-2 kernel: [    2.470706] tty tty9: hash matches
Nov  7 20:56:19 node-2 kernel: [    2.476223] processor cpu7: hash matches
Nov  7 20:56:19 node-2 kernel: [    2.481526] memory memory5: hash matches
Nov  7 20:56:19 node-2 kernel: [    2.486780] rtc_cmos 00:02: setting system clock to 2016-11-07 20:55:43 UTC (1478552143)
Nov  7 20:56:19 node-2 kernel: [    2.498821] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  7 20:56:19 node-2 kernel: [    2.504242] EDD information not available.
Nov  7 20:56:19 node-2 kernel: [    2.509611] PM: Hibernation image not present or could not be loaded.
Nov  7 20:56:19 node-2 kernel: [    2.510481] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  7 20:56:19 node-2 kernel: [    2.521549] Write protecting the kernel read-only data: 12288k
Nov  7 20:56:19 node-2 kernel: [    2.527692] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  7 20:56:19 node-2 kernel: [    2.540015] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  7 20:56:19 node-2 kernel: [    2.571258] device-mapper: multipath: version 1.6.0 loaded
Nov  7 20:56:19 node-2 kernel: [    2.578816] systemd-udevd[216]: starting version 204
Nov  7 20:56:19 node-2 kernel: [    2.601932] md: linear personality registered for level -1
Nov  7 20:56:19 node-2 kernel: [    2.610943] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov  7 20:56:19 node-2 kernel: [    2.622377] md: multipath personality registered for level -4
Nov  7 20:56:19 node-2 kernel: [    2.630237] md: raid0 personality registered for level 0
Nov  7 20:56:19 node-2 kernel: [    2.638201] md: raid1 personality registered for level 1
Nov  7 20:56:19 node-2 kernel: [    2.646546] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov  7 20:56:19 node-2 kernel: [    2.652671] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov  7 20:56:19 node-2 kernel: [    2.658842] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov  7 20:56:19 node-2 kernel: [    2.660265] megasas: FW now in Ready state
Nov  7 20:56:19 node-2 kernel: [    2.660574] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.660684] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.660809] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.660972] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661158] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661296] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661375] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661447] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661543] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661643] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661762] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.661955] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.662092] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.662247] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.662377] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.662534] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.663273] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov  7 20:56:19 node-2 kernel: [    2.691971] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Nov  7 20:56:19 node-2 kernel: [    2.705046] 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
Nov  7 20:56:19 node-2 kernel: [    2.710729] raid6: sse2x1   11269 MB/s
Nov  7 20:56:19 node-2 kernel: [    2.725635] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  7 20:56:19 node-2 kernel: [    2.732704] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.734834] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.734842] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.734847] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.734897] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  7 20:56:19 node-2 kernel: [    2.746615] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov  7 20:56:19 node-2 kernel: [    2.746801] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  7 20:56:19 node-2 kernel: [    2.746808] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov  7 20:56:19 node-2 kernel: [    2.746808] usb 2-1.4: Manufacturer: Avocent
Nov  7 20:56:19 node-2 kernel: [    2.746809] usb 2-1.4: SerialNumber: 20111102-00000001
Nov  7 20:56:19 node-2 kernel: [    2.778771] raid6: sse2x2   11927 MB/s
Nov  7 20:56:19 node-2 kernel: [    2.846547] raid6: sse2x4   10026 MB/s
Nov  7 20:56:19 node-2 kernel: [    2.918475] raid6: avx2x1   14936 MB/s
Nov  7 20:56:19 node-2 kernel: [    2.990417] raid6: avx2x2   18861 MB/s
Nov  7 20:56:19 node-2 kernel: [    3.062351] raid6: avx2x4   21309 MB/s
Nov  7 20:56:19 node-2 kernel: [    3.067909] raid6: using algorithm avx2x4 (21309 MB/s)
Nov  7 20:56:19 node-2 kernel: [    3.073408] raid6: using avx2x2 recovery algorithm
Nov  7 20:56:19 node-2 kernel: [    3.078806] Switched to clocksource tsc
Nov  7 20:56:19 node-2 kernel: [    3.078807] megasas:IOC Init cmd success
Nov  7 20:56:19 node-2 kernel: [    3.089633] hidraw: raw HID events driver (C) Jiri Kosina
Nov  7 20:56:19 node-2 kernel: [    3.090165] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Nov  7 20:56:19 node-2 kernel: [    3.090166] 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
Nov  7 20:56:19 node-2 kernel: [    3.090167] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov  7 20:56:19 node-2 kernel: [    3.090234] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.090268] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.090303] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.090338] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.090376] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.090411] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.090507] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.101108] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Nov  7 20:56:19 node-2 kernel: [    3.101110] 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
Nov  7 20:56:19 node-2 kernel: [    3.101111] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  7 20:56:19 node-2 kernel: [    3.101171] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.101212] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.101248] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.101284] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.101367] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.102347] megasas: INIT adapter done
Nov  7 20:56:19 node-2 kernel: [    3.108336] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Nov  7 20:56:19 node-2 kernel: [    3.108337] 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
Nov  7 20:56:19 node-2 kernel: [    3.108338] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  7 20:56:19 node-2 kernel: [    3.108396] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.108431] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.108458] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.108490] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.108573] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  7 20:56:19 node-2 kernel: [    3.174268] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov  7 20:56:19 node-2 kernel: [    3.174595] scsi0 : LSI SAS based MegaRAID driver
Nov  7 20:56:19 node-2 kernel: [    3.181850] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  7 20:56:19 node-2 kernel: [    3.192963] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  7 20:56:19 node-2 kernel: [    3.197102] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov  7 20:56:19 node-2 kernel: [    3.197114] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov  7 20:56:19 node-2 kernel: [    3.197404] sd 0:2:0:0: [sda] Write Protect is off
Nov  7 20:56:19 node-2 kernel: [    3.197405] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov  7 20:56:19 node-2 kernel: [    3.197474] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov  7 20:56:19 node-2 kernel: [    3.219540]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov  7 20:56:19 node-2 kernel: [    3.221020] sd 0:2:0:0: [sda] Attached SCSI disk
Nov  7 20:56:19 node-2 kernel: [    3.309549] xor: automatically using best checksumming function:
Nov  7 20:56:19 node-2 kernel: [    3.318843] usbcore: registered new interface driver usbhid
Nov  7 20:56:19 node-2 kernel: [    3.325388] usbhid: USB HID core driver
Nov  7 20:56:19 node-2 kernel: [    3.332763] 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
Nov  7 20:56:19 node-2 kernel: [    3.345760] 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
Nov  7 20:56:19 node-2 kernel: [    3.354087]    avx       : 35730.000 MB/sec
Nov  7 20:56:19 node-2 kernel: [    3.366160] 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
Nov  7 20:56:19 node-2 kernel: [    3.379968] async_tx: api initialized (async)
Nov  7 20:56:19 node-2 kernel: [    3.380136] 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
Nov  7 20:56:19 node-2 kernel: [    3.380194] 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
Nov  7 20:56:19 node-2 kernel: [    3.380566] 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
Nov  7 20:56:19 node-2 kernel: [    3.432759] md: raid6 personality registered for level 6
Nov  7 20:56:19 node-2 kernel: [    3.440002] md: raid5 personality registered for level 5
Nov  7 20:56:19 node-2 kernel: [    3.447068] md: raid4 personality registered for level 4
Nov  7 20:56:19 node-2 kernel: [    3.456900] md: raid10 personality registered for level 10
Nov  7 20:56:19 node-2 kernel: [    3.513350] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Nov  7 20:56:19 node-2 kernel: [    3.528340] random: lvm urandom read with 36 bits of entropy available
Nov  7 20:56:19 node-2 kernel: [    3.669574] bio: create slab <bio-1> at 1
Nov  7 20:56:19 node-2 kernel: [    4.537352] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Nov  7 20:56:19 node-2 kernel: [    4.905300] random: nonblocking pool is initialized
Nov  7 20:56:19 node-2 kernel: [    5.153215] init: plymouth-upstart-bridge main process (574) terminated with status 1
Nov  7 20:56:19 node-2 kernel: [    5.165954] init: plymouth-upstart-bridge main process ended, respawning
Nov  7 20:56:19 node-2 kernel: [    5.282117] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Nov  7 20:56:19 node-2 kernel: [    5.313570] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov  7 20:56:19 node-2 kernel: [    5.481758] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  7 20:56:19 node-2 kernel: [    5.523655] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  7 20:56:19 node-2 kernel: [    5.593557] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  7 20:56:19 node-2 kernel: [    5.842747] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  7 20:56:19 node-2 kernel: [    5.879555] XFS (dm-1): Mounting Filesystem
Nov  7 20:56:19 node-2 kernel: [    6.145575] XFS (dm-1): Ending clean mount
Nov  7 20:56:19 node-2 kernel: [    6.210333] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  7 20:56:19 node-2 kernel: [    6.242946] XFS (dm-2): Mounting Filesystem
Nov  7 20:56:19 node-2 kernel: [    6.326182] XFS (dm-2): Ending clean mount
Nov  7 20:56:19 node-2 kernel: [    6.465892] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Nov  7 20:56:19 node-2 kernel: [    8.591050] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  7 20:56:19 node-2 kernel: [    8.616359] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  7 20:56:19 node-2 kernel: [    8.817921] systemd-udevd[805]: starting version 204
Nov  7 20:56:19 node-2 kernel: [    9.095401] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov  7 20:56:19 node-2 kernel: [    9.095408] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  7 20:56:19 node-2 kernel: [    9.095412] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov  7 20:56:19 node-2 kernel: [    9.095415] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  7 20:56:19 node-2 kernel: [    9.095457] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov  7 20:56:19 node-2 kernel: [    9.099461] power_meter ACPI000D:00: Found ACPI power meter.
Nov  7 20:56:19 node-2 kernel: [    9.099470] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  7 20:56:19 node-2 kernel: [    9.106439] IPMI System Interface driver.
Nov  7 20:56:19 node-2 kernel: [    9.106499] ipmi_si: probing via ACPI
Nov  7 20:56:19 node-2 kernel: [    9.106511] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov  7 20:56:19 node-2 kernel: [    9.106512] ipmi_si: Adding ACPI-specified kcs state machine
Nov  7 20:56:19 node-2 kernel: [    9.106533] ipmi_si: probing via SMBIOS
Nov  7 20:56:19 node-2 kernel: [    9.106534] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  7 20:56:19 node-2 kernel: [    9.106535] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  7 20:56:19 node-2 kernel: [    9.106537] ipmi_si: probing via SPMI
Nov  7 20:56:19 node-2 kernel: [    9.106538] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov  7 20:56:19 node-2 kernel: [    9.106539] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov  7 20:56:19 node-2 kernel: [    9.106541] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  7 20:56:19 node-2 kernel: [    9.107435] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  7 20:56:19 node-2 kernel: [    9.108318] wmi: Mapper loaded
Nov  7 20:56:19 node-2 kernel: [    9.197626] systemd-udevd[841]: renamed network interface eth0 to enp6s0
Nov  7 20:56:19 node-2 kernel: [    9.213500] systemd-udevd[842]: renamed network interface eth1 to enp7s0
Nov  7 20:56:19 node-2 kernel: [    9.241716] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov  7 20:56:19 node-2 kernel: [    9.241723] ipmi_si 00:09: IPMI kcs interface initialized
Nov  7 20:56:19 node-2 kernel: [    9.245477] systemd-udevd[846]: renamed network interface eth3 to enp9s0
Nov  7 20:56:19 node-2 kernel: [    9.273520] systemd-udevd[844]: renamed network interface eth2 to enp8s0
Nov  7 20:56:19 node-2 kernel: [    9.518519] type=1400 audit(1478552150.535:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1013 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.518700] type=1400 audit(1478552150.535:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1013 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.518706] type=1400 audit(1478552150.535:4): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1012 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.518852] type=1400 audit(1478552150.535:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1013 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.518869] type=1400 audit(1478552150.535:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1012 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.518990] type=1400 audit(1478552150.535:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1012 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.527495] type=1400 audit(1478552150.543:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1027 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.527728] type=1400 audit(1478552150.543:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1027 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.527924] type=1400 audit(1478552150.543:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1027 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [    9.532400] type=1400 audit(1478552150.547:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=996 comm="apparmor_parser"
Nov  7 20:56:19 node-2 kernel: [   10.151021] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  7 20:56:19 node-2 kernel: [   10.151762] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  7 20:56:19 node-2 kernel: [   10.359288] enic 0000:06:00.0 enp6s0: Link UP
Nov  7 20:56:19 node-2 kernel: [   10.360324] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov  7 20:56:19 node-2 kernel: [   10.360338] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov  7 20:56:19 node-2 kernel: [   20.397894] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  7 20:56:20 node-2 failsafe: Failsafe of 120 seconds reached.
Nov  7 20:56:20 node-2 kernel: [   39.205608] init: failsafe main process (8458) killed by TERM signal
Nov  7 20:56:20 node-2 dbus[8508]: [system] AppArmor D-Bus mediation is enabled
Nov  7 20:56:20 node-2 kernel: [   39.392023] audit_printk_skb: 30 callbacks suppressed
Nov  7 20:56:20 node-2 kernel: [   39.392024] type=1400 audit(1478552180.455:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8584 comm="apparmor_parser"
Nov  7 20:56:20 node-2 kernel: [   39.392028] type=1400 audit(1478552180.455:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8584 comm="apparmor_parser"
Nov  7 20:56:20 node-2 kernel: [   39.392030] type=1400 audit(1478552180.455:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8584 comm="apparmor_parser"
Nov  7 20:56:20 node-2 kernel: [   39.392255] type=1400 audit(1478552180.455:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8584 comm="apparmor_parser"
Nov  7 20:56:20 node-2 kernel: [   39.392256] type=1400 audit(1478552180.455:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8584 comm="apparmor_parser"
Nov  7 20:56:20 node-2 kernel: [   39.392373] type=1400 audit(1478552180.455:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8584 comm="apparmor_parser"
Nov  7 20:56:20 node-2 kernel: [   39.392641] type=1400 audit(1478552180.455:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8585 comm="apparmor_parser"
Nov  7 20:56:20 node-2 kernel: [   39.468830] type=1400 audit(1478552180.531:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8587 comm="apparmor_parser"
Nov  7 20:56:20 node-2 cron[8617]: (CRON) INFO (pidfile fd = 3)
Nov  7 20:56:20 node-2 anacron[8651]: Anacron 2.3 started on 2016-11-07
Nov  7 20:56:20 node-2 cron[8654]: (CRON) STARTUP (fork ok)
Nov  7 20:56:20 node-2 anacron[8651]: Will run job `cron.daily' in 5 min.
Nov  7 20:56:20 node-2 anacron[8651]: Will run job `cron.weekly' in 10 min.
Nov  7 20:56:20 node-2 anacron[8651]: Will run job `cron.monthly' in 15 min.
Nov  7 20:56:20 node-2 anacron[8651]: Jobs will be executed sequentially
Nov  7 20:56:20 node-2 multipathd: path checkers start up
Nov  7 20:56:20 node-2 cron[8654]: (CRON) INFO (Running @reboot jobs)
Nov  7 20:56:21 node-2 postfix/master[8796]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  7 20:56:24 node-2 puppet-agent[8981]: Reopening log files
Nov  7 20:56:25 node-2 puppet-agent[8981]: Could not request certificate: Connection refused - connect(2)
Nov  7 20:56:36 node-2 puppet-user[9060]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  7 20:56:36 node-2 puppet-user[9060]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Nov  7 20:56:38 node-2 puppet-user[9060]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  7 20:56:38 node-2 puppet-user[9060]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  7 20:56:38 node-2 puppet-user[9060]: Finished catalog run in 1.35 seconds
Nov  7 20:56:39 node-2 multipathd: uevent trigger error
Nov  7 20:56:39 node-2 puppet-user[9585]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  7 20:56:39 node-2 puppet-user[9585]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Nov  7 20:56:39 node-2 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  7 20:56:39 node-2 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  7 20:56:39 node-2 puppet-user[9585]: (/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"]'
Nov  7 20:56:39 node-2 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  7 20:56:39 node-2 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  7 20:56:40 node-2 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  7 20:56:40 node-2 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  7 20:56:40 node-2 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  7 20:56:40 node-2 puppet-user[9585]: Finished catalog run in 0.08 seconds
Nov  7 20:56:41 node-2 puppet-user[10112]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  7 20:56:41 node-2 puppet-user[10112]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Nov  7 20:56:41 node-2 puppet-user[10112]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  7 20:56:41 node-2 puppet-user[10112]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  7 20:56:41 node-2 puppet-user[10112]: Finished catalog run in 0.03 seconds
Nov  7 20:56:42 node-2 puppet-user[10572]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  7 20:56:42 node-2 puppet-user[10572]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Nov  7 20:56:43 node-2 puppet-user[10572]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  7 20:56:43 node-2 puppet-user[10572]: Finished catalog run in 0.04 seconds
Nov  7 20:56:44 node-2 puppet-user[11042]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  7 20:56:45 node-2 puppet-user[11042]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Nov  7 20:56:45 node-2 puppet-user[11042]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  7 20:56:45 node-2 kernel: [   64.147802] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  7 20:56:45 node-2 kernel: [   64.147851] 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.
Nov  7 20:56:45 node-2 puppet-user[11042]: (/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'
Nov  7 20:56:45 node-2 puppet-user[11042]: Finished catalog run in 0.06 seconds
Nov  7 20:56:46 node-2 puppet-user[11505]: (Scope(Class[main])) MODULAR: sync_time
Nov  7 20:56:46 node-2 puppet-user[11505]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Nov  7 20:56:47 node-2 ntpdate[11917]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  7 20:56:53 node-2 ntpdate[11917]: adjust time server 10.20.0.2 offset 0.001870 sec
Nov  7 20:56:53 node-2 puppet-user[11505]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  7 20:56:53 node-2 puppet-user[11505]: Finished catalog run in 6.17 seconds
Nov  7 20:56:58 node-2 puppet-user[12301]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  7 20:56:58 node-2 puppet-user[12301]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Nov  7 20:56:58 node-2 puppet-user[12301]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  7 20:56:58 node-2 puppet-user[12301]: Finished catalog run in 0.06 seconds
Nov  7 20:57:00 node-2 puppet-user[12760]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  7 20:57:00 node-2 puppet-user[12760]: Compiled catalog for node-2.domain.tld in environment production in 0.48 seconds
Nov  7 20:57:00 node-2 puppet-user[12760]: (/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
Nov  7 20:57:00 node-2 puppet-user[12760]: (/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
Nov  7 20:57:00 node-2 puppet-user[12760]: (/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
Nov  7 20:57:00 node-2 puppet-user[12760]: (/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
Nov  7 20:57:00 node-2 puppet-user[12760]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  7 20:57:00 node-2 puppet-user[12760]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov  7 20:57:00 node-2 puppet-user[12760]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  7 20:57:00 node-2 puppet-user[12760]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov  7 20:57:00 node-2 puppet-user[12760]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  7 20:57:00 node-2 puppet-user[12760]: (/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
Nov  7 20:57:00 node-2 puppet-user[12760]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  7 20:57:00 node-2 puppet-user[12760]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov  7 20:57:01 node-2 puppet-user[12760]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  7 20:57:01 node-2 puppet-user[12760]: Finished catalog run in 0.84 seconds
Nov  7 20:57:01 node-2 CRON[13247]: (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")
Nov  7 20:57:03 node-2 puppet-user[13277]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  7 20:57:03 node-2 puppet-user[13277]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Nov  7 20:57:03 node-2 kernel: [   82.578024] init: plymouth-upstart-bridge main process ended, respawning
Nov  7 20:57:03 node-2 puppet-agent[8981]: Could not run: SIGTERM
Nov  7 20:57:03 node-2 kernel: [   82.854685] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  7 20:57:04 node-2 ec2: 
Nov  7 20:57:04 node-2 ec2: #############################################################
Nov  7 20:57:04 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  7 20:57:04 node-2 ec2: 1024 8a:ab:0a:2f:e1:ca:2b:6a:df:59:d7:41:f3:cc:c1:4c  root@node-2.domain.tld (DSA)
Nov  7 20:57:04 node-2 ec2: 256 5e:b9:2c:1f:9a:2d:97:fe:da:5a:82:47:ce:19:b2:e1  root@node-2.domain.tld (ECDSA)
Nov  7 20:57:04 node-2 ec2: 256 36:c8:8d:4b:62:b0:02:f8:45:b2:cf:7c:f4:42:a9:cc  root@node-2.domain.tld (ED25519)
Nov  7 20:57:04 node-2 ec2: 2048 86:8c:a0:57:26:75:a0:5f:02:5b:ab:14:de:35:2c:b4  root@node-2.domain.tld (RSA)
Nov  7 20:57:04 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  7 20:57:04 node-2 ec2: #############################################################
Nov  7 20:57:06 node-2 puppet-user[13277]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  7 20:57:12 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  7 20:57:12 node-2 nailgun-agent: D, [2016-11-07T20:57:01.942133 #13250] DEBUG -- : Sleep for 11 seconds before sending request
Nov  7 20:57:12 node-2 nailgun-agent: I, [2016-11-07T20:57:12.957959 #13250]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  7 20:57:13 node-2 nailgun-agent: D, [2016-11-07T20:57:13.413160 #13250] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.585242 #13250] DEBUG -- : Trying to find block devices
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.585499 #13250] DEBUG -- : Found block device: sda
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.585701 #13250] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.585763 #13250] DEBUG -- : Trying to get list of physical devices
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.586099 #13250] DEBUG -- : Getting udev properties for device: sda
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.590307 #13250] 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
Nov  7 20:57:25 node-2 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78490", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.590381 #13250] DEBUG -- : Trying to find out if device sda is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.590502 #13250] DEBUG -- : Device sda removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.590549 #13250] DEBUG -- : Device sda seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.591642 #13250] DEBUG -- : Getting udev properties for device: dm-0
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.594997 #13250] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-ArfuvpUMYaNtlVExTrmYwc6aCf62jUtcVwi3oZ163gKxZXWhbPhqLkSNd3O3foKJ /dev/disk/by-uuid/cc1b2289-d4e6-437d-8359-15d1404a8e20 /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-ArfuvpUMYaNtlVExTrmYwc6aCf62jUtcVwi3oZ163gKxZXWhbPhqLkSNd3O3foKJ", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cc1b2289-d4e6-437d-8359-15d1404a8e20", "ID_FS_UUID_ENC"=>"cc1b2289-d4e6-437d-8359-15d1404a8e20", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Nov  7 20:57:25 node-2 nailgun-agent: 7688", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.595051 #13250] DEBUG -- : Trying to find out if device dm-0 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.595111 #13250] DEBUG -- : Device dm-0 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.595139 #13250] DEBUG -- : Device dm-0 seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.595169 #13250] DEBUG -- : Getting udev properties for device: dm-1
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.598690 #13250] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-F6rbJm0aKWaI21qPCtBfDHcJATTTudJXwDy2yvSySWYd7ZTn1A8EfgTq5Cmzia37 /dev/disk/by-uuid/f14d4644-8f2e-490c-8b08-891c685a3120 /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-F6rbJm0aKWaI21qPCtBfDHcJATTTudJXwDy2yvSySWYd7ZTn1A8EfgTq5Cmzia37", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f14d4644-8f2e-490c-8b08-891c685a3120", "ID_FS_UUID_ENC"=>"f14d4644-8f2e-490c-8b08-891c685a3120", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58240", "nomdmonddf"=>"1", "nom
Nov  7 20:57:25 node-2 nailgun-agent: dmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.598765 #13250] DEBUG -- : Trying to find out if device dm-1 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.598861 #13250] DEBUG -- : Device dm-1 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.598989 #13250] DEBUG -- : Device dm-1 seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.599028 #13250] DEBUG -- : Getting udev properties for device: dm-2
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.602689 #13250] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-fxgKzsUppKJz5NeirW4heWwNY7gIjjRm0teSs7qg5Mf2fiuBWF6YIiqRn4aOKC3g /dev/disk/by-uuid/56f66095-7298-4806-b9c2-c3b0de922359 /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-fxgKzsUppKJz5NeirW4heWwNY7gIjjRm0teSs7qg5Mf2fiuBWF6YIiqRn4aOKC3g", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"56f66095-7298-4806-b9c2-c3b0de922359", "ID_FS_UUID_ENC"=>"56f66095-7298-4806-b9c2-c3b0de922359", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6
Nov  7 20:57:25 node-2 nailgun-agent: 9844", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.602767 #13250] DEBUG -- : Trying to find out if device dm-2 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.602856 #13250] DEBUG -- : Device dm-2 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.603009 #13250] DEBUG -- : Device dm-2 seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.603052 #13250] DEBUG -- : Getting udev properties for device: dm-3
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.606250 #13250] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-rUkZRzj6D5vRpqP0pMmSAclCx0cEIHcppZe4DcAw1cN1dGhIohDD3E7SQuym7xH9 /dev/disk/by-uuid/234b5f0d-1483-4891-9028-8cf76445a7d9 /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-rUkZRzj6D5vRpqP0pMmSAclCx0cEIHcppZe4DcAw1cN1dGhIohDD3E7SQuym7xH9", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"234b5f0d-1483-4891-9028-8cf76445a7d9", "ID_FS_UUID_ENC"=>"234b5f0d-1483-4891-9028-8cf76445a7d9", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81341", "nomdmon
Nov  7 20:57:25 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.606328 #13250] DEBUG -- : Trying to find out if device dm-3 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.606416 #13250] DEBUG -- : Device dm-3 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.606522 #13250] DEBUG -- : Device dm-3 seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.606562 #13250] DEBUG -- : Getting udev properties for device: dm-4
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.610109 #13250] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-urcFWYjE0PXEgZnLy01oXv504srT9GkEAdAGfGYu9KcPgSvMkiRp5oL7ULtDujmF /dev/disk/by-uuid/8f6d70b2-2eb2-4d37-b3c5-b6957684c763 /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-urcFWYjE0PXEgZnLy01oXv504srT9GkEAdAGfGYu9KcPgSvMkiRp5oL7ULtDujmF", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8f6d70b2-2eb2-4d37-b3c5-b6957684c763", "ID_FS_UUID_ENC"=>"8f6d70b2-2eb2-4d37-b3c5-b6957684c763", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82351", "nomdmonddf"=>"1",
Nov  7 20:57:25 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.610192 #13250] DEBUG -- : Trying to find out if device dm-4 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.610355 #13250] DEBUG -- : Device dm-4 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.610397 #13250] DEBUG -- : Device dm-4 seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.610442 #13250] DEBUG -- : Getting udev properties for device: dm-5
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.614717 #13250] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-HkTcSCZuC37rmywi166jgsV3VXau0GghIiiOUCIBUcBrr3XkOn3RG7QKeoBBLIQL /dev/disk/by-uuid/9fc91301-5dc4-4fdc-8130-eef4fe18c38a /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-HkTcSCZuC37rmywi166jgsV3VXau0GghIiiOUCIBUcBrr3XkOn3RG7QKeoBBLIQL", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9fc91301-5dc4-4fdc-8130-eef4fe18c38a", "ID_FS_UUID_ENC"=>"9fc91301-5dc4-4fdc-8130-eef4fe18c38a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85932", "nomdmonddf"=>"1", "nom
Nov  7 20:57:25 node-2 nailgun-agent: dmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.614776 #13250] DEBUG -- : Trying to find out if device dm-5 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.614945 #13250] DEBUG -- : Device dm-5 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.614979 #13250] DEBUG -- : Device dm-5 seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.615010 #13250] DEBUG -- : Getting udev properties for device: dm-6
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.618431 #13250] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-HkTcSCZuC37rmywi166jgsV3VXau0GghettEeDKBUb1R3B3Im1cmwdg14J3wVjTz /dev/disk/by-uuid/5e327bf3-beab-4fd5-b684-f92773ef6324 /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-HkTcSCZuC37rmywi166jgsV3VXau0GghettEeDKBUb1R3B3Im1cmwdg14J3wVjTz", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"5e327bf3-beab-4fd5-b684-f92773ef6324", "ID_FS_UUID_ENC"=>"5e327bf3-beab-4fd5-b684-f92773ef6324", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86309", "nomdmonddf"=>"1", "nomdmonisw
Nov  7 20:57:25 node-2 nailgun-agent: "=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.618512 #13250] DEBUG -- : Trying to find out if device dm-6 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.618585 #13250] DEBUG -- : Device dm-6 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.618620 #13250] DEBUG -- : Device dm-6 seems to be appropriate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.618690 #13250] DEBUG -- : Getting udev properties for device: ram0
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.621676 #13250] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83013", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.621731 #13250] DEBUG -- : Trying to find out if device ram0 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.621824 #13250] DEBUG -- : Device ram0 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.621867 #13250] DEBUG -- : Getting udev properties for device: ram1
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.625070 #13250] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83287", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.625157 #13250] DEBUG -- : Trying to find out if device ram1 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.625227 #13250] DEBUG -- : Device ram1 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.625267 #13250] DEBUG -- : Getting udev properties for device: ram2
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.628564 #13250] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85753", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.628616 #13250] DEBUG -- : Trying to find out if device ram2 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.628680 #13250] DEBUG -- : Device ram2 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.628755 #13250] DEBUG -- : Getting udev properties for device: ram3
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.632094 #13250] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86093", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.632149 #13250] DEBUG -- : Trying to find out if device ram3 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.632272 #13250] DEBUG -- : Device ram3 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.632316 #13250] DEBUG -- : Getting udev properties for device: ram4
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.635639 #13250] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86446", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.635693 #13250] DEBUG -- : Trying to find out if device ram4 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.635764 #13250] DEBUG -- : Device ram4 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.635810 #13250] DEBUG -- : Getting udev properties for device: ram5
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.638364 #13250] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86765", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.638420 #13250] DEBUG -- : Trying to find out if device ram5 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.638511 #13250] DEBUG -- : Device ram5 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.638555 #13250] DEBUG -- : Getting udev properties for device: ram6
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.641201 #13250] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87103", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.641255 #13250] DEBUG -- : Trying to find out if device ram6 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.641335 #13250] DEBUG -- : Device ram6 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.641381 #13250] DEBUG -- : Getting udev properties for device: ram7
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.643975 #13250] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87609", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.644033 #13250] DEBUG -- : Trying to find out if device ram7 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.644173 #13250] DEBUG -- : Device ram7 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.644216 #13250] DEBUG -- : Getting udev properties for device: ram8
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.646748 #13250] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87907", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.646838 #13250] DEBUG -- : Trying to find out if device ram8 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.646917 #13250] DEBUG -- : Device ram8 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.646982 #13250] DEBUG -- : Getting udev properties for device: ram9
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.649685 #13250] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88599", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.649759 #13250] DEBUG -- : Trying to find out if device ram9 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.649858 #13250] DEBUG -- : Device ram9 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.649943 #13250] DEBUG -- : Getting udev properties for device: loop0
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.652944 #13250] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81147", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.653020 #13250] DEBUG -- : Trying to find out if device loop0 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.653111 #13250] DEBUG -- : Device loop0 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.653200 #13250] DEBUG -- : Getting udev properties for device: loop1
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.656418 #13250] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81317", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.656569 #13250] DEBUG -- : Trying to find out if device loop1 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.656680 #13250] DEBUG -- : Device loop1 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.656739 #13250] DEBUG -- : Getting udev properties for device: loop2
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.660071 #13250] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81485", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.660141 #13250] DEBUG -- : Trying to find out if device loop2 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.660251 #13250] DEBUG -- : Device loop2 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.660310 #13250] DEBUG -- : Getting udev properties for device: loop3
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.664800 #13250] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81770", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.664873 #13250] DEBUG -- : Trying to find out if device loop3 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.664989 #13250] DEBUG -- : Device loop3 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.665044 #13250] DEBUG -- : Getting udev properties for device: loop4
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.668486 #13250] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82035", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.668591 #13250] DEBUG -- : Trying to find out if device loop4 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.668687 #13250] DEBUG -- : Device loop4 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.668742 #13250] DEBUG -- : Getting udev properties for device: loop5
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.671922 #13250] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82139", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.671996 #13250] DEBUG -- : Trying to find out if device loop5 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.672133 #13250] DEBUG -- : Device loop5 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.672190 #13250] DEBUG -- : Getting udev properties for device: loop6
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.676199 #13250] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82357", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.676274 #13250] DEBUG -- : Trying to find out if device loop6 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.676392 #13250] DEBUG -- : Device loop6 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.676477 #13250] DEBUG -- : Getting udev properties for device: loop7
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.680527 #13250] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82821", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.680599 #13250] DEBUG -- : Trying to find out if device loop7 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.680700 #13250] DEBUG -- : Device loop7 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.680755 #13250] DEBUG -- : Getting udev properties for device: ram10
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.684400 #13250] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83459", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.684471 #13250] DEBUG -- : Trying to find out if device ram10 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.684567 #13250] DEBUG -- : Device ram10 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.684620 #13250] DEBUG -- : Getting udev properties for device: ram11
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.687586 #13250] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83779", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.687658 #13250] DEBUG -- : Trying to find out if device ram11 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.687755 #13250] DEBUG -- : Device ram11 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.687810 #13250] DEBUG -- : Getting udev properties for device: ram12
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.690768 #13250] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84514", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.690845 #13250] DEBUG -- : Trying to find out if device ram12 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.690936 #13250] DEBUG -- : Device ram12 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.691092 #13250] DEBUG -- : Getting udev properties for device: ram13
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.694137 #13250] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84832", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.694201 #13250] DEBUG -- : Trying to find out if device ram13 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.694324 #13250] DEBUG -- : Device ram13 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.694372 #13250] DEBUG -- : Getting udev properties for device: ram14
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.697329 #13250] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85062", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.697397 #13250] DEBUG -- : Trying to find out if device ram14 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.697524 #13250] DEBUG -- : Device ram14 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.697575 #13250] DEBUG -- : Getting udev properties for device: ram15
Nov  7 20:57:25 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.700569 #13250] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85405", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.700635 #13250] DEBUG -- : Trying to find out if device ram15 is removable or not
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.700735 #13250] DEBUG -- : Device ram15 removable parameter: "0"
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.700823 #13250] 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"}]
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.700860 #13250] DEBUG -- : Block device seems to be physical data storage: sda
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701036 #13250] DEBUG -- : Found block device: dm-0
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701074 #13250] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701108 #13250] DEBUG -- : Found block device: dm-1
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701136 #13250] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701159 #13250] DEBUG -- : Found block device: dm-2
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701188 #13250] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701213 #13250] DEBUG -- : Found block device: dm-3
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701313 #13250] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701337 #13250] DEBUG -- : Found block device: dm-4
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701366 #13250] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701388 #13250] DEBUG -- : Found block device: dm-5
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701412 #13250] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701435 #13250] DEBUG -- : Found block device: dm-6
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701543 #13250] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701567 #13250] DEBUG -- : Found block device: ram0
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701593 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701616 #13250] DEBUG -- : Found block device: ram1
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701641 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701662 #13250] DEBUG -- : Found block device: ram2
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701767 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701791 #13250] DEBUG -- : Found block device: ram3
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701817 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701840 #13250] DEBUG -- : Found block device: ram4
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701870 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701895 #13250] DEBUG -- : Found block device: ram5
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701950 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701972 #13250] DEBUG -- : Found block device: ram6
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.701995 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702016 #13250] DEBUG -- : Found block device: ram7
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702070 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702093 #13250] DEBUG -- : Found block device: ram8
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702117 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702140 #13250] DEBUG -- : Found block device: ram9
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702216 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702238 #13250] DEBUG -- : Found block device: loop0
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702262 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702282 #13250] DEBUG -- : Found block device: loop1
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702304 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702324 #13250] DEBUG -- : Found block device: loop2
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702347 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702411 #13250] DEBUG -- : Found block device: loop3
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702435 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702455 #13250] DEBUG -- : Found block device: loop4
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702481 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702504 #13250] DEBUG -- : Found block device: loop5
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702527 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702603 #13250] DEBUG -- : Found block device: loop6
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702629 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702651 #13250] DEBUG -- : Found block device: loop7
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702673 #13250] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702694 #13250] DEBUG -- : Found block device: ram10
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702717 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702739 #13250] DEBUG -- : Found block device: ram11
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702762 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702815 #13250] DEBUG -- : Found block device: ram12
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702843 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702866 #13250] DEBUG -- : Found block device: ram13
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702890 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702912 #13250] DEBUG -- : Found block device: ram14
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702963 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.702986 #13250] DEBUG -- : Found block device: ram15
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.703010 #13250] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.703079 #13250] 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}]
Nov  7 20:57:25 node-2 nailgun-agent: D, [2016-11-07T20:57:25.887651 #13250] DEBUG -- : Response: status: 200 body: {"id": 2}
Nov  7 20:57:25 node-2 nailgun-agent: I, [2016-11-07T20:57:25.888038 #13250]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  7 20:57:36 node-2 puppet-user[13277]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  7 20:57:36 node-2 puppet-user[13277]: Finished catalog run in 33.65 seconds
Nov  7 20:57:38 node-2 puppet-user[16264]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  7 20:57:39 node-2 puppet-user[16264]: Compiled catalog for node-2.domain.tld in environment production in 0.64 seconds
Nov  7 20:57:39 node-2 puppet-user[16264]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  7 20:57:39 node-2 puppet-user[16264]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  7 20:57:39 node-2 puppet-user[16264]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  7 20:57:39 node-2 puppet-user[16264]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  7 20:57:39 node-2 puppet-user[16264]: Finished catalog run in 0.14 seconds
Nov  7 20:57:41 node-2 puppet-user[16739]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  7 20:57:42 node-2 puppet-user[16739]: Compiled catalog for node-2.domain.tld in environment production in 0.98 seconds
Nov  7 20:57:42 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  7 20:57:42 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  7 20:57:42 node-2 crontab[17176]: (root) LIST (root)
Nov  7 20:57:42 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  7 20:57:42 node-2 crontab[17177]: (root) REPLACE (root)
Nov  7 20:57:44 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  7 20:57:44 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  7 20:57:44 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  7 20:57:44 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/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
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  7 20:57:45 node-2 puppet-user[16739]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov  7 20:57:46 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8430" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  7 20:57:46 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  7 20:57:48 node-2 multipathd: uevent trigger error
<27>Nov  7 20:57:48 node-2 multipathd: uevent trigger error
<27>Nov  7 20:57:48 node-2 multipathd: uevent trigger error
<27>Nov  7 20:57:48 node-2 multipathd: uevent trigger error
<27>Nov  7 20:57:48 node-2 multipathd: uevent trigger error
<27>Nov  7 20:57:48 node-2 multipathd: uevent trigger error
<27>Nov  7 20:58:02 node-2 multipathd: uevent trigger error
<27>Nov  7 20:58:02 node-2 multipathd: uevent trigger error
<27>Nov  7 20:58:02 node-2 multipathd: uevent trigger error
<27>Nov  7 20:58:02 node-2 multipathd: uevent trigger error
<27>Nov  7 20:58:02 node-2 multipathd: uevent trigger error
<27>Nov  7 20:58:57 node-2 ntpdate[27720]: no servers can be used, exiting
<27>Nov  7 20:59:29 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:29 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:29 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:29 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:29 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:29 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:32 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:32 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:32 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:32 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:32 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:44 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:44 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:44 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:44 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:44 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:47 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:47 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:47 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:47 node-2 multipathd: uevent trigger error
<27>Nov  7 20:59:47 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:53 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:53 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:53 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:53 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:53 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:53 node-2 multipathd: uevent trigger error
<27>Nov  7 21:00:55 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  7 21:00:55 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  7 21:01:01 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  7 21:01:01 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  7 21:01:07 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  7 21:01:12 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  7 21:01:12 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  7 21:01:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:42 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:42 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:42 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:42 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:42 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:42 node-2 multipathd: uevent trigger error
<129>Nov  7 21:01:45 node-2 haproxy[17595]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:01:45 node-2 haproxy[17595]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:01:46 node-2 haproxy[17600]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:01:46 node-2 haproxy[17600]: proxy mysqld has no server available!
<27>Nov  7 21:01:48 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:48 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:48 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:48 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:48 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:48 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:51 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:51 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:51 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:51 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:51 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:51 node-2 multipathd: uevent trigger error
<129>Nov  7 21:01:54 node-2 haproxy[20173]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:01:54 node-2 haproxy[20173]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:01:54 node-2 haproxy[20173]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:01:54 node-2 haproxy[20173]: proxy mysqld has no server available!
<129>Nov  7 21:01:55 node-2 haproxy[20180]: 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>Nov  7 21:01:55 node-2 haproxy[20180]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:01:55 node-2 haproxy[20180]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:01:55 node-2 haproxy[20180]: proxy object-storage has no server available!
<27>Nov  7 21:01:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:01:57 node-2 multipathd: uevent trigger error
<129>Nov  7 21:01:59 node-2 haproxy[21535]: 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>Nov  7 21:01:59 node-2 haproxy[21535]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:00 node-2 haproxy[21543]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:00 node-2 haproxy[21543]: proxy neutron has no server available!
<129>Nov  7 21:02:00 node-2 haproxy[21543]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:00 node-2 haproxy[21543]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:00 node-2 haproxy[21543]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:00 node-2 haproxy[21543]: proxy mysqld has no server available!
<129>Nov  7 21:02:00 node-2 haproxy[21543]: 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>Nov  7 21:02:01 node-2 haproxy[21543]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:01 node-2 haproxy[21543]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:01 node-2 haproxy[21543]: proxy object-storage has no server available!
<27>Nov  7 21:02:02 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:02 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:02 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:02 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:02 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:02 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:05 node-2 haproxy[22976]: Server keystone-1/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>Nov  7 21:02:05 node-2 haproxy[22976]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:05 node-2 haproxy[22976]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:05 node-2 haproxy[22976]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:05 node-2 haproxy[22976]: Server keystone-2/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>Nov  7 21:02:05 node-2 haproxy[22976]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:05 node-2 haproxy[22976]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:05 node-2 haproxy[22976]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:05 node-2 haproxy[22976]: 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>Nov  7 21:02:06 node-2 haproxy[22980]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:06 node-2 haproxy[22980]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:06 node-2 haproxy[22980]: proxy neutron has no server available!
<129>Nov  7 21:02:06 node-2 haproxy[22980]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:06 node-2 haproxy[22980]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:06 node-2 haproxy[22980]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:06 node-2 haproxy[22980]: proxy mysqld has no server available!
<129>Nov  7 21:02:06 node-2 haproxy[22980]: 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>Nov  7 21:02:06 node-2 haproxy[22980]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:06 node-2 haproxy[22980]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:06 node-2 haproxy[22980]: proxy object-storage has no server available!
<27>Nov  7 21:02:08 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:08 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:08 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:08 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:08 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:10 node-2 haproxy[24328]: Server keystone-1/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>Nov  7 21:02:10 node-2 haproxy[24328]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:10 node-2 haproxy[24328]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:10 node-2 haproxy[24328]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:10 node-2 haproxy[24328]: Server keystone-2/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>Nov  7 21:02:10 node-2 haproxy[24328]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:10 node-2 haproxy[24328]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:10 node-2 haproxy[24328]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:11 node-2 haproxy[24332]: 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>Nov  7 21:02:11 node-2 haproxy[24332]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:11 node-2 haproxy[24332]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:11 node-2 haproxy[24332]: proxy neutron has no server available!
<129>Nov  7 21:02:11 node-2 haproxy[24332]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:11 node-2 haproxy[24332]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:11 node-2 haproxy[24332]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:11 node-2 haproxy[24332]: proxy mysqld has no server available!
<129>Nov  7 21:02:11 node-2 haproxy[24332]: 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>Nov  7 21:02:11 node-2 haproxy[24332]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:11 node-2 haproxy[24332]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:11 node-2 haproxy[24332]: proxy object-storage has no server available!
<129>Nov  7 21:02:12 node-2 haproxy[24332]: 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>Nov  7 21:02:12 node-2 haproxy[24332]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:12 node-2 haproxy[24332]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:12 node-2 haproxy[24332]: proxy aodh has no server available!
<27>Nov  7 21:02:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:13 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:15 node-2 haproxy[25663]: Server keystone-1/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>Nov  7 21:02:15 node-2 haproxy[25663]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:16 node-2 haproxy[25667]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:16 node-2 haproxy[25667]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:16 node-2 haproxy[25667]: Server keystone-2/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>Nov  7 21:02:16 node-2 haproxy[25667]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:16 node-2 haproxy[25667]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:16 node-2 haproxy[25667]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:16 node-2 haproxy[25667]: 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>Nov  7 21:02:16 node-2 haproxy[25667]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:16 node-2 haproxy[25667]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:16 node-2 haproxy[25667]: proxy neutron has no server available!
<129>Nov  7 21:02:16 node-2 haproxy[25667]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:16 node-2 haproxy[25667]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:16 node-2 haproxy[25667]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:16 node-2 haproxy[25667]: proxy mysqld has no server available!
<129>Nov  7 21:02:16 node-2 haproxy[25667]: 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>Nov  7 21:02:17 node-2 haproxy[25667]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:17 node-2 haproxy[25667]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:17 node-2 haproxy[25667]: proxy object-storage has no server available!
<129>Nov  7 21:02:17 node-2 haproxy[25667]: 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>Nov  7 21:02:17 node-2 haproxy[25667]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:17 node-2 haproxy[25667]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:17 node-2 haproxy[25667]: proxy aodh has no server available!
<129>Nov  7 21:02:17 node-2 haproxy[25667]: 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>Nov  7 21:02:17 node-2 haproxy[25667]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:17 node-2 haproxy[25667]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:17 node-2 haproxy[25667]: proxy ceilometer has no server available!
<27>Nov  7 21:02:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:19 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:21 node-2 haproxy[27021]: Server keystone-1/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>Nov  7 21:02:21 node-2 haproxy[27021]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:21 node-2 haproxy[27021]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:21 node-2 haproxy[27021]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:21 node-2 haproxy[27021]: Server keystone-2/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>Nov  7 21:02:21 node-2 haproxy[27021]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:21 node-2 haproxy[27021]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:21 node-2 haproxy[27021]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:21 node-2 haproxy[27021]: 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>Nov  7 21:02:21 node-2 haproxy[27021]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:22 node-2 haproxy[27030]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:22 node-2 haproxy[27030]: proxy neutron has no server available!
<129>Nov  7 21:02:22 node-2 haproxy[27030]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:22 node-2 haproxy[27030]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:22 node-2 haproxy[27030]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:22 node-2 haproxy[27030]: proxy mysqld has no server available!
<129>Nov  7 21:02:22 node-2 haproxy[27030]: 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>Nov  7 21:02:22 node-2 haproxy[27030]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:22 node-2 haproxy[27030]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:22 node-2 haproxy[27030]: proxy object-storage has no server available!
<129>Nov  7 21:02:22 node-2 haproxy[27030]: 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>Nov  7 21:02:22 node-2 haproxy[27030]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:22 node-2 haproxy[27030]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:22 node-2 haproxy[27030]: proxy aodh has no server available!
<129>Nov  7 21:02:23 node-2 haproxy[27030]: 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>Nov  7 21:02:23 node-2 haproxy[27030]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:23 node-2 haproxy[27030]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:23 node-2 haproxy[27030]: proxy ceilometer has no server available!
<27>Nov  7 21:02:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:24 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:26 node-2 haproxy[28491]: Server horizon/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>Nov  7 21:02:26 node-2 haproxy[28491]: Server keystone-1/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>Nov  7 21:02:26 node-2 haproxy[28491]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:27 node-2 haproxy[28509]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:27 node-2 haproxy[28509]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:27 node-2 haproxy[28509]: Server keystone-2/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>Nov  7 21:02:27 node-2 haproxy[28509]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:27 node-2 haproxy[28509]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:27 node-2 haproxy[28509]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:27 node-2 haproxy[28509]: 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>Nov  7 21:02:27 node-2 haproxy[28509]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:27 node-2 haproxy[28509]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:27 node-2 haproxy[28509]: proxy neutron has no server available!
<129>Nov  7 21:02:27 node-2 haproxy[28509]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:27 node-2 haproxy[28509]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:27 node-2 haproxy[28509]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:27 node-2 haproxy[28509]: proxy mysqld has no server available!
<129>Nov  7 21:02:27 node-2 haproxy[28509]: 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>Nov  7 21:02:27 node-2 haproxy[28509]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:28 node-2 haproxy[28509]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:28 node-2 haproxy[28509]: proxy object-storage has no server available!
<129>Nov  7 21:02:28 node-2 haproxy[28509]: 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>Nov  7 21:02:28 node-2 haproxy[28509]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:28 node-2 haproxy[28509]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:28 node-2 haproxy[28509]: proxy aodh has no server available!
<129>Nov  7 21:02:28 node-2 haproxy[28509]: 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>Nov  7 21:02:28 node-2 haproxy[28509]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:28 node-2 haproxy[28509]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:28 node-2 haproxy[28509]: proxy ceilometer has no server available!
<27>Nov  7 21:02:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:29 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:32 node-2 haproxy[29890]: Server horizon/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>Nov  7 21:02:32 node-2 haproxy[29890]: Server keystone-1/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>Nov  7 21:02:32 node-2 haproxy[29890]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:32 node-2 haproxy[29890]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:32 node-2 haproxy[29890]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:32 node-2 haproxy[29890]: Server keystone-2/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>Nov  7 21:02:32 node-2 haproxy[29890]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:32 node-2 haproxy[29890]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:32 node-2 haproxy[29890]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:32 node-2 haproxy[29890]: 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>Nov  7 21:02:32 node-2 haproxy[29890]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:33 node-2 haproxy[29894]: proxy glance-api has no server available!
<129>Nov  7 21:02:33 node-2 haproxy[29894]: 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>Nov  7 21:02:33 node-2 haproxy[29894]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:33 node-2 haproxy[29894]: proxy glance-glare has no server available!
<129>Nov  7 21:02:33 node-2 haproxy[29894]: 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>Nov  7 21:02:33 node-2 haproxy[29894]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:33 node-2 haproxy[29894]: proxy neutron has no server available!
<129>Nov  7 21:02:33 node-2 haproxy[29894]: 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>Nov  7 21:02:33 node-2 haproxy[29894]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:33 node-2 haproxy[29894]: proxy glance-registry has no server available!
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:33 node-2 haproxy[29894]: proxy mysqld has no server available!
<129>Nov  7 21:02:33 node-2 haproxy[29894]: 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>Nov  7 21:02:33 node-2 haproxy[29894]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:33 node-2 haproxy[29894]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:33 node-2 haproxy[29894]: proxy object-storage has no server available!
<129>Nov  7 21:02:33 node-2 haproxy[29894]: 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>Nov  7 21:02:34 node-2 haproxy[29894]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:34 node-2 haproxy[29894]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:34 node-2 haproxy[29894]: proxy aodh has no server available!
<129>Nov  7 21:02:34 node-2 haproxy[29894]: 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>Nov  7 21:02:34 node-2 haproxy[29894]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:34 node-2 haproxy[29894]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:34 node-2 haproxy[29894]: proxy ceilometer has no server available!
<27>Nov  7 21:02:35 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:35 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:35 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:35 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:35 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:35 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:38 node-2 haproxy[31276]: Server horizon/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>Nov  7 21:02:38 node-2 haproxy[31276]: Server keystone-1/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>Nov  7 21:02:38 node-2 haproxy[31276]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:38 node-2 haproxy[31276]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:38 node-2 haproxy[31276]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:38 node-2 haproxy[31276]: Server keystone-2/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>Nov  7 21:02:38 node-2 haproxy[31276]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:38 node-2 haproxy[31276]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:38 node-2 haproxy[31276]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:38 node-2 haproxy[31276]: 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>Nov  7 21:02:38 node-2 haproxy[31276]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:38 node-2 haproxy[31276]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:38 node-2 haproxy[31276]: proxy nova-api has no server available!
<129>Nov  7 21:02:38 node-2 haproxy[31276]: 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>Nov  7 21:02:38 node-2 haproxy[31276]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:38 node-2 haproxy[31276]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:38 node-2 haproxy[31276]: proxy nova-metadata-api has no server available!
<129>Nov  7 21:02:38 node-2 haproxy[31276]: 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>Nov  7 21:02:38 node-2 haproxy[31276]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:38 node-2 haproxy[31276]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:38 node-2 haproxy[31276]: proxy glance-api has no server available!
<129>Nov  7 21:02:38 node-2 haproxy[31276]: 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>Nov  7 21:02:38 node-2 haproxy[31276]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:39 node-2 haproxy[31282]: proxy glance-glare has no server available!
<129>Nov  7 21:02:39 node-2 haproxy[31282]: 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>Nov  7 21:02:39 node-2 haproxy[31282]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:39 node-2 haproxy[31282]: proxy neutron has no server available!
<129>Nov  7 21:02:39 node-2 haproxy[31282]: 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>Nov  7 21:02:39 node-2 haproxy[31282]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:39 node-2 haproxy[31282]: proxy glance-registry has no server available!
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:39 node-2 haproxy[31282]: proxy mysqld has no server available!
<129>Nov  7 21:02:39 node-2 haproxy[31282]: 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>Nov  7 21:02:39 node-2 haproxy[31282]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:39 node-2 haproxy[31282]: proxy object-storage has no server available!
<129>Nov  7 21:02:39 node-2 haproxy[31282]: 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>Nov  7 21:02:39 node-2 haproxy[31282]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:39 node-2 haproxy[31282]: proxy aodh has no server available!
<129>Nov  7 21:02:39 node-2 haproxy[31282]: 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>Nov  7 21:02:39 node-2 haproxy[31282]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:39 node-2 haproxy[31282]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:39 node-2 haproxy[31282]: proxy ceilometer has no server available!
<129>Nov  7 21:02:39 node-2 haproxy[31282]: 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>Nov  7 21:02:39 node-2 haproxy[31282]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:40 node-2 haproxy[31282]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:40 node-2 haproxy[31282]: proxy nova-novncproxy has no server available!
<27>Nov  7 21:02:41 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:41 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:41 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:41 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:41 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:41 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:43 node-2 haproxy[348]: Server horizon/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>Nov  7 21:02:43 node-2 haproxy[348]: Server keystone-1/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>Nov  7 21:02:43 node-2 haproxy[348]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:43 node-2 haproxy[348]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:43 node-2 haproxy[348]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:43 node-2 haproxy[348]: Server keystone-2/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>Nov  7 21:02:43 node-2 haproxy[348]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:43 node-2 haproxy[348]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:43 node-2 haproxy[348]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:43 node-2 haproxy[348]: 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>Nov  7 21:02:43 node-2 haproxy[348]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:43 node-2 haproxy[348]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:43 node-2 haproxy[348]: proxy nova-api has no server available!
<129>Nov  7 21:02:43 node-2 haproxy[348]: 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>Nov  7 21:02:44 node-2 haproxy[352]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy nova-metadata-api has no server available!
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy cinder-api has no server available!
<129>Nov  7 21:02:44 node-2 haproxy[352]: 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>Nov  7 21:02:44 node-2 haproxy[352]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy glance-api has no server available!
<129>Nov  7 21:02:44 node-2 haproxy[352]: 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>Nov  7 21:02:44 node-2 haproxy[352]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy glance-glare has no server available!
<129>Nov  7 21:02:44 node-2 haproxy[352]: 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>Nov  7 21:02:44 node-2 haproxy[352]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy neutron has no server available!
<129>Nov  7 21:02:44 node-2 haproxy[352]: 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>Nov  7 21:02:44 node-2 haproxy[352]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy glance-registry has no server available!
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy mysqld has no server available!
<129>Nov  7 21:02:44 node-2 haproxy[352]: 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>Nov  7 21:02:44 node-2 haproxy[352]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:44 node-2 haproxy[352]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:44 node-2 haproxy[352]: proxy object-storage has no server available!
<129>Nov  7 21:02:45 node-2 haproxy[352]: 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>Nov  7 21:02:45 node-2 haproxy[352]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:45 node-2 haproxy[352]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:45 node-2 haproxy[352]: proxy aodh has no server available!
<129>Nov  7 21:02:45 node-2 haproxy[352]: 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>Nov  7 21:02:45 node-2 haproxy[352]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:45 node-2 haproxy[352]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:45 node-2 haproxy[352]: proxy ceilometer has no server available!
<129>Nov  7 21:02:45 node-2 haproxy[352]: 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>Nov  7 21:02:45 node-2 haproxy[352]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:45 node-2 haproxy[352]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:45 node-2 haproxy[352]: proxy nova-novncproxy has no server available!
<27>Nov  7 21:02:46 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:46 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:46 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:46 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:46 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:46 node-2 multipathd: uevent trigger error
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server keystone-1/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>Nov  7 21:02:49 node-2 haproxy[1788]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:49 node-2 haproxy[1788]: proxy keystone-1 has no server available!
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server keystone-2/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>Nov  7 21:02:49 node-2 haproxy[1788]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:49 node-2 haproxy[1788]: proxy keystone-2 has no server available!
<129>Nov  7 21:02:49 node-2 haproxy[1788]: 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>Nov  7 21:02:49 node-2 haproxy[1788]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:49 node-2 haproxy[1788]: proxy nova-api has no server available!
<129>Nov  7 21:02:49 node-2 haproxy[1788]: 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>Nov  7 21:02:49 node-2 haproxy[1788]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:49 node-2 haproxy[1788]: proxy nova-metadata-api has no server available!
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:49 node-2 haproxy[1788]: proxy cinder-api has no server available!
<129>Nov  7 21:02:49 node-2 haproxy[1788]: 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>Nov  7 21:02:49 node-2 haproxy[1788]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:49 node-2 haproxy[1788]: proxy glance-api has no server available!
<129>Nov  7 21:02:49 node-2 haproxy[1788]: 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>Nov  7 21:02:49 node-2 haproxy[1788]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:49 node-2 haproxy[1788]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:49 node-2 haproxy[1788]: proxy glance-glare has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy neutron has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy glance-registry has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy mysqld has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy object-storage has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy aodh has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy ceilometer has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy heat-api has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy heat-api-cfn has no server available!
<129>Nov  7 21:02:50 node-2 haproxy[1792]: 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>Nov  7 21:02:50 node-2 haproxy[1792]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:50 node-2 haproxy[1792]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:50 node-2 haproxy[1792]: proxy heat-api-cloudwatch has no server available!
<129>Nov  7 21:02:51 node-2 haproxy[1792]: 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>Nov  7 21:02:51 node-2 haproxy[1792]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  7 21:02:51 node-2 haproxy[1792]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  7 21:02:51 node-2 haproxy[1792]: proxy nova-novncproxy has no server available!
<27>Nov  7 21:02:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:56 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:56 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:56 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:56 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:56 node-2 multipathd: uevent trigger error
<27>Nov  7 21:02:56 node-2 multipathd: uevent trigger error
<27>Nov  7 21:03:04 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  7 21:03:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  7 21:03:25 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  7 21:03:29 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>Nov  7 21:03:31 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  7 21:04:27 node-2 multipathd: uevent trigger error
<27>Nov  7 21:04:27 node-2 multipathd: uevent trigger error
<27>Nov  7 21:04:27 node-2 multipathd: uevent trigger error
<27>Nov  7 21:04:27 node-2 multipathd: uevent trigger error
<27>Nov  7 21:04:27 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:14 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:26 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  7 21:06:26 node-2 apache2_error [Mon Nov 07 21:06:26.374955 2016] [mpm_event:notice] [pid 12070:tid 140268493342592] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  7 21:06:26 node-2 apache2_error [Mon Nov 07 21:06:26.375097 2016] [core:notice] [pid 12070:tid 140268493342592] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  7 21:06:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:34 node-2 multipathd: uevent trigger error
<43>Nov  7 21:06:36 node-2 apache2_error [Mon Nov 07 21:06:29.360564 2016] [mpm_event:notice] [pid 12070:tid 140268493342592] AH00491: caught SIGTERM, shutting down
<43>Nov  7 21:06:36 node-2 apache2_error [Mon Nov 07 21:06:30.444107 2016] [mpm_worker:notice] [pid 12578:tid 139915252672384] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  7 21:06:36 node-2 apache2_error [Mon Nov 07 21:06:30.444130 2016] [core:notice] [pid 12578:tid 139915252672384] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  7 21:06:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:43 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:43 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:43 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:43 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:43 node-2 multipathd: uevent trigger error
<27>Nov  7 21:06:43 node-2 multipathd: uevent trigger error
<43>Nov  7 21:07:57 node-2 apache2_error [Mon Nov 07 21:07:52.745497 2016] [mpm_worker:notice] [pid 12578:tid 139915252672384] AH00295: caught SIGTERM, shutting down
<43>Nov  7 21:07:57 node-2 apache2_error [Mon Nov 07 21:07:53.496910 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  7 21:07:57 node-2 apache2_error [Mon Nov 07 21:07:53.496957 2016] [core:notice] [pid 26049:tid 140578602825600] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  7 21:08:47 node-2 apache2_error [Mon Nov 07 21:08:39.537359 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  7 21:08:47 node-2 apache2_error [Mon Nov 07 21:08:39.731637 2016] [mpm_worker:warn] [pid 26049:tid 140578602825600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  7 21:08:47 node-2 apache2_error [Mon Nov 07 21:08:39.734108 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  7 21:08:47 node-2 apache2_error [Mon Nov 07 21:08:39.734131 2016] [core:notice] [pid 26049:tid 140578602825600] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  7 21:09:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:28 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  7 21:09:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:09:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:14 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:14 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:14 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:14 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:14 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:14 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:59 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:59 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:59 node-2 multipathd: uevent trigger error
<27>Nov  7 21:10:59 node-2 multipathd: uevent trigger error
<27>Nov  7 21:11:00 node-2 multipathd: uevent trigger error
<27>Nov  7 21:11:00 node-2 multipathd: uevent trigger error
<27>Nov  7 21:11:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:11:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:11:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:11:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:11:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:12:06 node-2 multipathd: uevent trigger error
<27>Nov  7 21:12:06 node-2 multipathd: uevent trigger error
<27>Nov  7 21:12:06 node-2 multipathd: uevent trigger error
<27>Nov  7 21:12:06 node-2 multipathd: uevent trigger error
<27>Nov  7 21:12:06 node-2 multipathd: uevent trigger error
<27>Nov  7 21:12:06 node-2 multipathd: uevent trigger error
<27>Nov  7 21:12:29 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  7 21:13:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:13:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:13:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:13:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:13:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:13:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:14:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:15:31 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  7 21:17:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:17:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:32 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  7 21:18:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:18:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Nov  7 21:19:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Nov  7 21:19:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Nov  7 21:19:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Nov  7 21:19:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Nov  7 21:19:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:58 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:58 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:58 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:58 node-2 multipathd: uevent trigger error
<27>Nov  7 21:19:58 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:20:31 node-2 multipathd: uevent trigger error
<27>Nov  7 21:21:34 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  7 21:22:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:22:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:22:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:22:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:22:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:21 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:21 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:21 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:21 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:21 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:26 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:26 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:26 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:26 node-2 multipathd: uevent trigger error
<27>Nov  7 21:23:26 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:04 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:04 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:04 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:04 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:05 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:05 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:09 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:13 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:35 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  7 21:24:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:24:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:25:12 node-2 multipathd: uevent trigger error
<27>Nov  7 21:25:12 node-2 multipathd: uevent trigger error
<27>Nov  7 21:25:12 node-2 multipathd: uevent trigger error
<27>Nov  7 21:25:12 node-2 multipathd: uevent trigger error
<27>Nov  7 21:25:12 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:16 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:32 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:32 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:32 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:32 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:32 node-2 multipathd: uevent trigger error
<27>Nov  7 21:26:32 node-2 multipathd: uevent trigger error
<11>Nov  7 21:26:45 node-2 liberasurecode[15584]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:45 node-2 liberasurecode[15584]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:45 node-2 liberasurecode[15584]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:45 node-2 liberasurecode[15584]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:45 node-2 liberasurecode[15613]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:45 node-2 liberasurecode[15613]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:45 node-2 liberasurecode[15613]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:45 node-2 liberasurecode[15613]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:47 node-2 liberasurecode[16005]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:47 node-2 liberasurecode[16005]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:47 node-2 liberasurecode[16005]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:47 node-2 liberasurecode[16005]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18027]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18027]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18027]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18027]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18181]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18181]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18181]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18181]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18294]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18294]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18294]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18294]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18398]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18398]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18413]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18413]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18413]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18413]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18426]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18426]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18426]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18426]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18440]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18440]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18440]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:26:52 node-2 liberasurecode[18440]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  7 21:27:01 node-2 liberasurecode[18815]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:27:01 node-2 liberasurecode[18815]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:27:01 node-2 liberasurecode[18815]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:27:01 node-2 liberasurecode[18815]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  7 21:27:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:27:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:27:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:27:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:27:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:27:37 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  7 21:27:59 node-2 apache2_error [Mon Nov 07 21:27:56.649108 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  7 21:27:59 node-2 apache2_error [Mon Nov 07 21:27:57.032381 2016] [mpm_worker:warn] [pid 26049:tid 140578602825600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  7 21:27:59 node-2 apache2_error [Mon Nov 07 21:27:57.036335 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  7 21:27:59 node-2 apache2_error [Mon Nov 07 21:27:57.036354 2016] [core:notice] [pid 26049:tid 140578602825600] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  7 21:28:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:37 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:37 node-2 multipathd: uevent trigger error
<43>Nov  7 21:28:39 node-2 apache2_error [Mon Nov 07 21:28:33.811879 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  7 21:28:39 node-2 apache2_error [Mon Nov 07 21:28:34.007100 2016] [mpm_worker:warn] [pid 26049:tid 140578602825600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  7 21:28:39 node-2 apache2_error [Mon Nov 07 21:28:34.012329 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  7 21:28:39 node-2 apache2_error [Mon Nov 07 21:28:34.012352 2016] [core:notice] [pid 26049:tid 140578602825600] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  7 21:28:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:28:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:24 node-2 multipathd: uevent trigger error
<43>Nov  7 21:29:29 node-2 apache2_error [Mon Nov 07 21:29:20.061343 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  7 21:29:29 node-2 apache2_error [Mon Nov 07 21:29:20.256347 2016] [mpm_worker:warn] [pid 26049:tid 140578602825600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  7 21:29:29 node-2 apache2_error [Mon Nov 07 21:29:20.260861 2016] [mpm_worker:notice] [pid 26049:tid 140578602825600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  7 21:29:29 node-2 apache2_error [Mon Nov 07 21:29:20.260886 2016] [core:notice] [pid 26049:tid 140578602825600] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  7 21:29:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:30 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:36 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:29:55 node-2 multipathd: uevent trigger error
<11>Nov  7 21:30:02 node-2 liberasurecode[20442]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:30:02 node-2 liberasurecode[20442]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:30:02 node-2 liberasurecode[20442]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 21:30:02 node-2 liberasurecode[20442]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  7 21:30:17 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:31 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  7 21:30:40 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:40 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:40 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:40 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:40 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:44 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:45 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:49 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:50 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:50 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:50 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:50 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:30:55 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:07 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:39 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:52 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:31:57 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:10 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:15 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:19 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:24 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:29 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:34 node-2 multipathd: uevent trigger error
<27>Nov  7 21:32:34 node-2 multipathd: uevent trigger error
