Oct  6 15:34:50 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] start
Oct  6 15:34:50 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  6 15:34:50 node-2 rsyslogd: rsyslogd's groupid changed to 104
Oct  6 15:34:50 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct  6 15:34:50 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  6 15:34:50 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  6 15:34:50 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  6 15:34:50 node-2 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Oct  6 15:34:50 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f3f3f058-77c1-482c-aabc-2f2c3689ab97 nomdmonddf nomdmonisw
Oct  6 15:34:50 node-2 kernel: [    0.000000] KERNEL supported cpus:
Oct  6 15:34:50 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct  6 15:34:50 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct  6 15:34:50 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct  6 15:34:50 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  6 15:34:50 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  6 15:34:50 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  6 15:34:50 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct  6 15:34:50 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  6 15:34:50 node-2 kernel: [    0.000000] No AGP bridge found
Oct  6 15:34:50 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  6 15:34:50 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct  6 15:34:50 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  6 15:34:50 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct  6 15:34:50 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  6 15:34:50 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  6 15:34:50 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  6 15:34:50 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  6 15:34:50 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  6 15:34:50 node-2 kernel: [    0.000000]   2 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000]   3 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000]   4 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000]   5 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000]   6 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000]   7 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000]   8 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000]   9 disabled
Oct  6 15:34:50 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  6 15:34:50 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  6 15:34:50 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  6 15:34:50 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  6 15:34:50 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  6 15:34:50 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  6 15:34:50 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  6 15:34:50 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  6 15:34:50 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  6 15:34:50 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  6 15:34:50 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  6 15:34:50 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  6 15:34:50 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  6 15:34:50 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  6 15:34:50 node-2 kernel: [    0.000000] Zone ranges:
Oct  6 15:34:50 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] Movable zone start for each node
Oct  6 15:34:50 node-2 kernel: [    0.000000] Early memory node ranges
Oct  6 15:34:50 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct  6 15:34:50 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  6 15:34:50 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  6 15:34:50 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  6 15:34:50 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct  6 15:34:50 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct  6 15:34:50 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  6 15:34:50 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  6 15:34:50 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  6 15:34:50 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  6 15:34:50 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  6 15:34:50 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  6 15:34:50 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  6 15:34:50 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  6 15:34:50 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  6 15:34:50 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  6 15:34:50 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  6 15:34:50 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  6 15:34:50 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  6 15:34:50 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  6 15:34:50 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  6 15:34:50 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  6 15:34:50 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  6 15:34:50 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct  6 15:34:50 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct  6 15:34:50 node-2 kernel: [    0.000000] Policy zone: Normal
Oct  6 15:34:50 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f3f3f058-77c1-482c-aabc-2f2c3689ab97 nomdmonddf nomdmonisw
Oct  6 15:34:50 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  6 15:34:50 node-2 kernel: [    0.000000] Checking aperture...
Oct  6 15:34:50 node-2 kernel: [    0.000000] No AGP bridge found
Oct  6 15:34:50 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  6 15:34:50 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  6 15:34:50 node-2 kernel: [    0.000000] Memory: 32653452K/33280636K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct  6 15:34:50 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  6 15:34:50 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  6 15:34:50 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  6 15:34:50 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  6 15:34:50 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  6 15:34:50 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  6 15:34:50 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  6 15:34:50 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  6 15:34:50 node-2 kernel: [    0.000000] console [tty0] enabled
Oct  6 15:34:50 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  6 15:34:50 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  6 15:34:50 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  6 15:34:50 node-2 kernel: [    0.000000] hpet clockevent registered
Oct  6 15:34:50 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  6 15:34:50 node-2 kernel: [    0.004000] tsc: Detected 3492.207 MHz processor
Oct  6 15:34:50 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.41 BogoMIPS (lpj=13968828)
Oct  6 15:34:50 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  6 15:34:50 node-2 kernel: [    0.000050] Security Framework initialized
Oct  6 15:34:50 node-2 kernel: [    0.000068] AppArmor: AppArmor initialized
Oct  6 15:34:50 node-2 kernel: [    0.000069] Yama: becoming mindful.
Oct  6 15:34:50 node-2 kernel: [    0.001452] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.006381] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.008310] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.008339] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.008631] Initializing cgroup subsys memory
Oct  6 15:34:50 node-2 kernel: [    0.008639] Initializing cgroup subsys devices
Oct  6 15:34:50 node-2 kernel: [    0.008640] Initializing cgroup subsys freezer
Oct  6 15:34:50 node-2 kernel: [    0.008642] Initializing cgroup subsys blkio
Oct  6 15:34:50 node-2 kernel: [    0.008644] Initializing cgroup subsys perf_event
Oct  6 15:34:50 node-2 kernel: [    0.008646] Initializing cgroup subsys hugetlb
Oct  6 15:34:50 node-2 kernel: [    0.008665] CPU: Physical Processor ID: 0
Oct  6 15:34:50 node-2 kernel: [    0.008667] CPU: Processor Core ID: 0
Oct  6 15:34:50 node-2 kernel: [    0.008670] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  6 15:34:50 node-2 kernel: [    0.008670] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  6 15:34:50 node-2 kernel: [    0.009365] mce: CPU supports 22 MCE banks
Oct  6 15:34:50 node-2 kernel: [    0.009392] CPU0: Thermal monitoring enabled (TM1)
Oct  6 15:34:50 node-2 kernel: [    0.009412] process: using mwait in idle threads
Oct  6 15:34:50 node-2 kernel: [    0.009416] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  6 15:34:50 node-2 kernel: [    0.009416] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  6 15:34:50 node-2 kernel: [    0.009416] tlb_flushall_shift: 6
Oct  6 15:34:50 node-2 kernel: [    0.009503] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  6 15:34:50 node-2 kernel: [    0.010226] ACPI: Core revision 20131115
Oct  6 15:34:50 node-2 kernel: [    0.022895] ACPI: All ACPI Tables successfully acquired
Oct  6 15:34:50 node-2 kernel: [    0.023055] ftrace: allocating 28614 entries in 112 pages
Oct  6 15:34:50 node-2 kernel: [    0.031756] dmar: Host address width 46
Oct  6 15:34:50 node-2 kernel: [    0.031758] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  6 15:34:50 node-2 kernel: [    0.031764] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  6 15:34:50 node-2 kernel: [    0.031766] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  6 15:34:50 node-2 kernel: [    0.031769] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  6 15:34:50 node-2 kernel: [    0.031771] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  6 15:34:50 node-2 kernel: [    0.031772] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  6 15:34:50 node-2 kernel: [    0.031773] dmar: ATSR flags: 0x0
Oct  6 15:34:50 node-2 kernel: [    0.031774] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  6 15:34:50 node-2 kernel: [    0.031776] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  6 15:34:50 node-2 kernel: [    0.031891] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  6 15:34:50 node-2 kernel: [    0.031892] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  6 15:34:50 node-2 kernel: [    0.031893] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  6 15:34:50 node-2 kernel: [    0.031894] HPET id 0 under DRHD base 0xc7ffc000
Oct  6 15:34:50 node-2 kernel: [    0.031895] Your BIOS is broken and requested that x2apic be disabled.
Oct  6 15:34:50 node-2 kernel: [    0.031895] This will slightly decrease performance.
Oct  6 15:34:50 node-2 kernel: [    0.031895] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  6 15:34:50 node-2 kernel: [    0.032327] Enabled IRQ remapping in xapic mode
Oct  6 15:34:50 node-2 kernel: [    0.032328] x2apic not enabled, IRQ remapping is in xapic mode
Oct  6 15:34:50 node-2 kernel: [    0.032332] Switched APIC routing to physical flat.
Oct  6 15:34:50 node-2 kernel: [    0.032906] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  6 15:34:50 node-2 kernel: [    0.072559] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  6 15:34:50 node-2 kernel: [    0.072565] TSC deadline timer enabled
Oct  6 15:34:50 node-2 kernel: [    0.072572] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  6 15:34:50 node-2 kernel: [    0.072578] ... version:                3
Oct  6 15:34:50 node-2 kernel: [    0.072579] ... bit width:              48
Oct  6 15:34:50 node-2 kernel: [    0.072580] ... generic registers:      4
Oct  6 15:34:50 node-2 kernel: [    0.072581] ... value mask:             0000ffffffffffff
Oct  6 15:34:50 node-2 kernel: [    0.072582] ... max period:             0000ffffffffffff
Oct  6 15:34:50 node-2 kernel: [    0.072583] ... fixed-purpose events:   3
Oct  6 15:34:50 node-2 kernel: [    0.072583] ... event mask:             000000070000000f
Oct  6 15:34:50 node-2 kernel: [    0.073979] x86: Booting SMP configuration:
Oct  6 15:34:50 node-2 kernel: [    0.088083] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  6 15:34:50 node-2 kernel: [    0.073981] .... node  #0, CPUs:        #1  #2  #3
Oct  6 15:34:50 node-2 kernel: [    0.115992] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  6 15:34:50 node-2 kernel: [    0.270154] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  6 15:34:50 node-2 kernel: [    0.325787] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  6 15:34:50 node-2 kernel: [    0.382852] x86: Booted up 2 nodes, 16 CPUs
Oct  6 15:34:50 node-2 kernel: [    0.382856] smpboot: Total of 16 processors activated (111763.80 BogoMIPS)
Oct  6 15:34:50 node-2 kernel: [    0.407566] devtmpfs: initialized
Oct  6 15:34:50 node-2 kernel: [    0.410076] EVM: security.selinux
Oct  6 15:34:50 node-2 kernel: [    0.410078] EVM: security.SMACK64
Oct  6 15:34:50 node-2 kernel: [    0.410079] EVM: security.ima
Oct  6 15:34:50 node-2 kernel: [    0.410079] EVM: security.capability
Oct  6 15:34:50 node-2 kernel: [    0.410130] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.410783] pinctrl core: initialized pinctrl subsystem
Oct  6 15:34:50 node-2 kernel: [    0.410844] regulator-dummy: no parameters
Oct  6 15:34:50 node-2 kernel: [    0.410875] RTC time: 15:34:14, date: 10/06/16
Oct  6 15:34:50 node-2 kernel: [    0.410910] NET: Registered protocol family 16
Oct  6 15:34:50 node-2 kernel: [    0.410995] cpuidle: using governor ladder
Oct  6 15:34:50 node-2 kernel: [    0.410996] cpuidle: using governor menu
Oct  6 15:34:50 node-2 kernel: [    0.411031] ACPI: bus type PCI registered
Oct  6 15:34:50 node-2 kernel: [    0.411039] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  6 15:34:50 node-2 kernel: [    0.411093] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  6 15:34:50 node-2 kernel: [    0.411096] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  6 15:34:50 node-2 kernel: [    0.424833] PCI: Using configuration type 1 for base access
Oct  6 15:34:50 node-2 kernel: [    0.425851] bio: create slab <bio-0> at 0
Oct  6 15:34:50 node-2 kernel: [    0.426143] ACPI: Added _OSI(Module Device)
Oct  6 15:34:50 node-2 kernel: [    0.426145] ACPI: Added _OSI(Processor Device)
Oct  6 15:34:50 node-2 kernel: [    0.426146] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  6 15:34:50 node-2 kernel: [    0.426147] ACPI: Added _OSI(Processor Aggregator Device)
Oct  6 15:34:50 node-2 kernel: [    0.438975] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  6 15:34:50 node-2 kernel: [    0.449671] ACPI: Interpreter enabled
Oct  6 15:34:50 node-2 kernel: [    0.449676] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  6 15:34:50 node-2 kernel: [    0.449680] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  6 15:34:50 node-2 kernel: [    0.449683] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  6 15:34:50 node-2 kernel: [    0.449690] ACPI: (supports S0 S4 S5)
Oct  6 15:34:50 node-2 kernel: [    0.449691] ACPI: Using IOAPIC for interrupt routing
Oct  6 15:34:50 node-2 kernel: [    0.449732] HEST: Table parsing has been initialized.
Oct  6 15:34:50 node-2 kernel: [    0.449735] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  6 15:34:50 node-2 kernel: [    0.450292] ACPI: No dock devices found.
Oct  6 15:34:50 node-2 kernel: [    0.462061] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  6 15:34:50 node-2 kernel: [    0.462066] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  6 15:34:50 node-2 kernel: [    0.462069] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  6 15:34:50 node-2 kernel: [    0.462098] PCI host bridge to bus 0000:ff
Oct  6 15:34:50 node-2 kernel: [    0.462100] pci_bus 0000:ff: root bus resource [bus ff]
Oct  6 15:34:50 node-2 kernel: [    0.462108] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462148] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.462179] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462215] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462245] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.462277] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.462309] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462338] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462370] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462398] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462425] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462452] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462481] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462508] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462535] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462562] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462591] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462619] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462646] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.462674] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462701] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.462727] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462753] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462784] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.462820] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462852] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462882] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462913] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462945] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.462976] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463007] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463038] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463069] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463101] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463135] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463167] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463201] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463231] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463259] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463292] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463327] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463363] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463398] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463431] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463461] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463492] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463523] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463552] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463582] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463613] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463644] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463675] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463704] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463733] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463767] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463799] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463831] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463889] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  6 15:34:50 node-2 kernel: [    0.463891] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  6 15:34:50 node-2 kernel: [    0.463894] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  6 15:34:50 node-2 kernel: [    0.463912] PCI host bridge to bus 0000:7f
Oct  6 15:34:50 node-2 kernel: [    0.463913] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  6 15:34:50 node-2 kernel: [    0.463918] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.463945] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.463974] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464003] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464025] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.464049] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.464075] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464101] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464123] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464146] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464170] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464195] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464221] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464245] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464271] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464301] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464323] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464347] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464370] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.464394] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464416] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.464438] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464461] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464487] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  6 15:34:50 node-2 kernel: [    0.464522] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464548] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464574] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464601] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464626] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464652] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464678] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464706] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464731] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464757] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464783] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464809] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464836] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464861] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464887] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464916] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464942] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464968] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.464996] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465022] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465047] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465072] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465097] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465124] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465148] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465174] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465205] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465230] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465252] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465277] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465302] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465331] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.465357] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.466601] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  6 15:34:50 node-2 kernel: [    0.466605] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  6 15:34:50 node-2 kernel: [    0.467736] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  6 15:34:50 node-2 kernel: [    0.468248] PCI host bridge to bus 0000:00
Oct  6 15:34:50 node-2 kernel: [    0.468251] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  6 15:34:50 node-2 kernel: [    0.468252] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  6 15:34:50 node-2 kernel: [    0.468254] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  6 15:34:50 node-2 kernel: [    0.468255] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  6 15:34:50 node-2 kernel: [    0.468256] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  6 15:34:50 node-2 kernel: [    0.468258] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  6 15:34:50 node-2 kernel: [    0.468259] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  6 15:34:50 node-2 kernel: [    0.468265] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  6 15:34:50 node-2 kernel: [    0.468347] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.468378] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.468420] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  6 15:34:50 node-2 kernel: [    0.468439] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.468468] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.468508] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  6 15:34:50 node-2 kernel: [    0.468525] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.468555] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.468598] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  6 15:34:50 node-2 kernel: [    0.468614] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.468684] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.468764] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.468843] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  6 15:34:50 node-2 kernel: [    0.468848] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  6 15:34:50 node-2 kernel: [    0.468934] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  6 15:34:50 node-2 kernel: [    0.469081] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  6 15:34:50 node-2 kernel: [    0.469099] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  6 15:34:50 node-2 kernel: [    0.469176] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.469230] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  6 15:34:50 node-2 kernel: [    0.469252] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.469307] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.469351] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  6 15:34:50 node-2 kernel: [    0.469381] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.469437] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.469480] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  6 15:34:50 node-2 kernel: [    0.469503] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  6 15:34:50 node-2 kernel: [    0.469520] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  6 15:34:50 node-2 kernel: [    0.469598] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.469648] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  6 15:34:50 node-2 kernel: [    0.469675] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  6 15:34:50 node-2 kernel: [    0.469925] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  6 15:34:50 node-2 kernel: [    0.469931] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  6 15:34:50 node-2 kernel: [    0.469937] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.469943] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.469950] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  6 15:34:50 node-2 kernel: [    0.469980] pci 0000:01:00.0: supports D1 D2
Oct  6 15:34:50 node-2 kernel: [    0.479774] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  6 15:34:50 node-2 kernel: [    0.479781] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  6 15:34:50 node-2 kernel: [    0.479785] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  6 15:34:50 node-2 kernel: [    0.479962] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.479996] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  6 15:34:50 node-2 kernel: [    0.487772] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  6 15:34:50 node-2 kernel: [    0.487778] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.487782] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  6 15:34:50 node-2 kernel: [    0.487874] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.487960] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.488036] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.488082] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  6 15:34:50 node-2 kernel: [    0.488086] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.488087] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  6 15:34:50 node-2 kernel: [    0.488139] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.488262] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.488315] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  6 15:34:50 node-2 kernel: [    0.488318] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.488320] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.488369] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.488488] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.488529] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.488648] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.488686] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.488808] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.488846] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  6 15:34:50 node-2 kernel: [    0.488984] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  6 15:34:50 node-2 kernel: [    0.489029] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  6 15:34:50 node-2 kernel: [    0.489031] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.489033] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.489091] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  6 15:34:50 node-2 kernel: [    0.489155] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.489207] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.489251] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  6 15:34:50 node-2 kernel: [    0.489333] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  6 15:34:50 node-2 kernel: [    0.489439] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  6 15:34:50 node-2 kernel: [    0.489441] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.489443] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.489499] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  6 15:34:50 node-2 kernel: [    0.489553] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.489601] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.489814] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  6 15:34:50 node-2 kernel: [    0.489818] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  6 15:34:50 node-2 kernel: [    0.489882] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  6 15:34:50 node-2 kernel: [    0.489958] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.490007] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.490215] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  6 15:34:50 node-2 kernel: [    0.490218] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  6 15:34:50 node-2 kernel: [    0.490277] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  6 15:34:50 node-2 kernel: [    0.490342] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.490394] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  6 15:34:50 node-2 kernel: [    0.490616] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  6 15:34:50 node-2 kernel: [    0.490620] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  6 15:34:50 node-2 kernel: [    0.490795] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  6 15:34:50 node-2 kernel: [    0.490834] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  6 15:34:50 node-2 kernel: [    0.490909] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  6 15:34:50 node-2 kernel: [    0.490928] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  6 15:34:50 node-2 kernel: [    0.490941] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  6 15:34:50 node-2 kernel: [    0.490954] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  6 15:34:50 node-2 kernel: [    0.491004] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  6 15:34:50 node-2 kernel: [    0.495779] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  6 15:34:50 node-2 kernel: [    0.495788] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  6 15:34:50 node-2 kernel: [    0.495841] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  6 15:34:50 node-2 kernel: [    0.496560] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  6 15:34:50 node-2 kernel: [    0.496563] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  6 15:34:50 node-2 kernel: [    0.496687] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  6 15:34:50 node-2 kernel: [    0.496797] PCI host bridge to bus 0000:80
Oct  6 15:34:50 node-2 kernel: [    0.496799] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  6 15:34:50 node-2 kernel: [    0.496801] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  6 15:34:50 node-2 kernel: [    0.496802] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  6 15:34:50 node-2 kernel: [    0.496810] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.496874] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.496943] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  6 15:34:50 node-2 kernel: [    0.497005] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  6 15:34:50 node-2 kernel: [    0.497010] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  6 15:34:50 node-2 kernel: [    0.497081] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  6 15:34:50 node-2 kernel: [    0.497385] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  6 15:34:50 node-2 kernel: [    0.497417] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  6 15:34:50 node-2 kernel: [    0.497446] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  6 15:34:50 node-2 kernel: [    0.497475] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  6 15:34:50 node-2 kernel: [    0.497505] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  6 15:34:50 node-2 kernel: [    0.497535] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  6 15:34:50 node-2 kernel: [    0.497565] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  6 15:34:50 node-2 kernel: [    0.497595] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  6 15:34:50 node-2 kernel: [    0.497681] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  6 15:34:50 node-2 kernel: [    0.497685] ACPI: \_SB_.UNC1: notify handler is installed
Oct  6 15:34:50 node-2 kernel: [    0.497686] ACPI: \_SB_.UNC0: notify handler is installed
Oct  6 15:34:50 node-2 kernel: [    0.497702] ACPI: \_SB_.PCI0: notify handler is installed
Oct  6 15:34:50 node-2 kernel: [    0.497755] ACPI: \_SB_.PCI1: notify handler is installed
Oct  6 15:34:50 node-2 kernel: [    0.497834] Found 4 acpi root devices
Oct  6 15:34:50 node-2 kernel: [    0.497945] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  6 15:34:50 node-2 kernel: [    0.497948] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  6 15:34:50 node-2 kernel: [    0.497949] vgaarb: loaded
Oct  6 15:34:50 node-2 kernel: [    0.497950] vgaarb: bridge control possible 0000:0c:00.0
Oct  6 15:34:50 node-2 kernel: [    0.498071] SCSI subsystem initialized
Oct  6 15:34:50 node-2 kernel: [    0.498135] libata version 3.00 loaded.
Oct  6 15:34:50 node-2 kernel: [    0.498150] ACPI: bus type USB registered
Oct  6 15:34:50 node-2 kernel: [    0.498160] usbcore: registered new interface driver usbfs
Oct  6 15:34:50 node-2 kernel: [    0.498166] usbcore: registered new interface driver hub
Oct  6 15:34:50 node-2 kernel: [    0.498189] usbcore: registered new device driver usb
Oct  6 15:34:50 node-2 kernel: [    0.498358] PCI: Using ACPI for IRQ routing
Oct  6 15:34:50 node-2 kernel: [    0.501957] PCI: pci_cache_line_size set to 64 bytes
Oct  6 15:34:50 node-2 kernel: [    0.502165] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  6 15:34:50 node-2 kernel: [    0.502167] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct  6 15:34:50 node-2 kernel: [    0.502168] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  6 15:34:50 node-2 kernel: [    0.502234] NetLabel: Initializing
Oct  6 15:34:50 node-2 kernel: [    0.502235] NetLabel:  domain hash size = 128
Oct  6 15:34:50 node-2 kernel: [    0.502236] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  6 15:34:50 node-2 kernel: [    0.502246] NetLabel:  unlabeled traffic allowed by default
Oct  6 15:34:50 node-2 kernel: [    0.502304] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  6 15:34:50 node-2 kernel: [    0.502308] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  6 15:34:50 node-2 kernel: [    0.504365] Switched to clocksource hpet
Oct  6 15:34:50 node-2 kernel: [    0.508389] AppArmor: AppArmor Filesystem Enabled
Oct  6 15:34:50 node-2 kernel: [    0.508403] pnp: PnP ACPI init
Oct  6 15:34:50 node-2 kernel: [    0.508410] ACPI: bus type PNP registered
Oct  6 15:34:50 node-2 kernel: [    0.508520] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508528] pnp 00:01: [dma 4]
Oct  6 15:34:50 node-2 kernel: [    0.508540] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508567] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508587] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508604] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508637] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508689] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508691] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  6 15:34:50 node-2 kernel: [    0.508693] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508694] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508695] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508702] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508705] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  6 15:34:50 node-2 kernel: [    0.508706] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508708] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508709] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508711] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508712] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508714] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  6 15:34:50 node-2 kernel: [    0.508717] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508800] pnp 00:07: [dma 0 disabled]
Oct  6 15:34:50 node-2 kernel: [    0.508829] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508903] pnp 00:08: [dma 0 disabled]
Oct  6 15:34:50 node-2 kernel: [    0.508935] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  6 15:34:50 node-2 kernel: [    0.508986] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  6 15:34:50 node-2 kernel: [    0.509337] pnp: PnP ACPI: found 10 devices
Oct  6 15:34:50 node-2 kernel: [    0.509339] ACPI: bus type PNP unregistered
Oct  6 15:34:50 node-2 kernel: [    0.515610] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  6 15:34:50 node-2 kernel: [    0.515613] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  6 15:34:50 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  6 15:34:50 node-2 kernel: [    0.515615] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  6 15:34:50 node-2 kernel: [    0.515620] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  6 15:34:50 node-2 kernel: [    0.515621] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515636] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515665] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  6 15:34:50 node-2 kernel: [    0.515680] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515712] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  6 15:34:50 node-2 kernel: [    0.515727] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  6 15:34:50 node-2 kernel: [    0.515755] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  6 15:34:50 node-2 kernel: [    0.515770] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  6 15:34:50 node-2 kernel: [    0.515799] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  6 15:34:50 node-2 kernel: [    0.515801] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515815] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515844] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  6 15:34:50 node-2 kernel: [    0.515846] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515861] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515904] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  6 15:34:50 node-2 kernel: [    0.515905] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515908] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515912] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  6 15:34:50 node-2 kernel: [    0.515914] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515916] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515920] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  6 15:34:50 node-2 kernel: [    0.515925] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  6 15:34:50 node-2 kernel: [    0.515933] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  6 15:34:50 node-2 kernel: [    0.515936] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  6 15:34:50 node-2 kernel: [    0.515943] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  6 15:34:50 node-2 kernel: [    0.515944] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  6 15:34:50 node-2 kernel: [    0.515945] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  6 15:34:50 node-2 kernel: [    0.515945] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  6 15:34:50 node-2 kernel: [    0.515946] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  6 15:34:50 node-2 kernel: [    0.515947] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  6 15:34:50 node-2 kernel: [    0.515948] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  6 15:34:50 node-2 kernel: [    0.515949] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  6 15:34:50 node-2 kernel: [    0.515950] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515951] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515952] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515953] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515954] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515954] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515955] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515956] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515957] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  6 15:34:50 node-2 kernel: [    0.515958] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515959] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  6 15:34:50 node-2 kernel: [    0.515960] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  6 15:34:50 node-2 kernel: [    0.515961] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  6 15:34:50 node-2 kernel: [    0.515962] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  6 15:34:50 node-2 kernel: [    0.515964] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  6 15:34:50 node-2 kernel: [    0.515965] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  6 15:34:50 node-2 kernel: [    0.516002] NET: Registered protocol family 2
Oct  6 15:34:50 node-2 kernel: [    0.516262] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.516604] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.516752] TCP: Hash tables configured (established 262144 bind 65536)
Oct  6 15:34:50 node-2 kernel: [    0.516788] TCP: reno registered
Oct  6 15:34:50 node-2 kernel: [    0.516817] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.516914] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.517063] NET: Registered protocol family 1
Oct  6 15:34:50 node-2 kernel: [    0.556414] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  6 15:34:50 node-2 kernel: [    0.556421] PCI: CLS 64 bytes, default 64
Oct  6 15:34:50 node-2 kernel: [    0.556464] Trying to unpack rootfs image as initramfs...
Oct  6 15:34:50 node-2 kernel: [    0.775190] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct  6 15:34:50 node-2 kernel: [    0.775227] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  6 15:34:50 node-2 kernel: [    0.775229] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct  6 15:34:50 node-2 kernel: [    0.775631] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775637] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775642] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775647] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775659] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775676] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775691] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775706] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775718] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775728] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775734] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775741] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775750] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775762] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775775] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775787] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  6 15:34:50 node-2 kernel: [    0.775898] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  6 15:34:50 node-2 kernel: [    0.775904] Scanning for low memory corruption every 60 seconds
Oct  6 15:34:50 node-2 kernel: [    0.776369] Initialise system trusted keyring
Oct  6 15:34:50 node-2 kernel: [    0.776421] audit: initializing netlink socket (disabled)
Oct  6 15:34:50 node-2 kernel: [    0.776437] type=2000 audit(1475768054.728:1): initialized
Oct  6 15:34:50 node-2 kernel: [    0.794202] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  6 15:34:50 node-2 kernel: [    0.795731] zbud: loaded
Oct  6 15:34:50 node-2 kernel: [    0.795878] VFS: Disk quotas dquot_6.5.2
Oct  6 15:34:50 node-2 kernel: [    0.795914] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  6 15:34:50 node-2 kernel: [    0.796297] fuse init (API version 7.22)
Oct  6 15:34:50 node-2 kernel: [    0.796364] msgmni has been set to 32768
Oct  6 15:34:50 node-2 kernel: [    0.796413] Key type big_key registered
Oct  6 15:34:50 node-2 kernel: [    0.796965] Key type asymmetric registered
Oct  6 15:34:50 node-2 kernel: [    0.796966] Asymmetric key parser 'x509' registered
Oct  6 15:34:50 node-2 kernel: [    0.796989] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  6 15:34:50 node-2 kernel: [    0.797057] io scheduler noop registered
Oct  6 15:34:50 node-2 kernel: [    0.797059] io scheduler deadline registered (default)
Oct  6 15:34:50 node-2 kernel: [    0.797078] io scheduler cfq registered
Oct  6 15:34:50 node-2 kernel: [    0.797483] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    0.797604] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    0.797718] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    0.797825] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    0.797936] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    0.798080] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    0.798443] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  6 15:34:50 node-2 kernel: [    0.798468] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  6 15:34:50 node-2 kernel: [    0.798485] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  6 15:34:50 node-2 kernel: [    0.798494] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798496] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798499] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  6 15:34:50 node-2 kernel: [    0.798504] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798506] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798507] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798508] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798510] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798511] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798513] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798514] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798515] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798517] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798518] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798520] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798522] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  6 15:34:50 node-2 kernel: [    0.798533] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798535] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  6 15:34:50 node-2 kernel: [    0.798550] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798553] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  6 15:34:50 node-2 kernel: [    0.798564] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798566] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  6 15:34:50 node-2 kernel: [    0.798569] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  6 15:34:50 node-2 kernel: [    0.798619] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  6 15:34:50 node-2 kernel: [    0.798625] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  6 15:34:50 node-2 kernel: [    0.798630] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  6 15:34:50 node-2 kernel: [    0.798639] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  6 15:34:50 node-2 kernel: [    0.798679] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  6 15:34:50 node-2 kernel: [    0.798680] vesafb: scrolling: redraw
Oct  6 15:34:50 node-2 kernel: [    0.798682] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  6 15:34:50 node-2 kernel: [    0.819373] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  6 15:34:50 node-2 kernel: [    0.827881] Console: switching to colour frame buffer device 80x30
Oct  6 15:34:50 node-2 kernel: [    0.836551] fb0: VESA VGA frame buffer device
Oct  6 15:34:50 node-2 kernel: [    0.836749] intel_idle: MWAIT substates: 0x2120
Oct  6 15:34:50 node-2 kernel: [    0.836750] intel_idle: v0.4 model 0x3F
Oct  6 15:34:50 node-2 kernel: [    0.836751] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  6 15:34:50 node-2 kernel: [    0.836978] ipmi message handler version 39.2
Oct  6 15:34:50 node-2 kernel: [    0.837244] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  6 15:34:50 node-2 kernel: [    0.837679] ACPI: AC Adapter [P111] (on-line)
Oct  6 15:34:50 node-2 kernel: [    0.842897] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  6 15:34:50 node-2 kernel: [    0.853914] ACPI: Power Button [PWRB]
Oct  6 15:34:50 node-2 kernel: [    0.859682] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  6 15:34:50 node-2 kernel: [    0.871324] ACPI: Power Button [PWRF]
Oct  6 15:34:50 node-2 kernel: [    0.897922] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  6 15:34:50 node-2 kernel: [    0.909586] pstore: Registered erst as persistent store backend
Oct  6 15:34:50 node-2 kernel: [    0.915786] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  6 15:34:50 node-2 kernel: [    0.927717] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  6 15:34:50 node-2 kernel: [    0.954459] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  6 15:34:50 node-2 kernel: [    0.987726] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  6 15:34:50 node-2 kernel: [    1.001853] Linux agpgart interface v0.103
Oct  6 15:34:50 node-2 kernel: [    1.009479] brd: module loaded
Oct  6 15:34:50 node-2 kernel: [    1.016533] loop: module loaded
Oct  6 15:34:50 node-2 kernel: [    1.023235] libphy: Fixed MDIO Bus: probed
Oct  6 15:34:50 node-2 kernel: [    1.029767] tun: Universal TUN/TAP device driver, 1.6
Oct  6 15:34:50 node-2 kernel: [    1.036357] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  6 15:34:50 node-2 kernel: [    1.042855] PPP generic driver version 2.4.2
Oct  6 15:34:50 node-2 kernel: [    1.049225] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  6 15:34:50 node-2 kernel: [    1.055630] ehci-pci: EHCI PCI platform driver
Oct  6 15:34:50 node-2 kernel: [    1.062126] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  6 15:34:50 node-2 kernel: [    1.068517] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  6 15:34:50 node-2 kernel: [    1.081003] ehci-pci 0000:00:1a.0: debug port 2
Oct  6 15:34:50 node-2 kernel: [    1.091181] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  6 15:34:50 node-2 kernel: [    1.091201] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  6 15:34:50 node-2 kernel: [    1.107858] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  6 15:34:50 node-2 kernel: [    1.113916] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  6 15:34:50 node-2 kernel: [    1.120079] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  6 15:34:50 node-2 kernel: [    1.131946] usb usb1: Product: EHCI Host Controller
Oct  6 15:34:50 node-2 kernel: [    1.137999] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  6 15:34:50 node-2 kernel: [    1.144050] usb usb1: SerialNumber: 0000:00:1a.0
Oct  6 15:34:50 node-2 kernel: [    1.149990] hub 1-0:1.0: USB hub found
Oct  6 15:34:50 node-2 kernel: [    1.155736] hub 1-0:1.0: 2 ports detected
Oct  6 15:34:50 node-2 kernel: [    1.161513] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  6 15:34:50 node-2 kernel: [    1.167082] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  6 15:34:50 node-2 kernel: [    1.177939] ehci-pci 0000:00:1d.0: debug port 2
Oct  6 15:34:50 node-2 kernel: [    1.187228] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  6 15:34:50 node-2 kernel: [    1.187231] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  6 15:34:50 node-2 kernel: [    1.203777] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  6 15:34:50 node-2 kernel: [    1.208971] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  6 15:34:50 node-2 kernel: [    1.214251] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  6 15:34:50 node-2 kernel: [    1.224797] usb usb2: Product: EHCI Host Controller
Oct  6 15:34:50 node-2 kernel: [    1.230257] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  6 15:34:50 node-2 kernel: [    1.235791] usb usb2: SerialNumber: 0000:00:1d.0
Oct  6 15:34:50 node-2 kernel: [    1.241292] hub 2-0:1.0: USB hub found
Oct  6 15:34:50 node-2 kernel: [    1.246631] hub 2-0:1.0: 2 ports detected
Oct  6 15:34:50 node-2 kernel: [    1.251928] ehci-platform: EHCI generic platform driver
Oct  6 15:34:50 node-2 kernel: [    1.257193] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  6 15:34:50 node-2 kernel: [    1.262516] ohci-pci: OHCI PCI platform driver
Oct  6 15:34:50 node-2 kernel: [    1.267835] ohci-platform: OHCI generic platform driver
Oct  6 15:34:50 node-2 kernel: [    1.273064] uhci_hcd: USB Universal Host Controller Interface driver
Oct  6 15:34:50 node-2 kernel: [    1.278431] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  6 15:34:50 node-2 kernel: [    1.471556] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  6 15:34:50 node-2 kernel: [    1.771360] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  6 15:34:50 node-2 kernel: [    1.787583] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  6 15:34:50 node-2 kernel: [    1.793190] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  6 15:34:50 node-2 kernel: [    1.798850] hub 1-1:1.0: USB hub found
Oct  6 15:34:50 node-2 kernel: [    1.804319] hub 1-1:1.0: 6 ports detected
Oct  6 15:34:50 node-2 kernel: [    1.919196] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  6 15:34:50 node-2 kernel: [    2.317455] i8042: No controller found
Oct  6 15:34:50 node-2 kernel: [    2.322987] mousedev: PS/2 mouse device common for all mice
Oct  6 15:34:50 node-2 kernel: [    2.328692] rtc_cmos 00:02: RTC can wake from S4
Oct  6 15:34:50 node-2 kernel: [    2.334415] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  6 15:34:50 node-2 kernel: [    2.335565] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  6 15:34:50 node-2 kernel: [    2.335566] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  6 15:34:50 node-2 kernel: [    2.336201] hub 2-1:1.0: USB hub found
Oct  6 15:34:50 node-2 kernel: [    2.336427] hub 2-1:1.0: 8 ports detected
Oct  6 15:34:50 node-2 kernel: [    2.362545] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  6 15:34:50 node-2 kernel: [    2.373842] device-mapper: uevent: version 1.0.3
Oct  6 15:34:50 node-2 kernel: [    2.379563] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  6 15:34:50 node-2 kernel: [    2.390929] ledtrig-cpu: registered to indicate activity on CPUs
Oct  6 15:34:50 node-2 kernel: [    2.396904] TCP: cubic registered
Oct  6 15:34:50 node-2 kernel: [    2.402767] NET: Registered protocol family 10
Oct  6 15:34:50 node-2 kernel: [    2.408852] NET: Registered protocol family 17
Oct  6 15:34:50 node-2 kernel: [    2.414623] Key type dns_resolver registered
Oct  6 15:34:50 node-2 kernel: [    2.420681] Loading compiled-in X.509 certificates
Oct  6 15:34:50 node-2 kernel: [    2.426906] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  6 15:34:50 node-2 kernel: [    2.438549] registered taskstats version 1
Oct  6 15:34:50 node-2 kernel: [    2.446600] Key type trusted registered
Oct  6 15:34:50 node-2 kernel: [    2.454209] Key type encrypted registered
Oct  6 15:34:50 node-2 kernel: [    2.459725] AppArmor: AppArmor sha1 policy hashing enabled
Oct  6 15:34:50 node-2 kernel: [    2.465269] IMA: No TPM chip found, activating TPM-bypass!
Oct  6 15:34:50 node-2 kernel: [    2.471407] regulator-dummy: disabling
Oct  6 15:34:50 node-2 kernel: [    2.476963]   Magic number: 4:96:588
Oct  6 15:34:50 node-2 kernel: [    2.482529] pci_bus 0000:09: hash matches
Oct  6 15:34:50 node-2 kernel: [    2.488204] rtc_cmos 00:02: setting system clock to 2016-10-06 15:34:16 UTC (1475768056)
Oct  6 15:34:50 node-2 kernel: [    2.500582] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  6 15:34:50 node-2 kernel: [    2.506190] EDD information not available.
Oct  6 15:34:50 node-2 kernel: [    2.511803] PM: Hibernation image not present or could not be loaded.
Oct  6 15:34:50 node-2 kernel: [    2.512666] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  6 15:34:50 node-2 kernel: [    2.523943] Write protecting the kernel read-only data: 12288k
Oct  6 15:34:50 node-2 kernel: [    2.530215] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  6 15:34:50 node-2 kernel: [    2.543086] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  6 15:34:50 node-2 kernel: [    2.575009] device-mapper: multipath: version 1.6.0 loaded
Oct  6 15:34:50 node-2 kernel: [    2.582777] systemd-udevd[216]: starting version 204
Oct  6 15:34:50 node-2 kernel: [    2.604793] md: linear personality registered for level -1
Oct  6 15:34:50 node-2 kernel: [    2.610783] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  6 15:34:50 node-2 kernel: [    2.625446] md: multipath personality registered for level -4
Oct  6 15:34:50 node-2 kernel: [    2.633720] md: raid0 personality registered for level 0
Oct  6 15:34:50 node-2 kernel: [    2.642279] md: raid1 personality registered for level 1
Oct  6 15:34:50 node-2 kernel: [    2.648643] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  6 15:34:50 node-2 kernel: [    2.655052] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  6 15:34:50 node-2 kernel: [    2.654985] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  6 15:34:50 node-2 kernel: [    2.674634] megasas: FW now in Ready state
Oct  6 15:34:50 node-2 kernel: [    2.681056] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681062] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681067] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681073] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681079] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681084] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681089] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681095] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681104] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681110] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681115] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681120] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681125] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681131] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681136] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681143] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.681186] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  6 15:34:50 node-2 kernel: [    2.685133] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct  6 15:34:50 node-2 kernel: [    2.685158] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct  6 15:34:50 node-2 kernel: [    2.685178] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  6 15:34:50 node-2 kernel: [    2.685435] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.685530] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.685705] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.685797] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.686067] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.702734] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct  6 15:34:50 node-2 kernel: [    2.702756] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct  6 15:34:50 node-2 kernel: [    2.702796] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  6 15:34:50 node-2 kernel: [    2.703091] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.703242] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.703609] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.703789] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.703895] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.703929] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.704251] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.719768] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct  6 15:34:50 node-2 kernel: [    2.719795] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct  6 15:34:50 node-2 kernel: [    2.719802] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  6 15:34:50 node-2 kernel: [    2.719910] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.720026] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.720120] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.720196] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.720394] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.722557] raid6: sse2x1   11335 MB/s
Oct  6 15:34:50 node-2 kernel: [    2.733058] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct  6 15:34:50 node-2 kernel: [    2.733066] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct  6 15:34:50 node-2 kernel: [    2.733067] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  6 15:34:50 node-2 kernel: [    2.733331] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.733416] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.733555] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.733720] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.734014] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  6 15:34:50 node-2 kernel: [    2.746884] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  6 15:34:50 node-2 kernel: [    2.746895] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  6 15:34:50 node-2 kernel: [    2.746912] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  6 15:34:50 node-2 kernel: [    2.746934] usb 2-1.4: Manufacturer: Avocent
Oct  6 15:34:50 node-2 kernel: [    2.746935] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  6 15:34:50 node-2 kernel: [    2.790546] raid6: sse2x2   14263 MB/s
Oct  6 15:34:50 node-2 kernel: [    2.858471] raid6: sse2x4   16726 MB/s
Oct  6 15:34:50 node-2 kernel: [    2.926416] raid6: avx2x1   22260 MB/s
Oct  6 15:34:50 node-2 kernel: [    2.994273] raid6: avx2x2   20876 MB/s
Oct  6 15:34:50 node-2 kernel: [    3.066204] raid6: avx2x4   21372 MB/s
Oct  6 15:34:50 node-2 kernel: [    3.071882] raid6: using algorithm avx2x1 (22260 MB/s)
Oct  6 15:34:50 node-2 kernel: [    3.077499] raid6: using avx2x2 recovery algorithm
Oct  6 15:34:50 node-2 kernel: [    3.083185] Switched to clocksource tsc
Oct  6 15:34:50 node-2 kernel: [    3.089534] xor: automatically using best checksumming function:
Oct  6 15:34:50 node-2 kernel: [    3.099342] hidraw: raw HID events driver (C) Jiri Kosina
Oct  6 15:34:50 node-2 kernel: [    3.107504] usbcore: registered new interface driver usbhid
Oct  6 15:34:50 node-2 kernel: [    3.112913] usbhid: USB HID core driver
Oct  6 15:34:50 node-2 kernel: [    3.119033] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Oct  6 15:34:50 node-2 kernel: [    3.129985] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Oct  6 15:34:50 node-2 kernel: [    3.134156]    avx       : 35553.000 MB/sec
Oct  6 15:34:50 node-2 kernel: [    3.147088] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Oct  6 15:34:50 node-2 kernel: [    3.158622] async_tx: api initialized (async)
Oct  6 15:34:50 node-2 kernel: [    3.158709] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Oct  6 15:34:50 node-2 kernel: [    3.159273] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Oct  6 15:34:50 node-2 kernel: [    3.160139] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Oct  6 15:34:50 node-2 kernel: [    3.203715] md: raid6 personality registered for level 6
Oct  6 15:34:50 node-2 kernel: [    3.209805] md: raid5 personality registered for level 5
Oct  6 15:34:50 node-2 kernel: [    3.215851] md: raid4 personality registered for level 4
Oct  6 15:34:50 node-2 kernel: [    3.224817] md: raid10 personality registered for level 10
Oct  6 15:34:50 node-2 kernel: [    3.278558] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Oct  6 15:34:50 node-2 kernel: [    3.417956] megasas:IOC Init cmd success
Oct  6 15:34:50 node-2 kernel: [    3.445935] megasas: INIT adapter done
Oct  6 15:34:50 node-2 kernel: [    3.545854] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  6 15:34:50 node-2 kernel: [    3.552847] scsi0 : LSI SAS based MegaRAID driver
Oct  6 15:34:50 node-2 kernel: [    3.560375] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  6 15:34:50 node-2 kernel: [    3.579568] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  6 15:34:50 node-2 kernel: [    3.595008] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  6 15:34:50 node-2 kernel: [    3.601658] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  6 15:34:50 node-2 kernel: [    3.614809] sd 0:2:0:0: [sda] Write Protect is off
Oct  6 15:34:50 node-2 kernel: [    3.621249] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  6 15:34:50 node-2 kernel: [    3.621269] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  6 15:34:50 node-2 kernel: [    3.663529]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct  6 15:34:50 node-2 kernel: [    3.670280] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  6 15:34:50 node-2 kernel: [    3.796702] random: lvm urandom read with 29 bits of entropy available
Oct  6 15:34:50 node-2 kernel: [    3.953127] bio: create slab <bio-1> at 1
Oct  6 15:34:50 node-2 kernel: [    4.706786] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  6 15:34:50 node-2 kernel: [    5.286286] init: plymouth-upstart-bridge main process (554) terminated with status 1
Oct  6 15:34:50 node-2 kernel: [    5.298749] init: plymouth-upstart-bridge main process ended, respawning
Oct  6 15:34:50 node-2 kernel: [    5.440237] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  6 15:34:50 node-2 kernel: [    5.526503] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  6 15:34:50 node-2 kernel: [    5.658957] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  6 15:34:50 node-2 kernel: [    5.694896] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  6 15:34:50 node-2 kernel: [    5.750988] random: nonblocking pool is initialized
Oct  6 15:34:50 node-2 kernel: [    5.830021] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  6 15:34:50 node-2 kernel: [    5.972607] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  6 15:34:50 node-2 kernel: [    6.017026] XFS (dm-0): Mounting Filesystem
Oct  6 15:34:50 node-2 kernel: [    6.295324] XFS (dm-0): Ending clean mount
Oct  6 15:34:50 node-2 kernel: [    6.363116] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  6 15:34:50 node-2 kernel: [    6.388013] XFS (dm-1): Mounting Filesystem
Oct  6 15:34:50 node-2 kernel: [    6.556987] XFS (dm-1): Ending clean mount
Oct  6 15:34:50 node-2 kernel: [    8.252524] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  6 15:34:50 node-2 kernel: [    8.276564] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  6 15:34:50 node-2 kernel: [    8.448535] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  6 15:34:50 node-2 kernel: [    8.448540] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  6 15:34:50 node-2 kernel: [    8.448543] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  6 15:34:50 node-2 kernel: [    8.448547] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  6 15:34:50 node-2 kernel: [    8.492236] systemd-udevd[781]: starting version 204
Oct  6 15:34:50 node-2 kernel: [    8.680214] power_meter ACPI000D:00: Found ACPI power meter.
Oct  6 15:34:50 node-2 kernel: [    8.680223] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  6 15:34:50 node-2 kernel: [    8.688239] wmi: Mapper loaded
Oct  6 15:34:50 node-2 kernel: [    8.705586] IPMI System Interface driver.
Oct  6 15:34:50 node-2 kernel: [    8.705634] ipmi_si: probing via ACPI
Oct  6 15:34:50 node-2 kernel: [    8.705646] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  6 15:34:50 node-2 kernel: [    8.705646] ipmi_si: Adding ACPI-specified kcs state machine
Oct  6 15:34:50 node-2 kernel: [    8.705655] ipmi_si: probing via SMBIOS
Oct  6 15:34:50 node-2 kernel: [    8.705656] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  6 15:34:50 node-2 kernel: [    8.705656] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  6 15:34:50 node-2 kernel: [    8.705658] ipmi_si: probing via SPMI
Oct  6 15:34:50 node-2 kernel: [    8.705658] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  6 15:34:50 node-2 kernel: [    8.705659] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  6 15:34:50 node-2 kernel: [    8.705660] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  6 15:34:50 node-2 kernel: [    8.718614] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  6 15:34:50 node-2 kernel: [    8.718619] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  6 15:34:50 node-2 kernel: [    8.718622] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  6 15:34:50 node-2 kernel: [    8.718623] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  6 15:34:50 node-2 kernel: [    8.718635] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  6 15:34:50 node-2 kernel: [    8.737056] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  6 15:34:50 node-2 kernel: [    8.809786] systemd-udevd[799]: renamed network interface eth2 to enp8s0
Oct  6 15:34:50 node-2 kernel: [    8.833646] systemd-udevd[801]: renamed network interface eth3 to enp9s0
Oct  6 15:34:50 node-2 kernel: [    8.861685] systemd-udevd[810]: renamed network interface eth1 to enp7s0
Oct  6 15:34:50 node-2 kernel: [    8.877665] systemd-udevd[800]: renamed network interface eth0 to enp6s0
Oct  6 15:34:50 node-2 kernel: [    8.879245] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  6 15:34:50 node-2 kernel: [    8.879250] ipmi_si 00:09: IPMI kcs interface initialized
Oct  6 15:34:50 node-2 kernel: [    9.223385] type=1400 audit(1475768063.236:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1043 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.223541] type=1400 audit(1475768063.236:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1043 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.223666] type=1400 audit(1475768063.236:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1043 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.243335] type=1400 audit(1475768063.256:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.243473] type=1400 audit(1475768063.256:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.243593] type=1400 audit(1475768063.256:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.266375] type=1400 audit(1475768063.280:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.266512] type=1400 audit(1475768063.280:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1057 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.266628] type=1400 audit(1475768063.280:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1057 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.269082] type=1400 audit(1475768063.284:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Oct  6 15:34:50 node-2 kernel: [    9.816315] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  6 15:34:50 node-2 kernel: [    9.816945] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  6 15:34:50 node-2 kernel: [   10.014219] enic 0000:06:00.0 enp6s0: Link UP
Oct  6 15:34:50 node-2 kernel: [   10.014739] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  6 15:34:50 node-2 kernel: [   10.014748] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  6 15:34:50 node-2 kernel: [   19.143827] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  6 15:34:52 node-2 failsafe: Failsafe of 120 seconds reached.
Oct  6 15:34:52 node-2 kernel: [   38.138810] init: failsafe main process (8415) killed by TERM signal
Oct  6 15:34:52 node-2 dbus[8454]: [system] AppArmor D-Bus mediation is enabled
Oct  6 15:34:52 node-2 kernel: [   38.332890] audit_printk_skb: 30 callbacks suppressed
Oct  6 15:34:52 node-2 kernel: [   38.332890] type=1400 audit(1475768092.453:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8541 comm="apparmor_parser"
Oct  6 15:34:52 node-2 kernel: [   38.333685] type=1400 audit(1475768092.453:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8540 comm="apparmor_parser"
Oct  6 15:34:52 node-2 kernel: [   38.333719] type=1400 audit(1475768092.453:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8540 comm="apparmor_parser"
Oct  6 15:34:52 node-2 kernel: [   38.333724] type=1400 audit(1475768092.453:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8540 comm="apparmor_parser"
Oct  6 15:34:52 node-2 kernel: [   38.335123] type=1400 audit(1475768092.453:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8540 comm="apparmor_parser"
Oct  6 15:34:52 node-2 kernel: [   38.335162] type=1400 audit(1475768092.453:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8540 comm="apparmor_parser"
Oct  6 15:34:52 node-2 kernel: [   38.335890] type=1400 audit(1475768092.453:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8540 comm="apparmor_parser"
Oct  6 15:34:52 node-2 kernel: [   38.416467] type=1400 audit(1475768092.537:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8543 comm="apparmor_parser"
Oct  6 15:34:52 node-2 cron[8573]: (CRON) INFO (pidfile fd = 3)
Oct  6 15:34:52 node-2 anacron[8589]: Anacron 2.3 started on 2016-10-06
Oct  6 15:34:52 node-2 cron[8610]: (CRON) STARTUP (fork ok)
Oct  6 15:34:52 node-2 anacron[8589]: Will run job `cron.daily' in 5 min.
Oct  6 15:34:52 node-2 anacron[8589]: Will run job `cron.weekly' in 10 min.
Oct  6 15:34:52 node-2 anacron[8589]: Will run job `cron.monthly' in 15 min.
Oct  6 15:34:52 node-2 anacron[8589]: Jobs will be executed sequentially
Oct  6 15:34:52 node-2 multipathd: path checkers start up
Oct  6 15:34:52 node-2 cron[8610]: (CRON) INFO (Running @reboot jobs)
Oct  6 15:34:53 node-2 postfix/master[8752]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  6 15:34:56 node-2 puppet-agent[9065]: Reopening log files
Oct  6 15:34:56 node-2 puppet-agent[9065]: Could not request certificate: Connection refused - connect(2)
Oct  6 15:35:01 node-2 CRON[9096]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct  6 15:35:10 node-2 puppet-user[9335]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  6 15:35:10 node-2 puppet-user[9335]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct  6 15:35:11 node-2 puppet-user[9335]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  6 15:35:11 node-2 puppet-user[9335]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  6 15:35:11 node-2 puppet-user[9335]: Finished catalog run in 0.88 seconds
Oct  6 15:35:11 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  6 15:35:11 node-2 nailgun-agent: D, [2016-10-06T15:35:01.946501 #9099] DEBUG -- : Sleep for 10 seconds before sending request
Oct  6 15:35:11 node-2 nailgun-agent: I, [2016-10-06T15:35:11.960873 #9099]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  6 15:35:12 node-2 nailgun-agent: D, [2016-10-06T15:35:12.388334 #9099] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct  6 15:35:12 node-2 multipathd: uevent trigger error
Oct  6 15:35:12 node-2 puppet-user[9770]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  6 15:35:12 node-2 puppet-user[9770]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  6 15:35:12 node-2 puppet-user[9770]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  6 15:35:12 node-2 puppet-user[9770]: Finished catalog run in 0.08 seconds
Oct  6 15:35:14 node-2 puppet-user[10365]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  6 15:35:14 node-2 puppet-user[10365]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Oct  6 15:35:14 node-2 puppet-user[10365]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  6 15:35:14 node-2 puppet-user[10365]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  6 15:35:14 node-2 puppet-user[10365]: Finished catalog run in 0.04 seconds
Oct  6 15:35:16 node-2 puppet-user[10836]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  6 15:35:16 node-2 puppet-user[10836]: Compiled catalog for node-2.domain.tld in environment production in 0.04 seconds
Oct  6 15:35:16 node-2 puppet-user[10836]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  6 15:35:16 node-2 puppet-user[10836]: Finished catalog run in 0.04 seconds
Oct  6 15:35:17 node-2 puppet-user[11302]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  6 15:35:18 node-2 puppet-user[11302]: Compiled catalog for node-2.domain.tld in environment production in 0.23 seconds
Oct  6 15:35:18 node-2 puppet-user[11302]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  6 15:35:18 node-2 puppet-user[11302]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Oct  6 15:35:19 node-2 puppet-user[11302]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Oct  6 15:35:19 node-2 puppet-user[11302]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Oct  6 15:35:19 node-2 puppet-user[11302]: Finished catalog run in 1.19 seconds
Oct  6 15:35:20 node-2 puppet-user[11846]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  6 15:35:20 node-2 kernel: [   66.842277] init: plymouth-upstart-bridge main process ended, respawning
Oct  6 15:35:21 node-2 puppet-user[11846]: Compiled catalog for node-2.domain.tld in environment production in 0.28 seconds
Oct  6 15:35:21 node-2 puppet-agent[9065]: Could not run: SIGTERM
Oct  6 15:35:21 node-2 puppet-user[11846]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Oct  6 15:35:21 node-2 puppet-user[11846]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Oct  6 15:35:21 node-2 kernel: [   67.108450] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  6 15:35:21 node-2 puppet-user[11846]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  6 15:35:21 node-2 puppet-user[11846]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  6 15:35:21 node-2 puppet-user[11846]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Oct  6 15:35:21 node-2 ec2: 
Oct  6 15:35:21 node-2 ec2: #############################################################
Oct  6 15:35:21 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  6 15:35:21 node-2 ec2: 1024 23:b7:a1:c1:84:89:0a:da:8d:8f:2a:cf:5c:0f:6a:21  root@node-2.domain.tld (DSA)
Oct  6 15:35:21 node-2 ec2: 256 77:95:ed:99:c9:3a:51:55:96:af:86:91:69:84:aa:2a  root@node-2.domain.tld (ECDSA)
Oct  6 15:35:21 node-2 ec2: 256 f5:db:55:34:b2:a3:cf:87:4b:59:44:f2:93:4a:d2:82  root@node-2.domain.tld (ED25519)
Oct  6 15:35:21 node-2 ec2: 2048 c8:64:5e:a2:86:0d:8e:ce:33:cf:bc:94:e7:bb:67:c6  root@node-2.domain.tld (RSA)
Oct  6 15:35:21 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  6 15:35:21 node-2 ec2: #############################################################
Oct  6 15:35:21 node-2 puppet-user[11846]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  6 15:35:21 node-2 puppet-user[11846]: Finished catalog run in 0.59 seconds
Oct  6 15:35:23 node-2 puppet-user[12503]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  6 15:35:23 node-2 puppet-user[12503]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Oct  6 15:35:23 node-2 puppet-user[12503]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  6 15:35:23 node-2 kernel: [   69.296334] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  6 15:35:23 node-2 kernel: [   69.296386] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Oct  6 15:35:23 node-2 puppet-user[12503]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Oct  6 15:35:23 node-2 puppet-user[12503]: Finished catalog run in 0.05 seconds
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.371809 #9099] DEBUG -- : Trying to find block devices
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.371902 #9099] DEBUG -- : Found block device: sda
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.371948 #9099] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.371999 #9099] DEBUG -- : Trying to get list of physical devices
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.372148 #9099] DEBUG -- : Getting udev properties for device: sda
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.374142 #9099] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Oct  6 15:35:24 node-2 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24438", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.374181 #9099] DEBUG -- : Trying to find out if device sda is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.374226 #9099] DEBUG -- : Device sda removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.374243 #9099] DEBUG -- : Device sda seems to be appropriate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.374718 #9099] DEBUG -- : Getting udev properties for device: dm-0
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.376665 #9099] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-bD73X1ezupbcI9Smw2zzBOn0FZUpASc4fiD4wt53xqObMP3I0n0hgfrw78PN4YP1 /dev/disk/by-uuid/ee06e4c8-d844-499f-8a1e-1d540b936227 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-bD73X1ezupbcI9Smw2zzBOn0FZUpASc4fiD4wt53xqObMP3I0n0hgfrw78PN4YP1", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ee06e4c8-d844-499f-8a1e-1d540b936227", "ID_FS_UUID_ENC"=>"ee06e4c8-d844-499f-8a1e-1d540b936227", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7656", "nomdmonddf"=>"1", "nomdm
Oct  6 15:35:24 node-2 nailgun-agent: onisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.376706 #9099] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.376740 #9099] DEBUG -- : Device dm-0 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.376755 #9099] DEBUG -- : Device dm-0 seems to be appropriate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.376770 #9099] DEBUG -- : Getting udev properties for device: dm-1
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.378517 #9099] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-xuj7b2NR2OTYXD5dIh2RISf2LX9L9LLcg3uwe24M7BJwL1G9rfa7kBowch3pqsue /dev/disk/by-uuid/8311a025-c1d3-412d-8507-4e08e8aecb9c /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-xuj7b2NR2OTYXD5dIh2RISf2LX9L9LLcg3uwe24M7BJwL1G9rfa7kBowch3pqsue", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8311a025-c1d3-412d-8507-4e08e8aecb9c", "ID_FS_UUID_ENC"=>"8311a025-c1d3-412d-8507-4e08e8aecb9c", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36
Oct  6 15:35:24 node-2 nailgun-agent: 780", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.378545 #9099] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.378577 #9099] DEBUG -- : Device dm-1 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.378591 #9099] DEBUG -- : Device dm-1 seems to be appropriate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.378607 #9099] DEBUG -- : Getting udev properties for device: dm-2
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.380306 #9099] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-InGJU1qfldORJHK43x8lfI6VWZScUDGuesYBsR4RI6mT3d0PatsAAWv65ncwe1qp /dev/disk/by-uuid/52137152-20f6-43d8-88d9-61e778db1566 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-InGJU1qfldORJHK43x8lfI6VWZScUDGuesYBsR4RI6mT3d0PatsAAWv65ncwe1qp", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"52137152-20f6-43d8-88d9-61e778db1566", "ID_FS_UUID_ENC"=>"52137152-20f6-43d8-88d9-61e778db1566", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"41675", "nomdmond
Oct  6 15:35:24 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.380334 #9099] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.380380 #9099] DEBUG -- : Device dm-2 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.380396 #9099] DEBUG -- : Device dm-2 seems to be appropriate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.380411 #9099] DEBUG -- : Getting udev properties for device: dm-3
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.382043 #9099] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-yzg1CHYvuVu1SCsirJ2naWtMf4t1nFuXYr5h2IXRwqifaz0sdgIqOM9K1WsMeWdm /dev/disk/by-uuid/4b5b8436-74bf-4aea-a4cb-61ab1dc936d0 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-yzg1CHYvuVu1SCsirJ2naWtMf4t1nFuXYr5h2IXRwqifaz0sdgIqOM9K1WsMeWdm", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4b5b8436-74bf-4aea-a4cb-61ab1dc936d0", "ID_FS_UUID_ENC"=>"4b5b8436-74bf-4aea-a4cb-61ab1dc936d0", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40310", "nomdmonddf"=>"1", 
Oct  6 15:35:24 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.382070 #9099] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.382136 #9099] DEBUG -- : Device dm-3 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.382151 #9099] DEBUG -- : Device dm-3 seems to be appropriate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.382165 #9099] DEBUG -- : Getting udev properties for device: dm-4
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.383942 #9099] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-zipgnwo1KwZccOL4jcHh3i8MyLgd9i4PTVUnLCqHYW4fWyIjEmRvQvYOCTDSAWdL /dev/disk/by-uuid/f3f3f058-77c1-482c-aabc-2f2c3689ab97 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-zipgnwo1KwZccOL4jcHh3i8MyLgd9i4PTVUnLCqHYW4fWyIjEmRvQvYOCTDSAWdL", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f3f3f058-77c1-482c-aabc-2f2c3689ab97", "ID_FS_UUID_ENC"=>"f3f3f058-77c1-482c-aabc-2f2c3689ab97", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48313", "nomdmonddf"=>"1", "nomd
Oct  6 15:35:24 node-2 nailgun-agent: monisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.383972 #9099] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.384011 #9099] DEBUG -- : Device dm-4 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.384029 #9099] DEBUG -- : Device dm-4 seems to be appropriate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.384047 #9099] DEBUG -- : Getting udev properties for device: dm-5
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.385902 #9099] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-zipgnwo1KwZccOL4jcHh3i8MyLgd9i4PaMEtVxMsPlYSKeDGGVBlJg0vVhma89W2 /dev/disk/by-uuid/489e1f97-b93b-4a78-b506-3f26ec886548 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-zipgnwo1KwZccOL4jcHh3i8MyLgd9i4PaMEtVxMsPlYSKeDGGVBlJg0vVhma89W2", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"489e1f97-b93b-4a78-b506-3f26ec886548", "ID_FS_UUID_ENC"=>"489e1f97-b93b-4a78-b506-3f26ec886548", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48770", "nomdmonddf"=>"1", "nomdmonisw"
Oct  6 15:35:24 node-2 nailgun-agent: =>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.385926 #9099] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.385973 #9099] DEBUG -- : Device dm-5 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.385987 #9099] DEBUG -- : Device dm-5 seems to be appropriate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.386002 #9099] DEBUG -- : Getting udev properties for device: ram0
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.387497 #9099] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43511", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.387520 #9099] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.387564 #9099] DEBUG -- : Device ram0 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.387583 #9099] DEBUG -- : Getting udev properties for device: ram1
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.389048 #9099] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43518", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.389069 #9099] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.389131 #9099] DEBUG -- : Device ram1 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.389150 #9099] DEBUG -- : Getting udev properties for device: ram2
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.390585 #9099] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43576", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.390643 #9099] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.390684 #9099] DEBUG -- : Device ram2 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.390703 #9099] DEBUG -- : Getting udev properties for device: ram3
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.392142 #9099] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43586", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.392163 #9099] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.392204 #9099] DEBUG -- : Device ram3 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.392232 #9099] DEBUG -- : Getting udev properties for device: ram4
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.393949 #9099] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43596", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.393976 #9099] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.394010 #9099] DEBUG -- : Device ram4 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.394031 #9099] DEBUG -- : Getting udev properties for device: ram5
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.398303 #9099] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43605", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.398329 #9099] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.398406 #9099] DEBUG -- : Device ram5 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.398427 #9099] DEBUG -- : Getting udev properties for device: ram6
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.400215 #9099] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43618", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.400249 #9099] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.400311 #9099] DEBUG -- : Device ram6 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.400352 #9099] DEBUG -- : Getting udev properties for device: ram7
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.402118 #9099] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43632", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.402145 #9099] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.402196 #9099] DEBUG -- : Device ram7 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.402217 #9099] DEBUG -- : Getting udev properties for device: ram8
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.403695 #9099] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43644", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.403720 #9099] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.403770 #9099] DEBUG -- : Device ram8 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.403791 #9099] DEBUG -- : Getting udev properties for device: ram9
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.405290 #9099] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43653", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.405316 #9099] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.405361 #9099] DEBUG -- : Device ram9 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.405382 #9099] DEBUG -- : Getting udev properties for device: loop0
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.406923 #9099] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43455", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.406949 #9099] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.406993 #9099] DEBUG -- : Device loop0 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.407014 #9099] DEBUG -- : Getting udev properties for device: loop1
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.410064 #9099] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43463", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.410110 #9099] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.410145 #9099] DEBUG -- : Device loop1 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.410172 #9099] DEBUG -- : Getting udev properties for device: loop2
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.411729 #9099] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43471", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.411752 #9099] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.411809 #9099] DEBUG -- : Device loop2 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.411830 #9099] DEBUG -- : Getting udev properties for device: loop3
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.413297 #9099] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43479", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.413335 #9099] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.413379 #9099] DEBUG -- : Device loop3 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.413402 #9099] DEBUG -- : Getting udev properties for device: loop4
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.414844 #9099] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43485", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.414899 #9099] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.414946 #9099] DEBUG -- : Device loop4 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.414965 #9099] DEBUG -- : Getting udev properties for device: loop5
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.416412 #9099] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43491", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.416433 #9099] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.416472 #9099] DEBUG -- : Device loop5 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.416500 #9099] DEBUG -- : Getting udev properties for device: loop6
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.417983 #9099] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43498", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.418011 #9099] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.418043 #9099] DEBUG -- : Device loop6 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.418073 #9099] DEBUG -- : Getting udev properties for device: loop7
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.419709 #9099] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43505", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.419746 #9099] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.419800 #9099] DEBUG -- : Device loop7 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.419838 #9099] DEBUG -- : Getting udev properties for device: ram10
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.426027 #9099] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43526", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.426055 #9099] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.426095 #9099] DEBUG -- : Device ram10 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.426115 #9099] DEBUG -- : Getting udev properties for device: ram11
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.427736 #9099] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43533", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.427791 #9099] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.427832 #9099] DEBUG -- : Device ram11 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.427851 #9099] DEBUG -- : Getting udev properties for device: ram12
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.429273 #9099] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43540", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.429299 #9099] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.429362 #9099] DEBUG -- : Device ram12 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.429383 #9099] DEBUG -- : Getting udev properties for device: ram13
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.430769 #9099] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43547", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.430790 #9099] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.430820 #9099] DEBUG -- : Device ram13 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.430861 #9099] DEBUG -- : Getting udev properties for device: ram14
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.432419 #9099] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43555", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.432450 #9099] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.432485 #9099] DEBUG -- : Device ram14 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.432507 #9099] DEBUG -- : Getting udev properties for device: ram15
Oct  6 15:35:24 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434267 #9099] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43567", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434294 #9099] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434325 #9099] DEBUG -- : Device ram15 removable parameter: "0"
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434365 #9099] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434380 #9099] DEBUG -- : Block device seems to be physical data storage: sda
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434424 #9099] DEBUG -- : Found block device: dm-0
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434475 #9099] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434489 #9099] DEBUG -- : Found block device: dm-1
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434501 #9099] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434511 #9099] DEBUG -- : Found block device: dm-2
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434521 #9099] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434530 #9099] DEBUG -- : Found block device: dm-3
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434540 #9099] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434549 #9099] DEBUG -- : Found block device: dm-4
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434560 #9099] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434569 #9099] DEBUG -- : Found block device: dm-5
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434611 #9099] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434621 #9099] DEBUG -- : Found block device: ram0
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434632 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434641 #9099] DEBUG -- : Found block device: ram1
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434651 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434660 #9099] DEBUG -- : Found block device: ram2
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434670 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434678 #9099] DEBUG -- : Found block device: ram3
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434689 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434697 #9099] DEBUG -- : Found block device: ram4
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434707 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434755 #9099] DEBUG -- : Found block device: ram5
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434766 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434775 #9099] DEBUG -- : Found block device: ram6
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434786 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434795 #9099] DEBUG -- : Found block device: ram7
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434806 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434814 #9099] DEBUG -- : Found block device: ram8
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434825 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434834 #9099] DEBUG -- : Found block device: ram9
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434890 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434900 #9099] DEBUG -- : Found block device: loop0
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434910 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434918 #9099] DEBUG -- : Found block device: loop1
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434929 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434938 #9099] DEBUG -- : Found block device: loop2
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434948 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434957 #9099] DEBUG -- : Found block device: loop3
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.434967 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435010 #9099] DEBUG -- : Found block device: loop4
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435024 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435033 #9099] DEBUG -- : Found block device: loop5
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435043 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435051 #9099] DEBUG -- : Found block device: loop6
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435060 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435068 #9099] DEBUG -- : Found block device: loop7
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435078 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435086 #9099] DEBUG -- : Found block device: ram10
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435096 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435142 #9099] DEBUG -- : Found block device: ram11
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435153 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435161 #9099] DEBUG -- : Found block device: ram12
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435171 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435180 #9099] DEBUG -- : Found block device: ram13
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435190 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435198 #9099] DEBUG -- : Found block device: ram14
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435210 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435219 #9099] DEBUG -- : Found block device: ram15
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435267 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.435298 #9099] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.500775 #9099] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct  6 15:35:24 node-2 nailgun-agent: D, [2016-10-06T15:35:24.500823 #9099] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct  6 15:35:24 node-2 puppet-user[12966]: (Scope(Class[main])) MODULAR: sync_time
Oct  6 15:35:24 node-2 puppet-user[12966]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct  6 15:35:25 node-2 ntpdate[13566]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Oct  6 15:35:31 node-2 ntpdate[13566]: adjust time server 10.20.0.2 offset 0.000370 sec
Oct  6 15:35:31 node-2 puppet-user[12966]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  6 15:35:31 node-2 puppet-user[12966]: Finished catalog run in 6.16 seconds
Oct  6 15:35:36 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545608 #9099] DEBUG -- : Trying to find block devices
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545688 #9099] DEBUG -- : Found block device: sda
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545737 #9099] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545757 #9099] DEBUG -- : Block device seems to be physical data storage: sda
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545781 #9099] DEBUG -- : Found block device: dm-0
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545794 #9099] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545806 #9099] DEBUG -- : Found block device: dm-1
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545817 #9099] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545827 #9099] DEBUG -- : Found block device: dm-2
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545838 #9099] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545868 #9099] DEBUG -- : Found block device: dm-3
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545879 #9099] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545888 #9099] DEBUG -- : Found block device: dm-4
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545910 #9099] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545919 #9099] DEBUG -- : Found block device: dm-5
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545929 #9099] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545939 #9099] DEBUG -- : Found block device: ram0
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545948 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545956 #9099] DEBUG -- : Found block device: ram1
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545966 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.545995 #9099] DEBUG -- : Found block device: ram2
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546005 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546014 #9099] DEBUG -- : Found block device: ram3
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546023 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546031 #9099] DEBUG -- : Found block device: ram4
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546041 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546049 #9099] DEBUG -- : Found block device: ram5
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546058 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546067 #9099] DEBUG -- : Found block device: ram6
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546077 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546110 #9099] DEBUG -- : Found block device: ram7
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546120 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546128 #9099] DEBUG -- : Found block device: ram8
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546138 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546147 #9099] DEBUG -- : Found block device: ram9
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546156 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546164 #9099] DEBUG -- : Found block device: loop0
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546175 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546185 #9099] DEBUG -- : Found block device: loop1
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546195 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546204 #9099] DEBUG -- : Found block device: loop2
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546242 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546251 #9099] DEBUG -- : Found block device: loop3
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546261 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546269 #9099] DEBUG -- : Found block device: loop4
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546279 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546287 #9099] DEBUG -- : Found block device: loop5
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546297 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546305 #9099] DEBUG -- : Found block device: loop6
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546315 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546324 #9099] DEBUG -- : Found block device: loop7
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546362 #9099] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546371 #9099] DEBUG -- : Found block device: ram10
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546381 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546390 #9099] DEBUG -- : Found block device: ram11
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546399 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546407 #9099] DEBUG -- : Found block device: ram12
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546417 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546425 #9099] DEBUG -- : Found block device: ram13
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546435 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546443 #9099] DEBUG -- : Found block device: ram14
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546452 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546488 #9099] DEBUG -- : Found block device: ram15
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546498 #9099] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.546527 #9099] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct  6 15:35:36 node-2 nailgun-agent: D, [2016-10-06T15:35:36.699873 #9099] DEBUG -- : Response: status: 200 body: {"id": 2}
Oct  6 15:35:36 node-2 nailgun-agent: I, [2016-10-06T15:35:36.700183 #9099]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct  6 15:35:37 node-2 puppet-user[13773]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  6 15:35:37 node-2 puppet-user[13773]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Oct  6 15:35:37 node-2 puppet-user[13773]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  6 15:35:37 node-2 puppet-user[13773]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Oct  6 15:35:37 node-2 puppet-user[13773]: Finished catalog run in 0.08 seconds
Oct  6 15:35:39 node-2 puppet-user[14350]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  6 15:35:39 node-2 puppet-user[14350]: Compiled catalog for node-2.domain.tld in environment production in 0.47 seconds
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Oct  6 15:35:39 node-2 puppet-user[14350]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct  6 15:35:40 node-2 puppet-user[14350]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  6 15:35:40 node-2 puppet-user[14350]: Finished catalog run in 0.92 seconds
Oct  6 15:35:42 node-2 puppet-user[14869]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  6 15:35:42 node-2 puppet-user[14869]: Compiled catalog for node-2.domain.tld in environment production in 0.11 seconds
Oct  6 15:35:45 node-2 puppet-user[14869]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  6 15:36:01 node-2 CRON[16492]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct  6 15:36:11 node-2 puppet-user[14869]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  6 15:36:11 node-2 puppet-user[14869]: Finished catalog run in 28.97 seconds
Oct  6 15:36:13 node-2 puppet-user[17274]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  6 15:36:13 node-2 puppet-user[17274]: Compiled catalog for node-2.domain.tld in environment production in 0.60 seconds
Oct  6 15:36:13 node-2 puppet-user[17274]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  6 15:36:13 node-2 puppet-user[17274]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  6 15:36:13 node-2 puppet-user[17274]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  6 15:36:13 node-2 puppet-user[17274]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  6 15:36:13 node-2 puppet-user[17274]: Finished catalog run in 0.09 seconds
Oct  6 15:36:15 node-2 puppet-user[17741]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  6 15:36:16 node-2 puppet-user[17741]: Compiled catalog for node-2.domain.tld in environment production in 0.92 seconds
Oct  6 15:36:17 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  6 15:36:17 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  6 15:36:17 node-2 crontab[18186]: (root) LIST (root)
Oct  6 15:36:17 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  6 15:36:17 node-2 crontab[18187]: (root) REPLACE (root)
Oct  6 15:36:18 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  6 15:36:19 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Oct  6 15:36:20 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  6 15:36:20 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Oct  6 15:36:20 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Oct  6 15:36:20 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  6 15:36:20 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  6 15:36:20 node-2 puppet-user[17741]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct  6 15:36:20 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  6 15:36:20 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  6 15:36:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:22 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:36 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:36 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:36 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:36 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:36 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:36:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:37:33 node-2 ntpdate[28692]: no servers can be used, exiting
<27>Oct  6 15:37:33 node-2 ntpdate[28878]: no servers can be used, exiting
<27>Oct  6 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:38:21 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:26 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  6 15:39:26 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  6 15:39:32 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  6 15:39:32 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  6 15:39:37 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  6 15:39:43 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  6 15:39:43 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  6 15:39:50 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:50 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:50 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:50 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:50 node-2 multipathd: uevent trigger error
<27>Oct  6 15:39:50 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:02 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:02 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:02 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:02 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:02 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:02 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:08 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:08 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:10 node-2 haproxy[17083]: 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>Oct  6 15:40:11 node-2 haproxy[17092]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:11 node-2 haproxy[17092]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:11 node-2 haproxy[17092]: proxy mysqld has no server available!
<27>Oct  6 15:40:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:16 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:16 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:16 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:16 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:17 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:19 node-2 haproxy[19450]: 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>Oct  6 15:40:19 node-2 haproxy[19450]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:20 node-2 haproxy[19454]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:20 node-2 haproxy[19454]: proxy mysqld has no server available!
<129>Oct  6 15:40:20 node-2 haproxy[19454]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:20 node-2 haproxy[19454]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:20 node-2 haproxy[19454]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:20 node-2 haproxy[19454]: proxy object-storage has no server available!
<27>Oct  6 15:40:22 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:22 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:22 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:22 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:22 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:22 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:24 node-2 haproxy[20677]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:24 node-2 haproxy[20677]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:25 node-2 haproxy[20688]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:25 node-2 haproxy[20688]: proxy neutron has no server available!
<129>Oct  6 15:40:25 node-2 haproxy[20688]: 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>Oct  6 15:40:25 node-2 haproxy[20688]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:25 node-2 haproxy[20688]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:25 node-2 haproxy[20688]: proxy mysqld has no server available!
<129>Oct  6 15:40:25 node-2 haproxy[20688]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:25 node-2 haproxy[20688]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:26 node-2 haproxy[20688]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:26 node-2 haproxy[20688]: proxy object-storage has no server available!
<27>Oct  6 15:40:27 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:27 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:27 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:27 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:27 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:27 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:27 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:29 node-2 haproxy[22090]: 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>Oct  6 15:40:30 node-2 haproxy[22094]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:30 node-2 haproxy[22094]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:30 node-2 haproxy[22094]: proxy keystone-1 has no server available!
<129>Oct  6 15:40:30 node-2 haproxy[22094]: 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>Oct  6 15:40:30 node-2 haproxy[22094]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:30 node-2 haproxy[22094]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:30 node-2 haproxy[22094]: proxy keystone-2 has no server available!
<129>Oct  6 15:40:30 node-2 haproxy[22094]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:30 node-2 haproxy[22094]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:30 node-2 haproxy[22094]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:30 node-2 haproxy[22094]: proxy neutron has no server available!
<129>Oct  6 15:40:31 node-2 haproxy[22094]: 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>Oct  6 15:40:31 node-2 haproxy[22094]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:31 node-2 haproxy[22094]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:31 node-2 haproxy[22094]: proxy mysqld has no server available!
<129>Oct  6 15:40:31 node-2 haproxy[22094]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:31 node-2 haproxy[22094]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:31 node-2 haproxy[22094]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:31 node-2 haproxy[22094]: proxy object-storage has no server available!
<27>Oct  6 15:40:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:33 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:35 node-2 haproxy[23322]: 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>Oct  6 15:40:35 node-2 haproxy[23322]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:35 node-2 haproxy[23322]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:35 node-2 haproxy[23322]: proxy keystone-1 has no server available!
<129>Oct  6 15:40:35 node-2 haproxy[23322]: 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>Oct  6 15:40:35 node-2 haproxy[23322]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:35 node-2 haproxy[23322]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:35 node-2 haproxy[23322]: proxy keystone-2 has no server available!
<129>Oct  6 15:40:35 node-2 haproxy[23322]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:35 node-2 haproxy[23322]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:36 node-2 haproxy[23326]: proxy neutron has no server available!
<129>Oct  6 15:40:36 node-2 haproxy[23326]: 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>Oct  6 15:40:36 node-2 haproxy[23326]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:36 node-2 haproxy[23326]: proxy mysqld has no server available!
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:36 node-2 haproxy[23326]: proxy object-storage has no server available!
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:36 node-2 haproxy[23326]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:36 node-2 haproxy[23326]: proxy aodh has no server available!
<27>Oct  6 15:40:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:38 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:40 node-2 haproxy[24524]: 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>Oct  6 15:40:40 node-2 haproxy[24524]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:40 node-2 haproxy[24524]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:40 node-2 haproxy[24524]: proxy keystone-1 has no server available!
<129>Oct  6 15:40:40 node-2 haproxy[24524]: 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>Oct  6 15:40:40 node-2 haproxy[24524]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:40 node-2 haproxy[24524]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:40 node-2 haproxy[24524]: proxy keystone-2 has no server available!
<129>Oct  6 15:40:40 node-2 haproxy[24524]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:40 node-2 haproxy[24524]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:41 node-2 haproxy[24528]: proxy neutron has no server available!
<129>Oct  6 15:40:41 node-2 haproxy[24528]: 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>Oct  6 15:40:41 node-2 haproxy[24528]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:41 node-2 haproxy[24528]: proxy mysqld has no server available!
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:41 node-2 haproxy[24528]: proxy object-storage has no server available!
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:41 node-2 haproxy[24528]: proxy aodh has no server available!
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:41 node-2 haproxy[24528]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:42 node-2 haproxy[24528]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:42 node-2 haproxy[24528]: proxy ceilometer has no server available!
<27>Oct  6 15:40:43 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:43 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:43 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:43 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:43 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:43 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:45 node-2 haproxy[25938]: 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>Oct  6 15:40:45 node-2 haproxy[25938]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:45 node-2 haproxy[25938]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:45 node-2 haproxy[25938]: proxy keystone-1 has no server available!
<129>Oct  6 15:40:45 node-2 haproxy[25938]: 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>Oct  6 15:40:45 node-2 haproxy[25938]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:46 node-2 haproxy[25942]: proxy keystone-2 has no server available!
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:46 node-2 haproxy[25942]: proxy neutron has no server available!
<129>Oct  6 15:40:46 node-2 haproxy[25942]: 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>Oct  6 15:40:46 node-2 haproxy[25942]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:46 node-2 haproxy[25942]: proxy mysqld has no server available!
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:46 node-2 haproxy[25942]: proxy object-storage has no server available!
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:46 node-2 haproxy[25942]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:47 node-2 haproxy[25942]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:47 node-2 haproxy[25942]: proxy aodh has no server available!
<129>Oct  6 15:40:47 node-2 haproxy[25942]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:47 node-2 haproxy[25942]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:47 node-2 haproxy[25942]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:47 node-2 haproxy[25942]: proxy ceilometer has no server available!
<27>Oct  6 15:40:48 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:48 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:48 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:48 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:48 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:50 node-2 haproxy[27187]: 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>Oct  6 15:40:50 node-2 haproxy[27187]: 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>Oct  6 15:40:51 node-2 haproxy[27191]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:51 node-2 haproxy[27191]: proxy keystone-1 has no server available!
<129>Oct  6 15:40:51 node-2 haproxy[27191]: 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>Oct  6 15:40:51 node-2 haproxy[27191]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:51 node-2 haproxy[27191]: proxy keystone-2 has no server available!
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:51 node-2 haproxy[27191]: proxy neutron has no server available!
<129>Oct  6 15:40:51 node-2 haproxy[27191]: 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>Oct  6 15:40:51 node-2 haproxy[27191]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:51 node-2 haproxy[27191]: proxy mysqld has no server available!
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:51 node-2 haproxy[27191]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:52 node-2 haproxy[27191]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:52 node-2 haproxy[27191]: proxy object-storage has no server available!
<129>Oct  6 15:40:52 node-2 haproxy[27191]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:52 node-2 haproxy[27191]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:52 node-2 haproxy[27191]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:52 node-2 haproxy[27191]: proxy aodh has no server available!
<129>Oct  6 15:40:52 node-2 haproxy[27191]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:52 node-2 haproxy[27191]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:52 node-2 haproxy[27191]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:52 node-2 haproxy[27191]: proxy ceilometer has no server available!
<27>Oct  6 15:40:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:40:55 node-2 multipathd: uevent trigger error
<129>Oct  6 15:40:57 node-2 haproxy[28482]: 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>Oct  6 15:40:57 node-2 haproxy[28482]: 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>Oct  6 15:40:58 node-2 haproxy[28486]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:58 node-2 haproxy[28486]: proxy keystone-1 has no server available!
<129>Oct  6 15:40:58 node-2 haproxy[28486]: 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>Oct  6 15:40:58 node-2 haproxy[28486]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:58 node-2 haproxy[28486]: proxy keystone-2 has no server available!
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:58 node-2 haproxy[28486]: proxy glance-api has no server available!
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:58 node-2 haproxy[28486]: proxy glance-glare has no server available!
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:58 node-2 haproxy[28486]: proxy neutron has no server available!
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:58 node-2 haproxy[28486]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:58 node-2 haproxy[28486]: proxy glance-registry has no server available!
<129>Oct  6 15:40:59 node-2 haproxy[28486]: 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>Oct  6 15:40:59 node-2 haproxy[28486]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:59 node-2 haproxy[28486]: proxy mysqld has no server available!
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:59 node-2 haproxy[28486]: proxy object-storage has no server available!
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:59 node-2 haproxy[28486]: proxy aodh has no server available!
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:40:59 node-2 haproxy[28486]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:40:59 node-2 haproxy[28486]: proxy ceilometer has no server available!
<27>Oct  6 15:41:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:00 node-2 multipathd: uevent trigger error
<129>Oct  6 15:41:03 node-2 haproxy[29781]: 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>Oct  6 15:41:03 node-2 haproxy[29781]: 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>Oct  6 15:41:03 node-2 haproxy[29781]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:03 node-2 haproxy[29781]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:03 node-2 haproxy[29781]: proxy keystone-1 has no server available!
<129>Oct  6 15:41:03 node-2 haproxy[29781]: 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>Oct  6 15:41:03 node-2 haproxy[29781]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:03 node-2 haproxy[29781]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:03 node-2 haproxy[29781]: proxy keystone-2 has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:04 node-2 haproxy[29785]: proxy nova-api has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:04 node-2 haproxy[29785]: proxy nova-metadata-api has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:04 node-2 haproxy[29785]: proxy glance-api has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:04 node-2 haproxy[29785]: proxy glance-glare has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:04 node-2 haproxy[29785]: proxy neutron has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:04 node-2 haproxy[29785]: proxy glance-registry has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: 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>Oct  6 15:41:04 node-2 haproxy[29785]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:04 node-2 haproxy[29785]: proxy mysqld has no server available!
<129>Oct  6 15:41:04 node-2 haproxy[29785]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:05 node-2 haproxy[29785]: proxy object-storage has no server available!
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:05 node-2 haproxy[29785]: proxy aodh has no server available!
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:05 node-2 haproxy[29785]: proxy ceilometer has no server available!
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:05 node-2 haproxy[29785]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:05 node-2 haproxy[29785]: proxy nova-novncproxy has no server available!
<27>Oct  6 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:06 node-2 multipathd: uevent trigger error
<129>Oct  6 15:41:08 node-2 haproxy[30998]: 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>Oct  6 15:41:08 node-2 haproxy[30998]: 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>Oct  6 15:41:08 node-2 haproxy[30998]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:08 node-2 haproxy[30998]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:08 node-2 haproxy[30998]: proxy keystone-1 has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: 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>Oct  6 15:41:09 node-2 haproxy[31002]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:09 node-2 haproxy[31002]: proxy keystone-2 has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:09 node-2 haproxy[31002]: proxy nova-api has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:09 node-2 haproxy[31002]: proxy nova-metadata-api has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: 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>Oct  6 15:41:09 node-2 haproxy[31002]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:09 node-2 haproxy[31002]: proxy cinder-api has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:09 node-2 haproxy[31002]: proxy glance-api has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:09 node-2 haproxy[31002]: proxy glance-glare has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:09 node-2 haproxy[31002]: proxy neutron has no server available!
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:09 node-2 haproxy[31002]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:10 node-2 haproxy[31002]: proxy glance-registry has no server available!
<129>Oct  6 15:41:10 node-2 haproxy[31002]: 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>Oct  6 15:41:10 node-2 haproxy[31002]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:10 node-2 haproxy[31002]: proxy mysqld has no server available!
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:10 node-2 haproxy[31002]: proxy object-storage has no server available!
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:10 node-2 haproxy[31002]: proxy aodh has no server available!
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:10 node-2 haproxy[31002]: proxy ceilometer has no server available!
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:10 node-2 haproxy[31002]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:10 node-2 haproxy[31002]: proxy nova-novncproxy has no server available!
<27>Oct  6 15:41:11 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:11 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:11 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:11 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:11 node-2 multipathd: uevent trigger error
<129>Oct  6 15:41:14 node-2 haproxy[32273]: 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>Oct  6 15:41:14 node-2 haproxy[32273]: 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>Oct  6 15:41:14 node-2 haproxy[32273]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:14 node-2 haproxy[32273]: proxy keystone-1 has no server available!
<129>Oct  6 15:41:14 node-2 haproxy[32273]: 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>Oct  6 15:41:14 node-2 haproxy[32273]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:14 node-2 haproxy[32273]: proxy keystone-2 has no server available!
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:14 node-2 haproxy[32273]: proxy nova-api has no server available!
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:14 node-2 haproxy[32273]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:14 node-2 haproxy[32273]: proxy nova-metadata-api has no server available!
<129>Oct  6 15:41:14 node-2 haproxy[32273]: 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>Oct  6 15:41:14 node-2 haproxy[32273]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy cinder-api has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy glance-api has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy glance-glare has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy neutron has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy glance-registry has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: 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>Oct  6 15:41:15 node-2 haproxy[32277]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy mysqld has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy object-storage has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy aodh has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy ceilometer has no server available!
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:15 node-2 haproxy[32277]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:15 node-2 haproxy[32277]: proxy heat-api has no server available!
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:16 node-2 haproxy[32277]: proxy heat-api-cfn has no server available!
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:16 node-2 haproxy[32277]: proxy heat-api-cloudwatch has no server available!
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  6 15:41:16 node-2 haproxy[32277]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  6 15:41:16 node-2 haproxy[32277]: proxy nova-novncproxy has no server available!
<27>Oct  6 15:41:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:20 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:20 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:20 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:20 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:20 node-2 multipathd: uevent trigger error
<27>Oct  6 15:41:28 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  6 15:41:51 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Oct  6 15:41:53 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  6 15:42:25 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  6 15:42:33 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  6 15:42:49 node-2 multipathd: uevent trigger error
<27>Oct  6 15:42:49 node-2 multipathd: uevent trigger error
<27>Oct  6 15:42:49 node-2 multipathd: uevent trigger error
<27>Oct  6 15:42:49 node-2 multipathd: uevent trigger error
<27>Oct  6 15:42:49 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:07 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:07 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:07 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:07 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:07 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:13 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:17 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:27 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  6 15:45:31 node-2 apache2_error [Thu Oct 06 15:45:28.491678 2016] [mpm_event:notice] [pid 10253:tid 139622306355072] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  6 15:45:31 node-2 apache2_error [Thu Oct 06 15:45:28.491762 2016] [core:notice] [pid 10253:tid 139622306355072] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  6 15:45:31 node-2 apache2_error [Thu Oct 06 15:45:30.242827 2016] [mpm_event:notice] [pid 10253:tid 139622306355072] AH00491: caught SIGTERM, shutting down
<27>Oct  6 15:45:35 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:35 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:35 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:35 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:35 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:38 node-2 multipathd: uevent trigger error
<27>Oct  6 15:45:38 node-2 multipathd: uevent trigger error
<43>Oct  6 15:45:41 node-2 apache2_error [Thu Oct 06 15:45:31.318495 2016] [mpm_worker:notice] [pid 10570:tid 140080077694848] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  6 15:45:41 node-2 apache2_error [Thu Oct 06 15:45:31.318551 2016] [core:notice] [pid 10570:tid 140080077694848] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  6 15:46:41 node-2 apache2_error [Thu Oct 06 15:46:40.719726 2016] [mpm_worker:notice] [pid 10570:tid 140080077694848] AH00295: caught SIGTERM, shutting down
<43>Oct  6 15:46:51 node-2 apache2_error [Thu Oct 06 15:46:41.469672 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  6 15:46:51 node-2 apache2_error [Thu Oct 06 15:46:41.469717 2016] [core:notice] [pid 22118:tid 140429998036864] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  6 15:47:31 node-2 apache2_error [Thu Oct 06 15:47:25.315020 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  6 15:47:31 node-2 apache2_error [Thu Oct 06 15:47:25.511534 2016] [mpm_worker:warn] [pid 22118:tid 140429998036864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  6 15:47:31 node-2 apache2_error [Thu Oct 06 15:47:25.516897 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  6 15:47:31 node-2 apache2_error [Thu Oct 06 15:47:25.516924 2016] [core:notice] [pid 22118:tid 140429998036864] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  6 15:48:10 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:10 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:10 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:10 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:10 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:15 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:28 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  6 15:48:30 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:30 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:30 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:30 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:30 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:48:55 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:00 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:49:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:50:06 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:51:41 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  6 15:52:12 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:12 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:12 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:12 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:12 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:18 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:45 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:45 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:45 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:45 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:45 node-2 multipathd: uevent trigger error
<27>Oct  6 15:52:45 node-2 multipathd: uevent trigger error
<27>Oct  6 15:54:43 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  6 15:55:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:05 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:23 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:28 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:33 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:58 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:58 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:58 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:58 node-2 multipathd: uevent trigger error
<27>Oct  6 15:55:59 node-2 multipathd: uevent trigger error
<27>Oct  6 15:56:41 node-2 multipathd: uevent trigger error
<27>Oct  6 15:56:41 node-2 multipathd: uevent trigger error
<27>Oct  6 15:56:41 node-2 multipathd: uevent trigger error
<27>Oct  6 15:56:41 node-2 multipathd: uevent trigger error
<27>Oct  6 15:56:41 node-2 multipathd: uevent trigger error
<27>Oct  6 15:56:41 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:24 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:24 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:24 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:24 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:24 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:24 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:40 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:40 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:40 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:40 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:40 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:40 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:44 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  6 15:57:56 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:56 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:56 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:56 node-2 multipathd: uevent trigger error
<27>Oct  6 15:57:56 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:28 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:28 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:28 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:38 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:38 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:38 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:38 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:38 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:38 node-2 multipathd: uevent trigger error
<27>Oct  6 16:00:39 node-2 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct  6 16:00:46 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  6 16:01:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:01:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:01:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:01:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:01:54 node-2 multipathd: uevent trigger error
<27>Oct  6 16:01:54 node-2 multipathd: uevent trigger error
<27>Oct  6 16:01:54 node-2 multipathd: uevent trigger error
<27>Oct  6 16:01:54 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:30 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:30 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:30 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:30 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:30 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:30 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:34 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:34 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:34 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:34 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:34 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:51 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:51 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:51 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:51 node-2 multipathd: uevent trigger error
<27>Oct  6 16:02:51 node-2 multipathd: uevent trigger error
<27>Oct  6 16:03:19 node-2 multipathd: uevent trigger error
<27>Oct  6 16:03:19 node-2 multipathd: uevent trigger error
<27>Oct  6 16:03:19 node-2 multipathd: uevent trigger error
<27>Oct  6 16:03:19 node-2 multipathd: uevent trigger error
<27>Oct  6 16:03:19 node-2 multipathd: uevent trigger error
<27>Oct  6 16:03:19 node-2 multipathd: uevent trigger error
<27>Oct  6 16:03:47 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  6 16:04:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:36 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:36 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:36 node-2 multipathd: uevent trigger error
<27>Oct  6 16:04:36 node-2 multipathd: uevent trigger error
<11>Oct  6 16:04:49 node-2 liberasurecode[68534]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:49 node-2 liberasurecode[68534]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:49 node-2 liberasurecode[68534]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:49 node-2 liberasurecode[68534]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:49 node-2 liberasurecode[68558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:49 node-2 liberasurecode[68558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:49 node-2 liberasurecode[68558]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:49 node-2 liberasurecode[68558]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:51 node-2 liberasurecode[69578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:51 node-2 liberasurecode[69578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:51 node-2 liberasurecode[69578]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:51 node-2 liberasurecode[69578]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[70997]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[70997]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[70997]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[70997]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71038]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71038]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71038]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71038]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71082]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:55 node-2 liberasurecode[71082]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71139]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71139]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71139]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71139]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71153]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71153]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71153]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71153]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71170]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71170]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71170]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71170]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71182]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71182]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71182]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:04:56 node-2 liberasurecode[71182]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:01 node-2 liberasurecode[71489]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:01 node-2 liberasurecode[71489]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:01 node-2 liberasurecode[71489]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:01 node-2 liberasurecode[71489]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:13 node-2 liberasurecode[72113]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:13 node-2 liberasurecode[72113]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:13 node-2 liberasurecode[72113]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:05:13 node-2 liberasurecode[72113]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  6 16:05:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:05:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:05:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:05:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:05:20 node-2 multipathd: uevent trigger error
<27>Oct  6 16:05:20 node-2 multipathd: uevent trigger error
<43>Oct  6 16:06:12 node-2 apache2_error [Thu Oct 06 16:06:07.262791 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  6 16:06:12 node-2 apache2_error [Thu Oct 06 16:06:07.645338 2016] [mpm_worker:warn] [pid 22118:tid 140429998036864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  6 16:06:12 node-2 apache2_error [Thu Oct 06 16:06:07.648365 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  6 16:06:12 node-2 apache2_error [Thu Oct 06 16:06:07.648383 2016] [core:notice] [pid 22118:tid 140429998036864] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  6 16:06:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:48 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:49 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  6 16:06:52 node-2 apache2_error [Thu Oct 06 16:06:44.313486 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  6 16:06:52 node-2 apache2_error [Thu Oct 06 16:06:44.698916 2016] [mpm_worker:warn] [pid 22118:tid 140429998036864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  6 16:06:52 node-2 apache2_error [Thu Oct 06 16:06:44.708222 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  6 16:06:52 node-2 apache2_error [Thu Oct 06 16:06:44.708251 2016] [core:notice] [pid 22118:tid 140429998036864] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  6 16:06:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:06:55 node-2 multipathd: uevent trigger error
<43>Oct  6 16:07:32 node-2 apache2_error [Thu Oct 06 16:07:29.995083 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  6 16:07:32 node-2 apache2_error [Thu Oct 06 16:07:30.381679 2016] [mpm_worker:warn] [pid 22118:tid 140429998036864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  6 16:07:32 node-2 apache2_error [Thu Oct 06 16:07:30.390130 2016] [mpm_worker:notice] [pid 22118:tid 140429998036864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  6 16:07:32 node-2 apache2_error [Thu Oct 06 16:07:30.390155 2016] [core:notice] [pid 22118:tid 140429998036864] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  6 16:07:33 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:33 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:33 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:33 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:34 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:40 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:40 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:40 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:40 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:40 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:40 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:45 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:07:55 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:12 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:12 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:12 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:12 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:12 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:32 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:38 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  6 16:08:47 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:47 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:47 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:47 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:47 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:47 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:52 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:52 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:52 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:52 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:52 node-2 multipathd: uevent trigger error
<27>Oct  6 16:08:52 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:06 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:06 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:06 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:06 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:06 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:18 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:18 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:18 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:18 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:18 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:18 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:22 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  6 16:09:23 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:23 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:23 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:23 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:23 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:23 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:23 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:50 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:50 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:50 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:50 node-2 multipathd: uevent trigger error
<27>Oct  6 16:09:50 node-2 multipathd: uevent trigger error
<11>Oct  6 16:10:01 node-2 liberasurecode[131777]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:10:01 node-2 liberasurecode[131777]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:10:01 node-2 liberasurecode[131777]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  6 16:10:01 node-2 liberasurecode[131777]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  6 16:10:03 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:03 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:03 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:03 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:03 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:10 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:10 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:10 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:10 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:10 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:15 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:56 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:56 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:56 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:56 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:56 node-2 multipathd: uevent trigger error
<27>Oct  6 16:10:56 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:01 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:05 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:05 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:05 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:05 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:05 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:05 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:09 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:09 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:09 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:09 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:09 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:09 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:17 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:17 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:17 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:17 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:17 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:17 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:21 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:21 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:21 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:22 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:22 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:26 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:31 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:31 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:31 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:31 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:31 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:31 node-2 multipathd: uevent trigger error
<27>Oct  6 16:11:39 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:11:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:53 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:11:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:11:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:05 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:12:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:18 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:12:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:30 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:12:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:42 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:12:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:54 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:12:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:12:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:06 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:13:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:18 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:13:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:30 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct  6 16:13:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
<27>Oct  6 16:13:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-04bc8674-bc" in table Interface
