Oct 31 18:30:40 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] start
Oct 31 18:30:40 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 31 18:30:40 node-2 rsyslogd: rsyslogd's groupid changed to 104
Oct 31 18:30:40 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct 31 18:30:40 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 31 18:30:40 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 31 18:30:40 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 31 18:30:40 node-2 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Oct 31 18:30:40 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=5fa71a40-7532-4fc2-8e54-19d35da77e21 nomdmonddf nomdmonisw
Oct 31 18:30:40 node-2 kernel: [    0.000000] KERNEL supported cpus:
Oct 31 18:30:40 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct 31 18:30:40 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct 31 18:30:40 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct 31 18:30:40 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 31 18:30:40 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 31 18:30:40 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 31 18:30:40 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 31 18:30:40 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 31 18:30:40 node-2 kernel: [    0.000000] No AGP bridge found
Oct 31 18:30:40 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 31 18:30:40 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct 31 18:30:40 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 31 18:30:40 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct 31 18:30:40 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 31 18:30:40 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 31 18:30:40 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 31 18:30:40 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 31 18:30:40 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 31 18:30:40 node-2 kernel: [    0.000000]   2 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000]   3 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000]   4 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000]   5 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000]   6 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000]   7 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000]   8 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000]   9 disabled
Oct 31 18:30:40 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 31 18:30:40 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 31 18:30:40 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 31 18:30:40 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 31 18:30:40 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 31 18:30:40 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 31 18:30:40 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 31 18:30:40 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 31 18:30:40 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 31 18:30:40 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 31 18:30:40 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 31 18:30:40 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35828000-0x36c0bfff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 31 18:30:40 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 31 18:30:40 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 31 18:30:40 node-2 kernel: [    0.000000] Zone ranges:
Oct 31 18:30:40 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] Movable zone start for each node
Oct 31 18:30:40 node-2 kernel: [    0.000000] Early memory node ranges
Oct 31 18:30:40 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct 31 18:30:40 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 31 18:30:40 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 31 18:30:40 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 31 18:30:40 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct 31 18:30:40 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct 31 18:30:40 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 31 18:30:40 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 31 18:30:40 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 31 18:30:40 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 31 18:30:40 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 31 18:30:40 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 31 18:30:40 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 31 18:30:40 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 31 18:30:40 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 31 18:30:40 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 31 18:30:40 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 31 18:30:40 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 31 18:30:40 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 31 18:30:40 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 31 18:30:40 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 31 18:30:40 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 31 18:30:40 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 31 18:30:40 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 31 18:30:40 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct 31 18:30:40 node-2 kernel: [    0.000000] Policy zone: Normal
Oct 31 18:30:40 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=5fa71a40-7532-4fc2-8e54-19d35da77e21 nomdmonddf nomdmonisw
Oct 31 18:30:40 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 31 18:30:40 node-2 kernel: [    0.000000] Checking aperture...
Oct 31 18:30:40 node-2 kernel: [    0.000000] No AGP bridge found
Oct 31 18:30:40 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 31 18:30:40 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 31 18:30:40 node-2 kernel: [    0.000000] Memory: 32653468K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627168K reserved)
Oct 31 18:30:40 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 31 18:30:40 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 31 18:30:40 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 31 18:30:40 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 31 18:30:40 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 31 18:30:40 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 31 18:30:40 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 31 18:30:40 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 31 18:30:40 node-2 kernel: [    0.000000] console [tty0] enabled
Oct 31 18:30:40 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 31 18:30:40 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 31 18:30:40 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 31 18:30:40 node-2 kernel: [    0.000000] hpet clockevent registered
Oct 31 18:30:40 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 31 18:30:40 node-2 kernel: [    0.004000] tsc: Detected 3492.241 MHz processor
Oct 31 18:30:40 node-2 kernel: [    0.000014] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.48 BogoMIPS (lpj=13968964)
Oct 31 18:30:40 node-2 kernel: [    0.000017] pid_max: default: 32768 minimum: 301
Oct 31 18:30:40 node-2 kernel: [    0.000053] Security Framework initialized
Oct 31 18:30:40 node-2 kernel: [    0.000071] AppArmor: AppArmor initialized
Oct 31 18:30:40 node-2 kernel: [    0.000072] Yama: becoming mindful.
Oct 31 18:30:40 node-2 kernel: [    0.001470] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.006328] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.008257] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.008284] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.008575] Initializing cgroup subsys memory
Oct 31 18:30:40 node-2 kernel: [    0.008583] Initializing cgroup subsys devices
Oct 31 18:30:40 node-2 kernel: [    0.008585] Initializing cgroup subsys freezer
Oct 31 18:30:40 node-2 kernel: [    0.008586] Initializing cgroup subsys blkio
Oct 31 18:30:40 node-2 kernel: [    0.008588] Initializing cgroup subsys perf_event
Oct 31 18:30:40 node-2 kernel: [    0.008590] Initializing cgroup subsys hugetlb
Oct 31 18:30:40 node-2 kernel: [    0.008609] CPU: Physical Processor ID: 0
Oct 31 18:30:40 node-2 kernel: [    0.008611] CPU: Processor Core ID: 0
Oct 31 18:30:40 node-2 kernel: [    0.008614] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 31 18:30:40 node-2 kernel: [    0.008614] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 31 18:30:40 node-2 kernel: [    0.009308] mce: CPU supports 22 MCE banks
Oct 31 18:30:40 node-2 kernel: [    0.009336] CPU0: Thermal monitoring enabled (TM1)
Oct 31 18:30:40 node-2 kernel: [    0.009356] process: using mwait in idle threads
Oct 31 18:30:40 node-2 kernel: [    0.009359] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 31 18:30:40 node-2 kernel: [    0.009359] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 31 18:30:40 node-2 kernel: [    0.009359] tlb_flushall_shift: 6
Oct 31 18:30:40 node-2 kernel: [    0.009447] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 31 18:30:40 node-2 kernel: [    0.010171] ACPI: Core revision 20131115
Oct 31 18:30:40 node-2 kernel: [    0.022969] ACPI: All ACPI Tables successfully acquired
Oct 31 18:30:40 node-2 kernel: [    0.023129] ftrace: allocating 28622 entries in 112 pages
Oct 31 18:30:40 node-2 kernel: [    0.031887] dmar: Host address width 46
Oct 31 18:30:40 node-2 kernel: [    0.031889] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 31 18:30:40 node-2 kernel: [    0.031895] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 31 18:30:40 node-2 kernel: [    0.031897] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 31 18:30:40 node-2 kernel: [    0.031901] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 31 18:30:40 node-2 kernel: [    0.031903] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 31 18:30:40 node-2 kernel: [    0.031904] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 31 18:30:40 node-2 kernel: [    0.031905] dmar: ATSR flags: 0x0
Oct 31 18:30:40 node-2 kernel: [    0.031906] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 31 18:30:40 node-2 kernel: [    0.031908] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 31 18:30:40 node-2 kernel: [    0.032024] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 31 18:30:40 node-2 kernel: [    0.032025] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 31 18:30:40 node-2 kernel: [    0.032026] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 31 18:30:40 node-2 kernel: [    0.032027] HPET id 0 under DRHD base 0xc7ffc000
Oct 31 18:30:40 node-2 kernel: [    0.032028] Your BIOS is broken and requested that x2apic be disabled.
Oct 31 18:30:40 node-2 kernel: [    0.032028] This will slightly decrease performance.
Oct 31 18:30:40 node-2 kernel: [    0.032028] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 31 18:30:40 node-2 kernel: [    0.032459] Enabled IRQ remapping in xapic mode
Oct 31 18:30:40 node-2 kernel: [    0.032460] x2apic not enabled, IRQ remapping is in xapic mode
Oct 31 18:30:40 node-2 kernel: [    0.032464] Switched APIC routing to physical flat.
Oct 31 18:30:40 node-2 kernel: [    0.033039] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 31 18:30:40 node-2 kernel: [    0.072693] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 31 18:30:40 node-2 kernel: [    0.072698] TSC deadline timer enabled
Oct 31 18:30:40 node-2 kernel: [    0.072705] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 31 18:30:40 node-2 kernel: [    0.072712] ... version:                3
Oct 31 18:30:40 node-2 kernel: [    0.072713] ... bit width:              48
Oct 31 18:30:40 node-2 kernel: [    0.072713] ... generic registers:      4
Oct 31 18:30:40 node-2 kernel: [    0.072714] ... value mask:             0000ffffffffffff
Oct 31 18:30:40 node-2 kernel: [    0.072715] ... max period:             0000ffffffffffff
Oct 31 18:30:40 node-2 kernel: [    0.072716] ... fixed-purpose events:   3
Oct 31 18:30:40 node-2 kernel: [    0.072717] ... event mask:             000000070000000f
Oct 31 18:30:40 node-2 kernel: [    0.074147] x86: Booting SMP configuration:
Oct 31 18:30:40 node-2 kernel: [    0.088349] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 31 18:30:40 node-2 kernel: [    0.074149] .... node  #0, CPUs:        #1  #2  #3
Oct 31 18:30:40 node-2 kernel: [    0.116263] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 31 18:30:40 node-2 kernel: [    0.270429] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 31 18:30:40 node-2 kernel: [    0.326054] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 31 18:30:40 node-2 kernel: [    0.382711] x86: Booted up 2 nodes, 16 CPUs
Oct 31 18:30:40 node-2 kernel: [    0.382714] smpboot: Total of 16 processors activated (111763.62 BogoMIPS)
Oct 31 18:30:40 node-2 kernel: [    0.406730] devtmpfs: initialized
Oct 31 18:30:40 node-2 kernel: [    0.409463] EVM: security.selinux
Oct 31 18:30:40 node-2 kernel: [    0.409464] EVM: security.SMACK64
Oct 31 18:30:40 node-2 kernel: [    0.409465] EVM: security.ima
Oct 31 18:30:40 node-2 kernel: [    0.409466] EVM: security.capability
Oct 31 18:30:40 node-2 kernel: [    0.409516] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.410165] pinctrl core: initialized pinctrl subsystem
Oct 31 18:30:40 node-2 kernel: [    0.410224] regulator-dummy: no parameters
Oct 31 18:30:40 node-2 kernel: [    0.410255] RTC time: 18:30:03, date: 10/31/16
Oct 31 18:30:40 node-2 kernel: [    0.410302] NET: Registered protocol family 16
Oct 31 18:30:40 node-2 kernel: [    0.410386] cpuidle: using governor ladder
Oct 31 18:30:40 node-2 kernel: [    0.410388] cpuidle: using governor menu
Oct 31 18:30:40 node-2 kernel: [    0.410421] ACPI: bus type PCI registered
Oct 31 18:30:40 node-2 kernel: [    0.410423] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 31 18:30:40 node-2 kernel: [    0.410465] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 31 18:30:40 node-2 kernel: [    0.410468] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 31 18:30:40 node-2 kernel: [    0.424193] PCI: Using configuration type 1 for base access
Oct 31 18:30:40 node-2 kernel: [    0.425194] bio: create slab <bio-0> at 0
Oct 31 18:30:40 node-2 kernel: [    0.425476] ACPI: Added _OSI(Module Device)
Oct 31 18:30:40 node-2 kernel: [    0.425478] ACPI: Added _OSI(Processor Device)
Oct 31 18:30:40 node-2 kernel: [    0.425479] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 31 18:30:40 node-2 kernel: [    0.425480] ACPI: Added _OSI(Processor Aggregator Device)
Oct 31 18:30:40 node-2 kernel: [    0.438156] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 31 18:30:40 node-2 kernel: [    0.448723] ACPI: Interpreter enabled
Oct 31 18:30:40 node-2 kernel: [    0.448728] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 31 18:30:40 node-2 kernel: [    0.448732] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 31 18:30:40 node-2 kernel: [    0.448734] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 31 18:30:40 node-2 kernel: [    0.448741] ACPI: (supports S0 S4 S5)
Oct 31 18:30:40 node-2 kernel: [    0.448742] ACPI: Using IOAPIC for interrupt routing
Oct 31 18:30:40 node-2 kernel: [    0.448784] HEST: Table parsing has been initialized.
Oct 31 18:30:40 node-2 kernel: [    0.448787] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 31 18:30:40 node-2 kernel: [    0.449359] ACPI: No dock devices found.
Oct 31 18:30:40 node-2 kernel: [    0.461392] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 31 18:30:40 node-2 kernel: [    0.461398] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 31 18:30:40 node-2 kernel: [    0.461401] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 31 18:30:40 node-2 kernel: [    0.461430] PCI host bridge to bus 0000:ff
Oct 31 18:30:40 node-2 kernel: [    0.461432] pci_bus 0000:ff: root bus resource [bus ff]
Oct 31 18:30:40 node-2 kernel: [    0.461440] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461478] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.461508] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461544] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461575] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.461604] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.461634] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461663] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461694] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461722] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461748] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461774] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461802] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461827] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461854] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461880] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461908] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461935] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.461962] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.461989] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462015] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.462041] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462067] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462096] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.462130] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462161] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462191] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462221] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462252] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462282] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462312] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462342] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462373] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462405] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462438] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462471] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462504] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462534] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462561] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462592] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462626] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462664] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462699] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462732] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462763] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462791] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462821] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462851] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462881] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462911] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462946] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.462975] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463004] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463032] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463061] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463091] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463122] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463179] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 31 18:30:40 node-2 kernel: [    0.463182] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 31 18:30:40 node-2 kernel: [    0.463185] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 31 18:30:40 node-2 kernel: [    0.463202] PCI host bridge to bus 0000:7f
Oct 31 18:30:40 node-2 kernel: [    0.463204] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 31 18:30:40 node-2 kernel: [    0.463209] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463236] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.463262] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463293] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463314] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.463338] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.463364] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463389] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463411] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463433] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463455] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463477] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463501] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463523] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463546] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463571] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463593] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463615] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463638] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.463661] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463683] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.463704] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463727] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463752] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 31 18:30:40 node-2 kernel: [    0.463785] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463810] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463836] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463862] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463887] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463914] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463941] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463971] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.463995] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464021] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464047] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464074] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464105] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464130] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464155] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464183] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464207] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464233] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464261] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464287] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464313] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464339] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464364] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464390] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464416] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464442] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464471] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464495] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464517] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 31 18:30:40 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 31 18:30:40 node-2 kernel: [    0.464541] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464566] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464595] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.464620] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.465860] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 31 18:30:40 node-2 kernel: [    0.465864] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 31 18:30:40 node-2 kernel: [    0.466989] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 31 18:30:40 node-2 kernel: [    0.467496] PCI host bridge to bus 0000:00
Oct 31 18:30:40 node-2 kernel: [    0.467499] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 31 18:30:40 node-2 kernel: [    0.467500] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 31 18:30:40 node-2 kernel: [    0.467502] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 31 18:30:40 node-2 kernel: [    0.467503] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 31 18:30:40 node-2 kernel: [    0.467504] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 31 18:30:40 node-2 kernel: [    0.467506] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 31 18:30:40 node-2 kernel: [    0.467507] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 31 18:30:40 node-2 kernel: [    0.467513] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 31 18:30:40 node-2 kernel: [    0.467595] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.467625] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.467667] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 31 18:30:40 node-2 kernel: [    0.467685] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.467715] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.467755] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 31 18:30:40 node-2 kernel: [    0.467773] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.467802] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.467842] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 31 18:30:40 node-2 kernel: [    0.467859] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.467928] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.468008] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.468083] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 31 18:30:40 node-2 kernel: [    0.468088] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 31 18:30:40 node-2 kernel: [    0.468172] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 31 18:30:40 node-2 kernel: [    0.468321] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 31 18:30:40 node-2 kernel: [    0.468338] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 31 18:30:40 node-2 kernel: [    0.468416] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.468469] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 31 18:30:40 node-2 kernel: [    0.468491] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.468546] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.468590] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 31 18:30:40 node-2 kernel: [    0.468616] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.468673] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.468716] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 31 18:30:40 node-2 kernel: [    0.468740] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 31 18:30:40 node-2 kernel: [    0.468757] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 31 18:30:40 node-2 kernel: [    0.468835] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.468885] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 31 18:30:40 node-2 kernel: [    0.468910] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 31 18:30:40 node-2 kernel: [    0.469156] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 31 18:30:40 node-2 kernel: [    0.469162] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 31 18:30:40 node-2 kernel: [    0.469168] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.469174] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.469182] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 31 18:30:40 node-2 kernel: [    0.469212] pci 0000:01:00.0: supports D1 D2
Oct 31 18:30:40 node-2 kernel: [    0.474955] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 31 18:30:40 node-2 kernel: [    0.474961] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 31 18:30:40 node-2 kernel: [    0.474965] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 31 18:30:40 node-2 kernel: [    0.475101] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.475134] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 31 18:30:40 node-2 kernel: [    0.482953] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 31 18:30:40 node-2 kernel: [    0.482956] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.482958] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 31 18:30:40 node-2 kernel: [    0.483012] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.483085] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.483161] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.483207] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 31 18:30:40 node-2 kernel: [    0.483210] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.483212] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 31 18:30:40 node-2 kernel: [    0.483265] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.483404] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.483459] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 31 18:30:40 node-2 kernel: [    0.483461] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.483463] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.483513] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.483636] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.483678] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.483797] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.483835] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.483956] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.483994] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 31 18:30:40 node-2 kernel: [    0.484113] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 31 18:30:40 node-2 kernel: [    0.484156] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 31 18:30:40 node-2 kernel: [    0.484159] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.484161] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.484221] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 31 18:30:40 node-2 kernel: [    0.484284] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.484336] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.484378] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 31 18:30:40 node-2 kernel: [    0.484484] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 31 18:30:40 node-2 kernel: [    0.484592] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 31 18:30:40 node-2 kernel: [    0.484594] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.484596] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.484652] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 31 18:30:40 node-2 kernel: [    0.484706] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.484755] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.484968] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 31 18:30:40 node-2 kernel: [    0.484971] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 31 18:30:40 node-2 kernel: [    0.485036] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 31 18:30:40 node-2 kernel: [    0.485091] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.485140] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.485350] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 31 18:30:40 node-2 kernel: [    0.485354] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 31 18:30:40 node-2 kernel: [    0.485431] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 31 18:30:40 node-2 kernel: [    0.485495] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.485547] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 31 18:30:40 node-2 kernel: [    0.485774] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 31 18:30:40 node-2 kernel: [    0.485778] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 31 18:30:40 node-2 kernel: [    0.485952] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 31 18:30:40 node-2 kernel: [    0.485990] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 31 18:30:40 node-2 kernel: [    0.486071] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 31 18:30:40 node-2 kernel: [    0.486090] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 31 18:30:40 node-2 kernel: [    0.486103] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 31 18:30:40 node-2 kernel: [    0.486116] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 31 18:30:40 node-2 kernel: [    0.486167] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 31 18:30:40 node-2 kernel: [    0.490968] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 31 18:30:40 node-2 kernel: [    0.490977] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 31 18:30:40 node-2 kernel: [    0.491029] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 31 18:30:40 node-2 kernel: [    0.491681] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 31 18:30:40 node-2 kernel: [    0.491684] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 31 18:30:40 node-2 kernel: [    0.491804] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 31 18:30:40 node-2 kernel: [    0.491915] PCI host bridge to bus 0000:80
Oct 31 18:30:40 node-2 kernel: [    0.491917] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 31 18:30:40 node-2 kernel: [    0.491918] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 31 18:30:40 node-2 kernel: [    0.491920] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 31 18:30:40 node-2 kernel: [    0.491928] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.491991] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.492060] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 31 18:30:40 node-2 kernel: [    0.492122] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 31 18:30:40 node-2 kernel: [    0.492128] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 31 18:30:40 node-2 kernel: [    0.492198] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 31 18:30:40 node-2 kernel: [    0.492494] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 31 18:30:40 node-2 kernel: [    0.492526] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 31 18:30:40 node-2 kernel: [    0.492555] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 31 18:30:40 node-2 kernel: [    0.492584] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 31 18:30:40 node-2 kernel: [    0.492614] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 31 18:30:40 node-2 kernel: [    0.492644] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 31 18:30:40 node-2 kernel: [    0.492674] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 31 18:30:40 node-2 kernel: [    0.492703] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 31 18:30:40 node-2 kernel: [    0.492788] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 31 18:30:40 node-2 kernel: [    0.492793] ACPI: \_SB_.UNC1: notify handler is installed
Oct 31 18:30:40 node-2 kernel: [    0.492794] ACPI: \_SB_.UNC0: notify handler is installed
Oct 31 18:30:40 node-2 kernel: [    0.492809] ACPI: \_SB_.PCI0: notify handler is installed
Oct 31 18:30:40 node-2 kernel: [    0.492861] ACPI: \_SB_.PCI1: notify handler is installed
Oct 31 18:30:40 node-2 kernel: [    0.492941] Found 4 acpi root devices
Oct 31 18:30:40 node-2 kernel: [    0.493050] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 31 18:30:40 node-2 kernel: [    0.493052] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 31 18:30:40 node-2 kernel: [    0.493054] vgaarb: loaded
Oct 31 18:30:40 node-2 kernel: [    0.493055] vgaarb: bridge control possible 0000:0c:00.0
Oct 31 18:30:40 node-2 kernel: [    0.493177] SCSI subsystem initialized
Oct 31 18:30:40 node-2 kernel: [    0.493243] libata version 3.00 loaded.
Oct 31 18:30:40 node-2 kernel: [    0.493259] ACPI: bus type USB registered
Oct 31 18:30:40 node-2 kernel: [    0.493269] usbcore: registered new interface driver usbfs
Oct 31 18:30:40 node-2 kernel: [    0.493274] usbcore: registered new interface driver hub
Oct 31 18:30:40 node-2 kernel: [    0.493297] usbcore: registered new device driver usb
Oct 31 18:30:40 node-2 kernel: [    0.493458] PCI: Using ACPI for IRQ routing
Oct 31 18:30:40 node-2 kernel: [    0.497071] PCI: pci_cache_line_size set to 64 bytes
Oct 31 18:30:40 node-2 kernel: [    0.497275] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 31 18:30:40 node-2 kernel: [    0.497276] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct 31 18:30:40 node-2 kernel: [    0.497277] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 31 18:30:40 node-2 kernel: [    0.497342] NetLabel: Initializing
Oct 31 18:30:40 node-2 kernel: [    0.497343] NetLabel:  domain hash size = 128
Oct 31 18:30:40 node-2 kernel: [    0.497344] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 31 18:30:40 node-2 kernel: [    0.497354] NetLabel:  unlabeled traffic allowed by default
Oct 31 18:30:40 node-2 kernel: [    0.497422] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 31 18:30:40 node-2 kernel: [    0.497426] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 31 18:30:40 node-2 kernel: [    0.499483] Switched to clocksource hpet
Oct 31 18:30:40 node-2 kernel: [    0.503471] AppArmor: AppArmor Filesystem Enabled
Oct 31 18:30:40 node-2 kernel: [    0.503490] pnp: PnP ACPI init
Oct 31 18:30:40 node-2 kernel: [    0.503497] ACPI: bus type PNP registered
Oct 31 18:30:40 node-2 kernel: [    0.503604] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503613] pnp 00:01: [dma 4]
Oct 31 18:30:40 node-2 kernel: [    0.503625] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503651] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503671] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503689] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503721] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503774] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503776] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 31 18:30:40 node-2 kernel: [    0.503778] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503780] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503781] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503786] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503789] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 31 18:30:40 node-2 kernel: [    0.503790] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503792] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503793] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503795] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503796] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503798] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 31 18:30:40 node-2 kernel: [    0.503800] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503883] pnp 00:07: [dma 0 disabled]
Oct 31 18:30:40 node-2 kernel: [    0.503911] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 31 18:30:40 node-2 kernel: [    0.503986] pnp 00:08: [dma 0 disabled]
Oct 31 18:30:40 node-2 kernel: [    0.504018] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 31 18:30:40 node-2 kernel: [    0.504069] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 31 18:30:40 node-2 kernel: [    0.504413] pnp: PnP ACPI: found 10 devices
Oct 31 18:30:40 node-2 kernel: [    0.504414] ACPI: bus type PNP unregistered
Oct 31 18:30:40 node-2 kernel: [    0.510806] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 31 18:30:40 node-2 kernel: [    0.510808] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 31 18:30:40 node-2 kernel: [    0.510811] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 31 18:30:40 node-2 kernel: [    0.510815] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 31 18:30:40 node-2 kernel: [    0.510817] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.510832] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.510861] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 31 18:30:40 node-2 kernel: [    0.510876] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 31 18:30:40 node-2 kernel: [    0.510905] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 31 18:30:40 node-2 kernel: [    0.510919] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 31 18:30:40 node-2 kernel: [    0.510948] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 31 18:30:40 node-2 kernel: [    0.510963] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 31 18:30:40 node-2 kernel: [    0.510995] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 31 18:30:40 node-2 kernel: [    0.510997] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511012] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511041] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 31 18:30:40 node-2 kernel: [    0.511042] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511057] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511086] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 31 18:30:40 node-2 kernel: [    0.511088] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511090] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511094] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 31 18:30:40 node-2 kernel: [    0.511096] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511099] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511102] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 31 18:30:40 node-2 kernel: [    0.511107] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 31 18:30:40 node-2 kernel: [    0.511115] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 31 18:30:40 node-2 kernel: [    0.511118] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 31 18:30:40 node-2 kernel: [    0.511125] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 31 18:30:40 node-2 kernel: [    0.511126] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 31 18:30:40 node-2 kernel: [    0.511127] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 31 18:30:40 node-2 kernel: [    0.511127] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 31 18:30:40 node-2 kernel: [    0.511128] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 31 18:30:40 node-2 kernel: [    0.511129] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 31 18:30:40 node-2 kernel: [    0.511130] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 31 18:30:40 node-2 kernel: [    0.511131] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 31 18:30:40 node-2 kernel: [    0.511132] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511133] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511134] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511135] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511135] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511136] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511137] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511138] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511139] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 31 18:30:40 node-2 kernel: [    0.511140] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511141] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 31 18:30:40 node-2 kernel: [    0.511142] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 31 18:30:40 node-2 kernel: [    0.511143] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 31 18:30:40 node-2 kernel: [    0.511144] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 31 18:30:40 node-2 kernel: [    0.511146] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 31 18:30:40 node-2 kernel: [    0.511147] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 31 18:30:40 node-2 kernel: [    0.511188] NET: Registered protocol family 2
Oct 31 18:30:40 node-2 kernel: [    0.511443] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.511783] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.511928] TCP: Hash tables configured (established 262144 bind 65536)
Oct 31 18:30:40 node-2 kernel: [    0.511970] TCP: reno registered
Oct 31 18:30:40 node-2 kernel: [    0.511999] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.512093] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.512239] NET: Registered protocol family 1
Oct 31 18:30:40 node-2 kernel: [    0.547580] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 31 18:30:40 node-2 kernel: [    0.547587] PCI: CLS 64 bytes, default 64
Oct 31 18:30:40 node-2 kernel: [    0.547630] Trying to unpack rootfs image as initramfs...
Oct 31 18:30:40 node-2 kernel: [    0.766787] Freeing initrd memory: 20368K (ffff880035828000 - ffff880036c0c000)
Oct 31 18:30:40 node-2 kernel: [    0.766823] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 31 18:30:40 node-2 kernel: [    0.766826] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct 31 18:30:40 node-2 kernel: [    0.767227] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767234] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767238] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767244] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767256] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767283] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767292] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767301] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767309] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767318] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767325] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767331] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767338] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767346] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767353] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767361] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 31 18:30:40 node-2 kernel: [    0.767434] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 31 18:30:40 node-2 kernel: [    0.767437] Scanning for low memory corruption every 60 seconds
Oct 31 18:30:40 node-2 kernel: [    0.767834] Initialise system trusted keyring
Oct 31 18:30:40 node-2 kernel: [    0.767889] audit: initializing netlink socket (disabled)
Oct 31 18:30:40 node-2 kernel: [    0.767906] type=2000 audit(1477938603.720:1): initialized
Oct 31 18:30:40 node-2 kernel: [    0.785635] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 31 18:30:40 node-2 kernel: [    0.787129] zbud: loaded
Oct 31 18:30:40 node-2 kernel: [    0.787262] VFS: Disk quotas dquot_6.5.2
Oct 31 18:30:40 node-2 kernel: [    0.787298] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 31 18:30:40 node-2 kernel: [    0.787669] fuse init (API version 7.22)
Oct 31 18:30:40 node-2 kernel: [    0.787724] msgmni has been set to 32768
Oct 31 18:30:40 node-2 kernel: [    0.787780] Key type big_key registered
Oct 31 18:30:40 node-2 kernel: [    0.788305] Key type asymmetric registered
Oct 31 18:30:40 node-2 kernel: [    0.788307] Asymmetric key parser 'x509' registered
Oct 31 18:30:40 node-2 kernel: [    0.788330] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 31 18:30:40 node-2 kernel: [    0.788396] io scheduler noop registered
Oct 31 18:30:40 node-2 kernel: [    0.788398] io scheduler deadline registered (default)
Oct 31 18:30:40 node-2 kernel: [    0.788416] io scheduler cfq registered
Oct 31 18:30:40 node-2 kernel: [    0.788841] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    0.788965] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    0.789077] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    0.789236] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    0.789347] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    0.789445] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    0.789854] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 31 18:30:40 node-2 kernel: [    0.789904] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 31 18:30:40 node-2 kernel: [    0.789920] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 31 18:30:40 node-2 kernel: [    0.789933] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789936] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789938] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 31 18:30:40 node-2 kernel: [    0.789944] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789946] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789947] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789948] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789950] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789951] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789953] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789954] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789956] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789957] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789958] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789960] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789962] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 31 18:30:40 node-2 kernel: [    0.789967] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789970] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 31 18:30:40 node-2 kernel: [    0.789982] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789985] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 31 18:30:40 node-2 kernel: [    0.789996] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.789998] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 31 18:30:40 node-2 kernel: [    0.790001] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 31 18:30:40 node-2 kernel: [    0.790044] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 31 18:30:40 node-2 kernel: [    0.790050] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 31 18:30:40 node-2 kernel: [    0.790055] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 31 18:30:40 node-2 kernel: [    0.790072] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 31 18:30:40 node-2 kernel: [    0.790112] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 31 18:30:40 node-2 kernel: [    0.790113] vesafb: scrolling: redraw
Oct 31 18:30:40 node-2 kernel: [    0.790115] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 31 18:30:40 node-2 kernel: [    0.810926] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 31 18:30:40 node-2 kernel: [    0.819453] Console: switching to colour frame buffer device 80x30
Oct 31 18:30:40 node-2 kernel: [    0.828142] fb0: VESA VGA frame buffer device
Oct 31 18:30:40 node-2 kernel: [    0.828337] intel_idle: MWAIT substates: 0x2120
Oct 31 18:30:40 node-2 kernel: [    0.828338] intel_idle: v0.4 model 0x3F
Oct 31 18:30:40 node-2 kernel: [    0.828339] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 31 18:30:40 node-2 kernel: [    0.828573] ipmi message handler version 39.2
Oct 31 18:30:40 node-2 kernel: [    0.828854] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 31 18:30:40 node-2 kernel: [    0.829285] ACPI: AC Adapter [P111] (on-line)
Oct 31 18:30:40 node-2 kernel: [    0.834510] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 31 18:30:40 node-2 kernel: [    0.845541] ACPI: Power Button [PWRB]
Oct 31 18:30:40 node-2 kernel: [    0.851312] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 31 18:30:40 node-2 kernel: [    0.862998] ACPI: Power Button [PWRF]
Oct 31 18:30:40 node-2 kernel: [    0.881059] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 31 18:30:40 node-2 kernel: [    0.892751] pstore: Registered erst as persistent store backend
Oct 31 18:30:40 node-2 kernel: [    0.898980] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 31 18:30:40 node-2 kernel: [    0.910997] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 31 18:30:40 node-2 kernel: [    0.937779] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 31 18:30:40 node-2 kernel: [    0.971139] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 31 18:30:40 node-2 kernel: [    0.985281] Linux agpgart interface v0.103
Oct 31 18:30:40 node-2 kernel: [    0.992941] brd: module loaded
Oct 31 18:30:40 node-2 kernel: [    1.000041] loop: module loaded
Oct 31 18:30:40 node-2 kernel: [    1.006835] libphy: Fixed MDIO Bus: probed
Oct 31 18:30:40 node-2 kernel: [    1.013390] tun: Universal TUN/TAP device driver, 1.6
Oct 31 18:30:40 node-2 kernel: [    1.019860] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 31 18:30:40 node-2 kernel: [    1.026404] PPP generic driver version 2.4.2
Oct 31 18:30:40 node-2 kernel: [    1.032820] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 31 18:30:40 node-2 kernel: [    1.039285] ehci-pci: EHCI PCI platform driver
Oct 31 18:30:40 node-2 kernel: [    1.045801] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 31 18:30:40 node-2 kernel: [    1.052196] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 31 18:30:40 node-2 kernel: [    1.064716] ehci-pci 0000:00:1a.0: debug port 2
Oct 31 18:30:40 node-2 kernel: [    1.074901] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 31 18:30:40 node-2 kernel: [    1.074919] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 31 18:30:40 node-2 kernel: [    1.090987] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 31 18:30:40 node-2 kernel: [    1.097045] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 31 18:30:40 node-2 kernel: [    1.103210] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 31 18:30:40 node-2 kernel: [    1.115101] usb usb1: Product: EHCI Host Controller
Oct 31 18:30:40 node-2 kernel: [    1.121122] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 31 18:30:40 node-2 kernel: [    1.127150] usb usb1: SerialNumber: 0000:00:1a.0
Oct 31 18:30:40 node-2 kernel: [    1.133099] hub 1-0:1.0: USB hub found
Oct 31 18:30:40 node-2 kernel: [    1.138858] hub 1-0:1.0: 2 ports detected
Oct 31 18:30:40 node-2 kernel: [    1.144642] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 31 18:30:40 node-2 kernel: [    1.150217] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 31 18:30:40 node-2 kernel: [    1.161114] ehci-pci 0000:00:1d.0: debug port 2
Oct 31 18:30:40 node-2 kernel: [    1.170429] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 31 18:30:40 node-2 kernel: [    1.170432] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 31 18:30:40 node-2 kernel: [    1.186906] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 31 18:30:40 node-2 kernel: [    1.192104] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 31 18:30:40 node-2 kernel: [    1.197440] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 31 18:30:40 node-2 kernel: [    1.208032] usb usb2: Product: EHCI Host Controller
Oct 31 18:30:40 node-2 kernel: [    1.213510] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 31 18:30:40 node-2 kernel: [    1.219071] usb usb2: SerialNumber: 0000:00:1d.0
Oct 31 18:30:40 node-2 kernel: [    1.224598] hub 2-0:1.0: USB hub found
Oct 31 18:30:40 node-2 kernel: [    1.229957] hub 2-0:1.0: 2 ports detected
Oct 31 18:30:40 node-2 kernel: [    1.235284] ehci-platform: EHCI generic platform driver
Oct 31 18:30:40 node-2 kernel: [    1.240537] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 31 18:30:40 node-2 kernel: [    1.245878] ohci-pci: OHCI PCI platform driver
Oct 31 18:30:40 node-2 kernel: [    1.251196] ohci-platform: OHCI generic platform driver
Oct 31 18:30:40 node-2 kernel: [    1.256409] uhci_hcd: USB Universal Host Controller Interface driver
Oct 31 18:30:40 node-2 kernel: [    1.261764] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 31 18:30:40 node-2 kernel: [    1.454686] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 31 18:30:40 node-2 kernel: [    1.626930] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 31 18:30:40 node-2 kernel: [    1.632469] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 31 18:30:40 node-2 kernel: [    1.638198] hub 1-1:1.0: USB hub found
Oct 31 18:30:40 node-2 kernel: [    1.643667] hub 1-1:1.0: 6 ports detected
Oct 31 18:30:40 node-2 kernel: [    1.758419] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 31 18:30:40 node-2 kernel: [    1.762890] tsc: Refined TSC clocksource calibration: 3491.889 MHz
Oct 31 18:30:40 node-2 kernel: [    2.026591] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 31 18:30:40 node-2 kernel: [    2.032236] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 31 18:30:40 node-2 kernel: [    2.038111] hub 2-1:1.0: USB hub found
Oct 31 18:30:40 node-2 kernel: [    2.043953] hub 2-1:1.0: 8 ports detected
Oct 31 18:30:40 node-2 kernel: [    2.303605] i8042: No controller found
Oct 31 18:30:40 node-2 kernel: [    2.309060] mousedev: PS/2 mouse device common for all mice
Oct 31 18:30:40 node-2 kernel: [    2.314596] rtc_cmos 00:02: RTC can wake from S4
Oct 31 18:30:40 node-2 kernel: [    2.320208] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 31 18:30:40 node-2 kernel: [    2.322015] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 31 18:30:40 node-2 kernel: [    2.331390] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 31 18:30:40 node-2 kernel: [    2.342539] device-mapper: uevent: version 1.0.3
Oct 31 18:30:40 node-2 kernel: [    2.348198] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 31 18:30:40 node-2 kernel: [    2.359469] ledtrig-cpu: registered to indicate activity on CPUs
Oct 31 18:30:40 node-2 kernel: [    2.365409] TCP: cubic registered
Oct 31 18:30:40 node-2 kernel: [    2.371300] NET: Registered protocol family 10
Oct 31 18:30:40 node-2 kernel: [    2.377377] NET: Registered protocol family 17
Oct 31 18:30:40 node-2 kernel: [    2.383064] Key type dns_resolver registered
Oct 31 18:30:40 node-2 kernel: [    2.389024] Loading compiled-in X.509 certificates
Oct 31 18:30:40 node-2 kernel: [    2.395190] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 31 18:30:40 node-2 kernel: [    2.406631] registered taskstats version 1
Oct 31 18:30:40 node-2 kernel: [    2.414668] Key type trusted registered
Oct 31 18:30:40 node-2 kernel: [    2.422234] Key type encrypted registered
Oct 31 18:30:40 node-2 kernel: [    2.427699] AppArmor: AppArmor sha1 policy hashing enabled
Oct 31 18:30:40 node-2 kernel: [    2.433175] IMA: No TPM chip found, activating TPM-bypass!
Oct 31 18:30:40 node-2 kernel: [    2.439320] regulator-dummy: disabling
Oct 31 18:30:40 node-2 kernel: [    2.444882]   Magic number: 4:742:545
Oct 31 18:30:40 node-2 kernel: [    2.450279] tty ttyS21: hash matches
Oct 31 18:30:40 node-2 kernel: [    2.454422] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 31 18:30:40 node-2 kernel: [    2.454423] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 31 18:30:40 node-2 kernel: [    2.454424] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 31 18:30:40 node-2 kernel: [    2.454425] usb 2-1.4: Manufacturer: Avocent
Oct 31 18:30:40 node-2 kernel: [    2.454426] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 31 18:30:40 node-2 kernel: [    2.488461] acpi device:131: hash matches
Oct 31 18:30:40 node-2 kernel: [    2.494137] rtc_cmos 00:02: setting system clock to 2016-10-31 18:30:05 UTC (1477938605)
Oct 31 18:30:40 node-2 kernel: [    2.506503] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 31 18:30:40 node-2 kernel: [    2.512058] EDD information not available.
Oct 31 18:30:40 node-2 kernel: [    2.517574] PM: Hibernation image not present or could not be loaded.
Oct 31 18:30:40 node-2 kernel: [    2.518433] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 31 18:30:40 node-2 kernel: [    2.529484] Write protecting the kernel read-only data: 12288k
Oct 31 18:30:40 node-2 kernel: [    2.535535] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 31 18:30:40 node-2 kernel: [    2.547855] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 31 18:30:40 node-2 kernel: [    2.579664] device-mapper: multipath: version 1.6.0 loaded
Oct 31 18:30:40 node-2 kernel: [    2.587587] systemd-udevd[219]: starting version 204
Oct 31 18:30:40 node-2 kernel: [    2.613270] md: linear personality registered for level -1
Oct 31 18:30:40 node-2 kernel: [    2.627397] md: multipath personality registered for level -4
Oct 31 18:30:40 node-2 kernel: [    2.635412] md: raid0 personality registered for level 0
Oct 31 18:30:40 node-2 kernel: [    2.644076] md: raid1 personality registered for level 1
Oct 31 18:30:40 node-2 kernel: [    2.650382] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 31 18:30:40 node-2 kernel: [    2.650383] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 31 18:30:40 node-2 kernel: [    2.661960] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct 31 18:30:40 node-2 kernel: [    2.661961] 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 31 18:30:40 node-2 kernel: [    2.661962] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 31 18:30:40 node-2 kernel: [    2.662276] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.662425] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.662455] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.662554] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.662871] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.677032] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct 31 18:30:40 node-2 kernel: [    2.677046] 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 31 18:30:40 node-2 kernel: [    2.677053] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 31 18:30:40 node-2 kernel: [    2.677301] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.677413] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.677506] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.677563] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.677769] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.677875] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.678177] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.694893] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct 31 18:30:40 node-2 kernel: [    2.694895] 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 31 18:30:40 node-2 kernel: [    2.694899] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 31 18:30:40 node-2 kernel: [    2.695089] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.695169] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.695261] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.695342] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.695726] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.708960] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct 31 18:30:40 node-2 kernel: [    2.708977] 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 31 18:30:40 node-2 kernel: [    2.708978] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 31 18:30:40 node-2 kernel: [    2.709132] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.709282] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.709425] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.709543] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.709795] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.851704] Switched to clocksource tsc
Oct 31 18:30:40 node-2 kernel: [    2.851735] hidraw: raw HID events driver (C) Jiri Kosina
Oct 31 18:30:40 node-2 kernel: [    2.851848] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 31 18:30:40 node-2 kernel: [    2.853122] megasas: FW now in Ready state
Oct 31 18:30:40 node-2 kernel: [    2.853634] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.853783] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.853892] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854041] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854146] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854316] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854438] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854617] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854703] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854794] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854859] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854923] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.854990] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.855099] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.855210] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.855352] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Oct 31 18:30:40 node-2 kernel: [    2.855958] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 31 18:30:40 node-2 kernel: [    2.894274] usbcore: registered new interface driver usbhid
Oct 31 18:30:40 node-2 kernel: [    2.901154] usbhid: USB HID core driver
Oct 31 18:30:40 node-2 kernel: [    2.908857] 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 31 18:30:40 node-2 kernel: [    2.922624] 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 31 18:30:40 node-2 kernel: [    2.936400] 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 31 18:30:40 node-2 kernel: [    2.950368] 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 31 18:30:40 node-2 kernel: [    2.957408] raid6: sse2x1    9238 MB/s
Oct 31 18:30:40 node-2 kernel: [    2.971695] 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 31 18:30:40 node-2 kernel: [    2.985877] 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 31 18:30:40 node-2 kernel: [    3.025338] raid6: sse2x2   14467 MB/s
Oct 31 18:30:40 node-2 kernel: [    3.097275] raid6: sse2x4   16839 MB/s
Oct 31 18:30:40 node-2 kernel: [    3.169211] raid6: avx2x1   22365 MB/s
Oct 31 18:30:40 node-2 kernel: [    3.193194] megasas:IOC Init cmd success
Oct 31 18:30:40 node-2 kernel: [    3.221176] megasas: INIT adapter done
Oct 31 18:30:40 node-2 kernel: [    3.241151] raid6: avx2x2   20740 MB/s
Oct 31 18:30:40 node-2 kernel: [    3.297107] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 31 18:30:40 node-2 kernel: [    3.303757] scsi0 : LSI SAS based MegaRAID driver
Oct 31 18:30:40 node-2 kernel: [    3.310801] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 31 18:30:40 node-2 kernel: [    3.313288] raid6: avx2x4   23377 MB/s
Oct 31 18:30:40 node-2 kernel: [    3.313288] raid6: using algorithm avx2x4 (23377 MB/s)
Oct 31 18:30:40 node-2 kernel: [    3.313289] raid6: using avx2x2 recovery algorithm
Oct 31 18:30:40 node-2 kernel: [    3.343915] xor: automatically using best checksumming function:
Oct 31 18:30:40 node-2 kernel: [    3.353988] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 31 18:30:40 node-2 kernel: [    3.369088] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 31 18:30:40 node-2 kernel: [    3.375470] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 31 18:30:40 node-2 kernel: [    3.388093] sd 0:2:0:0: [sda] Write Protect is off
Oct 31 18:30:40 node-2 kernel: [    3.389052]    avx       : 36503.000 MB/sec
Oct 31 18:30:40 node-2 kernel: [    3.400157] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 31 18:30:40 node-2 kernel: [    3.400184] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 31 18:30:40 node-2 kernel: [    3.412089] async_tx: api initialized (async)
Oct 31 18:30:40 node-2 kernel: [    3.421807] md: raid6 personality registered for level 6
Oct 31 18:30:40 node-2 kernel: [    3.427567] md: raid5 personality registered for level 5
Oct 31 18:30:40 node-2 kernel: [    3.433113] md: raid4 personality registered for level 4
Oct 31 18:30:40 node-2 kernel: [    3.438515]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 31 18:30:40 node-2 kernel: [    3.444209] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 31 18:30:40 node-2 kernel: [    3.451121] md: raid10 personality registered for level 10
Oct 31 18:30:40 node-2 kernel: [    3.498909] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Oct 31 18:30:40 node-2 kernel: [    3.566620] random: lvm urandom read with 29 bits of entropy available
Oct 31 18:30:40 node-2 kernel: [    3.805559] bio: create slab <bio-1> at 1
Oct 31 18:30:40 node-2 kernel: [    4.573207] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 18:30:40 node-2 kernel: [    5.440616] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 31 18:30:40 node-2 kernel: [    5.496078] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 31 18:30:40 node-2 kernel: [    5.599235] random: nonblocking pool is initialized
Oct 31 18:30:40 node-2 kernel: [    5.659397] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 31 18:30:40 node-2 kernel: [    5.695304] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 31 18:30:40 node-2 kernel: [    5.740615] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 18:30:40 node-2 kernel: [    5.940008] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 31 18:30:40 node-2 kernel: [    5.977296] XFS (dm-0): Mounting Filesystem
Oct 31 18:30:40 node-2 kernel: [    6.229931] XFS (dm-0): Ending clean mount
Oct 31 18:30:40 node-2 kernel: [    6.291411] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 18:30:40 node-2 kernel: [    6.324365] XFS (dm-1): Mounting Filesystem
Oct 31 18:30:40 node-2 kernel: [    6.447471] XFS (dm-1): Ending clean mount
Oct 31 18:30:40 node-2 kernel: [    8.434153] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 31 18:30:40 node-2 kernel: [    8.462477] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 31 18:30:40 node-2 kernel: [    8.693086] systemd-udevd[770]: starting version 204
Oct 31 18:30:40 node-2 kernel: [    8.938097] power_meter ACPI000D:00: Found ACPI power meter.
Oct 31 18:30:40 node-2 kernel: [    8.938110] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 31 18:30:40 node-2 kernel: [    8.950176] wmi: Mapper loaded
Oct 31 18:30:40 node-2 kernel: [    8.955133] IPMI System Interface driver.
Oct 31 18:30:40 node-2 kernel: [    8.955169] ipmi_si: probing via ACPI
Oct 31 18:30:40 node-2 kernel: [    8.955183] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 31 18:30:40 node-2 kernel: [    8.955184] ipmi_si: Adding ACPI-specified kcs state machine
Oct 31 18:30:40 node-2 kernel: [    8.955190] ipmi_si: probing via SMBIOS
Oct 31 18:30:40 node-2 kernel: [    8.955191] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 31 18:30:40 node-2 kernel: [    8.955192] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 31 18:30:40 node-2 kernel: [    8.955193] ipmi_si: probing via SPMI
Oct 31 18:30:40 node-2 kernel: [    8.955194] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 31 18:30:40 node-2 kernel: [    8.955194] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 31 18:30:40 node-2 kernel: [    8.955196] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 31 18:30:40 node-2 kernel: [    9.006772] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 31 18:30:40 node-2 kernel: [    9.006778] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 31 18:30:40 node-2 kernel: [    9.006781] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 31 18:30:40 node-2 kernel: [    9.006782] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 31 18:30:40 node-2 kernel: [    9.006798] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 31 18:30:40 node-2 kernel: [    9.014217] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 31 18:30:40 node-2 kernel: [    9.060689] systemd-udevd[800]: renamed network interface eth0 to enp6s0
Oct 31 18:30:40 node-2 kernel: [    9.088590] systemd-udevd[788]: renamed network interface eth1 to enp7s0
Oct 31 18:30:40 node-2 kernel: [    9.097139] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 31 18:30:40 node-2 kernel: [    9.097144] ipmi_si 00:09: IPMI kcs interface initialized
Oct 31 18:30:40 node-2 kernel: [    9.120513] systemd-udevd[790]: renamed network interface eth2 to enp8s0
Oct 31 18:30:40 node-2 kernel: [    9.167071] systemd-udevd[814]: renamed network interface eth3 to enp9s0
Oct 31 18:30:40 node-2 kernel: [    9.438254] type=1400 audit(1477938612.447:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1040 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.438411] type=1400 audit(1477938612.447:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1040 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.438538] type=1400 audit(1477938612.447:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1040 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.448881] type=1400 audit(1477938612.459:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1041 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.449022] type=1400 audit(1477938612.459:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1041 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.449143] type=1400 audit(1477938612.459:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1041 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.455941] type=1400 audit(1477938612.467:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.456082] type=1400 audit(1477938612.467:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1055 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.456201] type=1400 audit(1477938612.467:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1055 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [    9.469160] type=1400 audit(1477938612.479:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1042 comm="apparmor_parser"
Oct 31 18:30:40 node-2 kernel: [   10.163629] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 31 18:30:40 node-2 kernel: [   10.173575] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 31 18:30:40 node-2 kernel: [   10.391042] enic 0000:06:00.0 enp6s0: Link UP
Oct 31 18:30:40 node-2 kernel: [   10.392307] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 31 18:30:40 node-2 kernel: [   10.399732] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 31 18:30:40 node-2 kernel: [   20.218558] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 31 18:30:41 node-2 failsafe: Failsafe of 120 seconds reached.
Oct 31 18:30:41 node-2 kernel: [   38.463987] init: failsafe main process (8418) killed by TERM signal
Oct 31 18:30:42 node-2 dbus[8460]: [system] AppArmor D-Bus mediation is enabled
Oct 31 18:30:42 node-2 kernel: [   38.636830] audit_printk_skb: 30 callbacks suppressed
Oct 31 18:30:42 node-2 kernel: [   38.636831] type=1400 audit(1477938642.133:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8536 comm="apparmor_parser"
Oct 31 18:30:42 node-2 kernel: [   38.637107] type=1400 audit(1477938642.133:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8535 comm="apparmor_parser"
Oct 31 18:30:42 node-2 kernel: [   38.637112] type=1400 audit(1477938642.133:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8535 comm="apparmor_parser"
Oct 31 18:30:42 node-2 kernel: [   38.637115] type=1400 audit(1477938642.133:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8535 comm="apparmor_parser"
Oct 31 18:30:42 node-2 kernel: [   38.637348] type=1400 audit(1477938642.133:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8535 comm="apparmor_parser"
Oct 31 18:30:42 node-2 kernel: [   38.637350] type=1400 audit(1477938642.133:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8535 comm="apparmor_parser"
Oct 31 18:30:42 node-2 kernel: [   38.637463] type=1400 audit(1477938642.133:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8535 comm="apparmor_parser"
Oct 31 18:30:42 node-2 kernel: [   38.704507] type=1400 audit(1477938642.201:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8538 comm="apparmor_parser"
Oct 31 18:30:42 node-2 anacron[8611]: Anacron 2.3 started on 2016-10-31
Oct 31 18:30:42 node-2 cron[8576]: (CRON) INFO (pidfile fd = 3)
Oct 31 18:30:42 node-2 cron[8617]: (CRON) STARTUP (fork ok)
Oct 31 18:30:42 node-2 anacron[8611]: Will run job `cron.daily' in 5 min.
Oct 31 18:30:42 node-2 anacron[8611]: Will run job `cron.weekly' in 10 min.
Oct 31 18:30:42 node-2 anacron[8611]: Will run job `cron.monthly' in 15 min.
Oct 31 18:30:42 node-2 anacron[8611]: Jobs will be executed sequentially
Oct 31 18:30:42 node-2 multipathd: path checkers start up
Oct 31 18:30:42 node-2 cron[8617]: (CRON) INFO (Running @reboot jobs)
Oct 31 18:30:42 node-2 postfix/master[8755]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 31 18:30:45 node-2 puppet-agent[8939]: Reopening log files
Oct 31 18:30:46 node-2 puppet-agent[8939]: Could not request certificate: Connection refused - connect(2)
Oct 31 18:30:59 node-2 puppet-user[9018]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 31 18:30:59 node-2 puppet-user[9018]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 31 18:30:59 node-2 puppet-user[9018]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 31 18:30:59 node-2 puppet-user[9018]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 31 18:30:59 node-2 puppet-user[9018]: Finished catalog run in 0.75 seconds
Oct 31 18:31:01 node-2 CRON[9730]: (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 31 18:31:01 node-2 multipathd: uevent trigger error
Oct 31 18:31:01 node-2 puppet-user[9453]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 31 18:31:01 node-2 puppet-user[9453]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Oct 31 18:31:01 node-2 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 31 18:31:01 node-2 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 31 18:31:01 node-2 puppet-user[9453]: (/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 31 18:31:01 node-2 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 31 18:31:01 node-2 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 31 18:31:01 node-2 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 31 18:31:01 node-2 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 31 18:31:01 node-2 puppet-user[9453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 31 18:31:01 node-2 puppet-user[9453]: Finished catalog run in 0.06 seconds
Oct 31 18:31:03 node-2 puppet-user[9934]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 31 18:31:03 node-2 puppet-user[9934]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Oct 31 18:31:03 node-2 puppet-user[9934]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 31 18:31:03 node-2 puppet-user[9934]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 31 18:31:03 node-2 puppet-user[9934]: Finished catalog run in 0.04 seconds
Oct 31 18:31:05 node-2 puppet-user[10401]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 31 18:31:05 node-2 puppet-user[10401]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 31 18:31:05 node-2 puppet-user[10401]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 31 18:31:05 node-2 puppet-user[10401]: Finished catalog run in 0.03 seconds
Oct 31 18:31:06 node-2 puppet-user[10862]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 31 18:31:06 node-2 puppet-user[10862]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Oct 31 18:31:06 node-2 puppet-user[10862]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 31 18:31:07 node-2 puppet-user[10862]: (/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 31 18:31:07 node-2 puppet-user[10862]: (/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 31 18:31:07 node-2 puppet-user[10862]: (/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 31 18:31:08 node-2 puppet-user[10862]: Finished catalog run in 1.20 seconds
Oct 31 18:31:09 node-2 puppet-user[11401]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 31 18:31:09 node-2 puppet-user[11401]: Compiled catalog for node-2.domain.tld in environment production in 0.27 seconds
Oct 31 18:31:09 node-2 puppet-user[11401]: (/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 31 18:31:09 node-2 puppet-user[11401]: (/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 31 18:31:09 node-2 puppet-user[11401]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 31 18:31:09 node-2 puppet-user[11401]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 31 18:31:09 node-2 puppet-user[11401]: (/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 31 18:31:10 node-2 puppet-user[11401]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 31 18:31:10 node-2 puppet-user[11401]: Finished catalog run in 0.36 seconds
Oct 31 18:31:11 node-2 puppet-user[11888]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 31 18:31:11 node-2 puppet-user[11888]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Oct 31 18:31:11 node-2 puppet-user[11888]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 31 18:31:11 node-2 kernel: [   68.571484] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 31 18:31:11 node-2 kernel: [   68.571534] 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 31 18:31:11 node-2 puppet-user[11888]: (/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 31 18:31:11 node-2 puppet-user[11888]: Finished catalog run in 0.06 seconds
Oct 31 18:31:13 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 31 18:31:13 node-2 nailgun-agent: D, [2016-10-31T18:31:01.367970 #9735] DEBUG -- : Sleep for 12 seconds before sending request
Oct 31 18:31:13 node-2 nailgun-agent: I, [2016-10-31T18:31:13.389807 #9735]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 31 18:31:13 node-2 puppet-user[12354]: (Scope(Class[main])) MODULAR: sync_time
Oct 31 18:31:13 node-2 puppet-user[12354]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct 31 18:31:13 node-2 nailgun-agent: D, [2016-10-31T18:31:13.794320 #9735] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 31 18:31:13 node-2 ntpdate[13040]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 31 18:31:20 node-2 ntpdate[13040]: adjust time server 10.20.0.2 offset 0.000475 sec
Oct 31 18:31:20 node-2 puppet-user[12354]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 31 18:31:20 node-2 puppet-user[12354]: Finished catalog run in 6.18 seconds
Oct 31 18:31:24 node-2 puppet-user[13232]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 31 18:31:24 node-2 puppet-user[13232]: Compiled catalog for node-2.domain.tld in environment production in 0.11 seconds
Oct 31 18:31:24 node-2 puppet-user[13232]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 31 18:31:24 node-2 puppet-user[13232]: (/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 31 18:31:24 node-2 puppet-user[13232]: Finished catalog run in 0.08 seconds
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.658601 #9735] DEBUG -- : Trying to find block devices
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.658673 #9735] DEBUG -- : Found block device: sda
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.658720 #9735] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.658745 #9735] DEBUG -- : Trying to get list of physical devices
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.658920 #9735] DEBUG -- : Getting udev properties for device: sda
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.660761 #9735] 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 31 18:31:25 node-2 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99043", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.660801 #9735] DEBUG -- : Trying to find out if device sda is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.660847 #9735] DEBUG -- : Device sda removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.660863 #9735] DEBUG -- : Device sda seems to be appropriate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.661347 #9735] DEBUG -- : Getting udev properties for device: dm-0
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.663297 #9735] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-lKEadWdW70vl4BCjYdYVfcnct6aHziSMMfekZFbb66VGsvj3BVS1O5uWtDdEumsC /dev/disk/by-uuid/59185d0c-ab41-4639-8b3b-a5ede173b888 /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-lKEadWdW70vl4BCjYdYVfcnct6aHziSMMfekZFbb66VGsvj3BVS1O5uWtDdEumsC", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"59185d0c-ab41-4639-8b3b-a5ede173b888", "ID_FS_UUID_ENC"=>"59185d0c-ab41-4639-8b3b-a5ede173b888", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60770", "nomdmonddf"=>"1", "nomd
Oct 31 18:31:25 node-2 nailgun-agent: monisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.663332 #9735] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.663369 #9735] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.663386 #9735] DEBUG -- : Device dm-0 seems to be appropriate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.663405 #9735] DEBUG -- : Getting udev properties for device: dm-1
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.665202 #9735] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-rjhEi7AS1FXmzvKpncSy65nY0wXzoz2mmQ8r9zKScoUn5VTk8DIYcquqF467q4eX /dev/disk/by-uuid/987ed023-0f3d-41e1-8a67-f4744d83332a /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-rjhEi7AS1FXmzvKpncSy65nY0wXzoz2mmQ8r9zKScoUn5VTk8DIYcquqF467q4eX", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"987ed023-0f3d-41e1-8a67-f4744d83332a", "ID_FS_UUID_ENC"=>"987ed023-0f3d-41e1-8a67-f4744d83332a", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98
Oct 31 18:31:25 node-2 nailgun-agent: 819", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.665235 #9735] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.665272 #9735] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.665290 #9735] DEBUG -- : Device dm-1 seems to be appropriate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.665309 #9735] DEBUG -- : Getting udev properties for device: dm-2
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.666949 #9735] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-NOUqhGSFA5AN2hwVQL3flkPx6e5bAtmu4T8XxpFUVnW6scp9qWMqSapssBmE1xIo /dev/disk/by-uuid/f3341877-5ce7-4fb9-b4c1-a67c8616fe96 /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-NOUqhGSFA5AN2hwVQL3flkPx6e5bAtmu4T8XxpFUVnW6scp9qWMqSapssBmE1xIo", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f3341877-5ce7-4fb9-b4c1-a67c8616fe96", "ID_FS_UUID_ENC"=>"f3341877-5ce7-4fb9-b4c1-a67c8616fe96", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12585", "nomdmond
Oct 31 18:31:25 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.666974 #9735] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.667003 #9735] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.667017 #9735] DEBUG -- : Device dm-2 seems to be appropriate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.667031 #9735] DEBUG -- : Getting udev properties for device: dm-3
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.668708 #9735] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-UJTfAILwe6pxM4hLKZckIhxWKc1Q38h8MryPwibftNGyqt8znYV9Avw1cVIEbyfT /dev/disk/by-uuid/8fc37d1e-51de-43cb-a046-01f87ff1b60b /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-UJTfAILwe6pxM4hLKZckIhxWKc1Q38h8MryPwibftNGyqt8znYV9Avw1cVIEbyfT", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8fc37d1e-51de-43cb-a046-01f87ff1b60b", "ID_FS_UUID_ENC"=>"8fc37d1e-51de-43cb-a046-01f87ff1b60b", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15805", "nomdmonddf"=>"1", 
Oct 31 18:31:25 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.668732 #9735] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.668771 #9735] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.668784 #9735] DEBUG -- : Device dm-3 seems to be appropriate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.668798 #9735] DEBUG -- : Getting udev properties for device: dm-4
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.670491 #9735] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-K9pdc7Q7Mvfh03ReKGr4BhYvs828fWjUlw4lkvAcpFDG1Ofyq2dvOta8CQHbzxGe /dev/disk/by-uuid/5fa71a40-7532-4fc2-8e54-19d35da77e21 /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-K9pdc7Q7Mvfh03ReKGr4BhYvs828fWjUlw4lkvAcpFDG1Ofyq2dvOta8CQHbzxGe", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"5fa71a40-7532-4fc2-8e54-19d35da77e21", "ID_FS_UUID_ENC"=>"5fa71a40-7532-4fc2-8e54-19d35da77e21", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17410", "nomdmonddf"=>"1", "nomd
Oct 31 18:31:25 node-2 nailgun-agent: monisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.670523 #9735] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.670559 #9735] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.670577 #9735] DEBUG -- : Device dm-4 seems to be appropriate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.670595 #9735] DEBUG -- : Getting udev properties for device: dm-5
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.672278 #9735] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-K9pdc7Q7Mvfh03ReKGr4BhYvs828fWjUxfybyLVpkXfo6CpW0f1PIxwPmq3RG1OO /dev/disk/by-uuid/5a377c6d-d4eb-4988-864e-abbfcc106ac9 /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-K9pdc7Q7Mvfh03ReKGr4BhYvs828fWjUxfybyLVpkXfo6CpW0f1PIxwPmq3RG1OO", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"5a377c6d-d4eb-4988-864e-abbfcc106ac9", "ID_FS_UUID_ENC"=>"5a377c6d-d4eb-4988-864e-abbfcc106ac9", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17839", "nomdmonddf"=>"1", "nomdmonisw"
Oct 31 18:31:25 node-2 nailgun-agent: =>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.672302 #9735] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.672394 #9735] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.672408 #9735] DEBUG -- : Device dm-5 seems to be appropriate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.672422 #9735] DEBUG -- : Getting udev properties for device: ram0
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.673843 #9735] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60784", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.673892 #9735] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.673927 #9735] DEBUG -- : Device ram0 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.673946 #9735] DEBUG -- : Getting udev properties for device: ram1
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.676028 #9735] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60871", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.676071 #9735] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.676149 #9735] DEBUG -- : Device ram1 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.676173 #9735] DEBUG -- : Getting udev properties for device: ram2
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.677748 #9735] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61599", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.677774 #9735] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.677854 #9735] DEBUG -- : Device ram2 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.677873 #9735] DEBUG -- : Getting udev properties for device: ram3
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.679505 #9735] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61687", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.679530 #9735] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.679566 #9735] DEBUG -- : Device ram3 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.679586 #9735] DEBUG -- : Getting udev properties for device: ram4
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.681351 #9735] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61785", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.681378 #9735] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.681414 #9735] DEBUG -- : Device ram4 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.681435 #9735] DEBUG -- : Getting udev properties for device: ram5
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.682985 #9735] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61874", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.683012 #9735] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.683050 #9735] DEBUG -- : Device ram5 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.683071 #9735] DEBUG -- : Getting udev properties for device: ram6
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.684738 #9735] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61965", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.684765 #9735] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.684799 #9735] DEBUG -- : Device ram6 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.684819 #9735] DEBUG -- : Getting udev properties for device: ram7
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.686652 #9735] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62032", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.686680 #9735] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.686713 #9735] DEBUG -- : Device ram7 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.686758 #9735] DEBUG -- : Getting udev properties for device: ram8
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.688537 #9735] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62115", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.688567 #9735] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.688603 #9735] DEBUG -- : Device ram8 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.688653 #9735] DEBUG -- : Getting udev properties for device: ram9
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.690205 #9735] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62213", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.690230 #9735] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.690269 #9735] DEBUG -- : Device ram9 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.690312 #9735] DEBUG -- : Getting udev properties for device: loop0
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.691734 #9735] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59872", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.691780 #9735] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.691828 #9735] DEBUG -- : Device loop0 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.691896 #9735] DEBUG -- : Getting udev properties for device: loop1
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.693718 #9735] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59975", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.693743 #9735] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.693775 #9735] DEBUG -- : Device loop1 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.693815 #9735] DEBUG -- : Getting udev properties for device: loop2
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.695527 #9735] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60245", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.695558 #9735] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.695601 #9735] DEBUG -- : Device loop2 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.695674 #9735] DEBUG -- : Getting udev properties for device: loop3
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.697510 #9735] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60321", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.697534 #9735] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.697568 #9735] DEBUG -- : Device loop3 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.697588 #9735] DEBUG -- : Getting udev properties for device: loop4
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.699094 #9735] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60415", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.699115 #9735] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.699186 #9735] DEBUG -- : Device loop4 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.699206 #9735] DEBUG -- : Getting udev properties for device: loop5
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.700655 #9735] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60495", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.700677 #9735] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.700707 #9735] DEBUG -- : Device loop5 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.700725 #9735] DEBUG -- : Getting udev properties for device: loop6
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.702164 #9735] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60605", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.702187 #9735] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.702229 #9735] DEBUG -- : Device loop6 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.702248 #9735] DEBUG -- : Getting udev properties for device: loop7
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.703675 #9735] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60686", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.703698 #9735] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.703726 #9735] DEBUG -- : Device loop7 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.703784 #9735] DEBUG -- : Getting udev properties for device: ram10
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.705493 #9735] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60987", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.705520 #9735] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.705553 #9735] DEBUG -- : Device ram10 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.705573 #9735] DEBUG -- : Getting udev properties for device: ram11
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.707280 #9735] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61110", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.707307 #9735] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.707383 #9735] DEBUG -- : Device ram11 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.707403 #9735] DEBUG -- : Getting udev properties for device: ram12
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.708924 #9735] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61219", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.708954 #9735] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.709001 #9735] DEBUG -- : Device ram12 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.709027 #9735] DEBUG -- : Getting udev properties for device: ram13
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.710630 #9735] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61313", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.710661 #9735] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.710708 #9735] DEBUG -- : Device ram13 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.710747 #9735] DEBUG -- : Getting udev properties for device: ram14
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.712361 #9735] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61417", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.712392 #9735] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.712447 #9735] DEBUG -- : Device ram14 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.712503 #9735] DEBUG -- : Getting udev properties for device: ram15
Oct 31 18:31:25 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714059 #9735] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61537", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714083 #9735] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714167 #9735] DEBUG -- : Device ram15 removable parameter: "0"
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714205 #9735] 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 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714222 #9735] DEBUG -- : Block device seems to be physical data storage: sda
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714261 #9735] DEBUG -- : Found block device: dm-0
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714291 #9735] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714305 #9735] DEBUG -- : Found block device: dm-1
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714332 #9735] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714343 #9735] DEBUG -- : Found block device: dm-2
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714374 #9735] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714384 #9735] DEBUG -- : Found block device: dm-3
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714395 #9735] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714428 #9735] DEBUG -- : Found block device: dm-4
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714438 #9735] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714447 #9735] DEBUG -- : Found block device: dm-5
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714492 #9735] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714502 #9735] DEBUG -- : Found block device: ram0
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714513 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714522 #9735] DEBUG -- : Found block device: ram1
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714559 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714569 #9735] DEBUG -- : Found block device: ram2
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714579 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714623 #9735] DEBUG -- : Found block device: ram3
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714634 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714643 #9735] DEBUG -- : Found block device: ram4
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714655 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714663 #9735] DEBUG -- : Found block device: ram5
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714715 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714726 #9735] DEBUG -- : Found block device: ram6
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714737 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714745 #9735] DEBUG -- : Found block device: ram7
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714755 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714764 #9735] DEBUG -- : Found block device: ram8
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714833 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714845 #9735] DEBUG -- : Found block device: ram9
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714855 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714864 #9735] DEBUG -- : Found block device: loop0
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714874 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714883 #9735] DEBUG -- : Found block device: loop1
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714929 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714940 #9735] DEBUG -- : Found block device: loop2
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714952 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714961 #9735] DEBUG -- : Found block device: loop3
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714971 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.714980 #9735] DEBUG -- : Found block device: loop4
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715035 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715045 #9735] DEBUG -- : Found block device: loop5
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715054 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715063 #9735] DEBUG -- : Found block device: loop6
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715074 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715083 #9735] DEBUG -- : Found block device: loop7
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715093 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715101 #9735] DEBUG -- : Found block device: ram10
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715139 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715148 #9735] DEBUG -- : Found block device: ram11
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715158 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715166 #9735] DEBUG -- : Found block device: ram12
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715177 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715186 #9735] DEBUG -- : Found block device: ram13
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715196 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715205 #9735] DEBUG -- : Found block device: ram14
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715239 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715249 #9735] DEBUG -- : Found block device: ram15
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715259 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.715292 #9735] 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 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.775531 #9735] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 31 18:31:25 node-2 nailgun-agent: D, [2016-10-31T18:31:25.775591 #9735] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 31 18:31:26 node-2 puppet-user[13708]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 31 18:31:26 node-2 puppet-user[13708]: Compiled catalog for node-2.domain.tld in environment production in 0.52 seconds
Oct 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:26 node-2 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:26 node-2 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:26 node-2 puppet-user[13708]: (/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 31 18:31:27 node-2 puppet-user[13708]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 31 18:31:27 node-2 puppet-user[13708]: Finished catalog run in 0.88 seconds
Oct 31 18:31:29 node-2 puppet-user[14601]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 31 18:31:29 node-2 puppet-user[14601]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Oct 31 18:31:32 node-2 puppet-user[14601]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 31 18:31:37 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 31 18:31:37 node-2 kernel: [   94.580567] init: plymouth-upstart-bridge main process ended, respawning
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.791784 #9735] DEBUG -- : Trying to find block devices
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.791891 #9735] DEBUG -- : Found block device: sda
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.791926 #9735] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.791956 #9735] DEBUG -- : Block device seems to be physical data storage: sda
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.791982 #9735] DEBUG -- : Found block device: dm-0
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.791998 #9735] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792010 #9735] DEBUG -- : Found block device: dm-1
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792026 #9735] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792039 #9735] DEBUG -- : Found block device: dm-2
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792070 #9735] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792080 #9735] DEBUG -- : Found block device: dm-3
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792090 #9735] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792100 #9735] DEBUG -- : Found block device: dm-4
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792115 #9735] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792125 #9735] DEBUG -- : Found block device: dm-5
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792137 #9735] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792146 #9735] DEBUG -- : Found block device: ram0
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792156 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792165 #9735] DEBUG -- : Found block device: ram1
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792175 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792205 #9735] DEBUG -- : Found block device: ram2
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792226 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792235 #9735] DEBUG -- : Found block device: ram3
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792244 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792252 #9735] DEBUG -- : Found block device: ram4
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792261 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792269 #9735] DEBUG -- : Found block device: ram5
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792278 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792287 #9735] DEBUG -- : Found block device: ram6
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792298 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792307 #9735] DEBUG -- : Found block device: ram7
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792335 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792343 #9735] DEBUG -- : Found block device: ram8
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792353 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792361 #9735] DEBUG -- : Found block device: ram9
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792371 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792379 #9735] DEBUG -- : Found block device: loop0
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792388 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792397 #9735] DEBUG -- : Found block device: loop1
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792407 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792415 #9735] DEBUG -- : Found block device: loop2
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792442 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792451 #9735] DEBUG -- : Found block device: loop3
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792461 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792469 #9735] DEBUG -- : Found block device: loop4
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792479 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792487 #9735] DEBUG -- : Found block device: loop5
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792496 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792504 #9735] DEBUG -- : Found block device: loop6
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792513 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792522 #9735] DEBUG -- : Found block device: loop7
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792531 #9735] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792556 #9735] DEBUG -- : Found block device: ram10
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792566 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792575 #9735] DEBUG -- : Found block device: ram11
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792585 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792593 #9735] DEBUG -- : Found block device: ram12
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792601 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792610 #9735] DEBUG -- : Found block device: ram13
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792619 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792627 #9735] DEBUG -- : Found block device: ram14
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792636 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792644 #9735] DEBUG -- : Found block device: ram15
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792667 #9735] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.792696 #9735] 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 31 18:31:37 node-2 nailgun-agent: D, [2016-10-31T18:31:37.907729 #9735] DEBUG -- : Response: status: 200 body: {"id": 2}
Oct 31 18:31:37 node-2 nailgun-agent: I, [2016-10-31T18:31:37.907977 #9735]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 31 18:31:38 node-2 puppet-agent[8939]: Could not run: SIGTERM
Oct 31 18:31:38 node-2 kernel: [   94.904681] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 31 18:31:38 node-2 ec2: 
Oct 31 18:31:38 node-2 ec2: #############################################################
Oct 31 18:31:38 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 31 18:31:38 node-2 ec2: 1024 c0:c5:8e:d3:70:44:53:7f:12:60:82:22:7e:3e:d4:03  root@node-2.domain.tld (DSA)
Oct 31 18:31:38 node-2 ec2: 256 86:67:a6:dd:c3:9c:36:41:b1:72:7f:5c:30:0f:1f:9c  root@node-2.domain.tld (ECDSA)
Oct 31 18:31:38 node-2 ec2: 256 26:de:58:c6:3b:ef:f5:9a:c1:90:4c:8e:74:b4:0c:ff  root@node-2.domain.tld (ED25519)
Oct 31 18:31:38 node-2 ec2: 2048 71:ef:02:b7:22:eb:01:33:ce:80:49:12:55:c4:3b:0e  root@node-2.domain.tld (RSA)
Oct 31 18:31:38 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 31 18:31:38 node-2 ec2: #############################################################
Oct 31 18:31:59 node-2 puppet-user[14601]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 31 18:31:59 node-2 puppet-user[14601]: Finished catalog run in 29.67 seconds
Oct 31 18:32:01 node-2 puppet-user[17325]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 31 18:32:01 node-2 puppet-user[17325]: Compiled catalog for node-2.domain.tld in environment production in 0.66 seconds
Oct 31 18:32:01 node-2 CRON[17760]: (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 31 18:32:01 node-2 puppet-user[17325]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 31 18:32:01 node-2 puppet-user[17325]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 31 18:32:01 node-2 puppet-user[17325]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 31 18:32:01 node-2 puppet-user[17325]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 31 18:32:01 node-2 puppet-user[17325]: Finished catalog run in 0.08 seconds
Oct 31 18:32:03 node-2 puppet-user[17803]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 31 18:32:04 node-2 puppet-user[17803]: Compiled catalog for node-2.domain.tld in environment production in 1.00 seconds
Oct 31 18:32:05 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 31 18:32:05 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 31 18:32:05 node-2 crontab[18258]: (root) LIST (root)
Oct 31 18:32:05 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 31 18:32:05 node-2 crontab[18259]: (root) REPLACE (root)
Oct 31 18:32:06 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 31 18:32:07 node-2 puppet-user[17803]: (/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 31 18:32:08 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 31 18:32:08 node-2 puppet-user[17803]: (/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 31 18:32:08 node-2 puppet-user[17803]: (/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 31 18:32:08 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 31 18:32:08 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 31 18:32:08 node-2 puppet-user[17803]: (/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 31 18:32:08 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 31 18:32:08 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 31 18:32:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:26 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:26 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:26 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:26 node-2 multipathd: uevent trigger error
<27>Oct 31 18:32:27 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:21 node-2 ntpdate[28497]: no servers can be used, exiting
<27>Oct 31 18:33:21 node-2 ntpdate[28671]: no servers can be used, exiting
<27>Oct 31 18:33:52 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:52 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:52 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:52 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:52 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:52 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:52 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:33:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:14 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 31 18:35:14 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 31 18:35:20 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 31 18:35:20 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 31 18:35:26 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 31 18:35:31 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 31 18:35:31 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 31 18:35:38 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:38 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:38 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:39 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:39 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:48 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:48 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:48 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:48 node-2 multipathd: uevent trigger error
<27>Oct 31 18:35:48 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:00 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:00 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:00 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:00 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:00 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:06 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:08 node-2 haproxy[17957]: 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 31 18:36:09 node-2 haproxy[17961]: 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 31 18:36:09 node-2 haproxy[17961]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:09 node-2 haproxy[17961]: proxy mysqld has no server available!
<27>Oct 31 18:36:11 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:11 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:11 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:15 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:15 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:15 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:15 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:15 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:15 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:17 node-2 haproxy[20492]: 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 31 18:36:17 node-2 haproxy[20492]: 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 31 18:36:18 node-2 haproxy[20501]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:18 node-2 haproxy[20501]: proxy mysqld has no server available!
<129>Oct 31 18:36:18 node-2 haproxy[20501]: 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 31 18:36:18 node-2 haproxy[20501]: 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 31 18:36:18 node-2 haproxy[20501]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:18 node-2 haproxy[20501]: proxy object-storage has no server available!
<27>Oct 31 18:36:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:20 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:22 node-2 haproxy[21747]: 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 31 18:36:22 node-2 haproxy[21747]: 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 31 18:36:23 node-2 haproxy[21751]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:23 node-2 haproxy[21751]: proxy neutron has no server available!
<129>Oct 31 18:36:23 node-2 haproxy[21751]: 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 31 18:36:23 node-2 haproxy[21751]: 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 31 18:36:23 node-2 haproxy[21751]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:23 node-2 haproxy[21751]: proxy mysqld has no server available!
<129>Oct 31 18:36:23 node-2 haproxy[21751]: 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 31 18:36:23 node-2 haproxy[21751]: 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 31 18:36:24 node-2 haproxy[21751]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:24 node-2 haproxy[21751]: proxy object-storage has no server available!
<27>Oct 31 18:36:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:25 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:28 node-2 haproxy[23208]: 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 31 18:36:28 node-2 haproxy[23208]: 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 31 18:36:28 node-2 haproxy[23208]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:28 node-2 haproxy[23208]: proxy keystone-1 has no server available!
<129>Oct 31 18:36:28 node-2 haproxy[23208]: 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 31 18:36:28 node-2 haproxy[23208]: 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 31 18:36:28 node-2 haproxy[23208]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:28 node-2 haproxy[23208]: proxy keystone-2 has no server available!
<129>Oct 31 18:36:28 node-2 haproxy[23208]: 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 31 18:36:28 node-2 haproxy[23208]: 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 31 18:36:28 node-2 haproxy[23208]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:28 node-2 haproxy[23208]: proxy neutron has no server available!
<129>Oct 31 18:36:29 node-2 haproxy[23212]: 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 31 18:36:29 node-2 haproxy[23212]: 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 31 18:36:29 node-2 haproxy[23212]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:29 node-2 haproxy[23212]: proxy mysqld has no server available!
<129>Oct 31 18:36:29 node-2 haproxy[23212]: 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 31 18:36:29 node-2 haproxy[23212]: 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 31 18:36:29 node-2 haproxy[23212]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:29 node-2 haproxy[23212]: proxy object-storage has no server available!
<27>Oct 31 18:36:30 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:30 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:30 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:30 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:30 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:30 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:33 node-2 haproxy[24440]: 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 31 18:36:33 node-2 haproxy[24440]: 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 31 18:36:33 node-2 haproxy[24440]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:33 node-2 haproxy[24440]: proxy keystone-1 has no server available!
<129>Oct 31 18:36:33 node-2 haproxy[24440]: 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 31 18:36:33 node-2 haproxy[24440]: 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 31 18:36:33 node-2 haproxy[24440]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:33 node-2 haproxy[24440]: proxy keystone-2 has no server available!
<129>Oct 31 18:36:33 node-2 haproxy[24440]: 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 31 18:36:33 node-2 haproxy[24440]: 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 31 18:36:33 node-2 haproxy[24440]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:33 node-2 haproxy[24440]: proxy neutron has no server available!
<129>Oct 31 18:36:34 node-2 haproxy[24445]: 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 31 18:36:34 node-2 haproxy[24445]: 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 31 18:36:34 node-2 haproxy[24445]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:34 node-2 haproxy[24445]: proxy mysqld has no server available!
<129>Oct 31 18:36:34 node-2 haproxy[24445]: 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 31 18:36:34 node-2 haproxy[24445]: 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 31 18:36:34 node-2 haproxy[24445]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:34 node-2 haproxy[24445]: proxy object-storage has no server available!
<129>Oct 31 18:36:34 node-2 haproxy[24445]: 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 31 18:36:34 node-2 haproxy[24445]: 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 31 18:36:34 node-2 haproxy[24445]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:34 node-2 haproxy[24445]: proxy aodh has no server available!
<27>Oct 31 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:36 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:38 node-2 haproxy[25687]: 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 31 18:36:38 node-2 haproxy[25687]: 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 31 18:36:38 node-2 haproxy[25687]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:38 node-2 haproxy[25687]: proxy keystone-1 has no server available!
<129>Oct 31 18:36:38 node-2 haproxy[25687]: 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 31 18:36:38 node-2 haproxy[25687]: 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 31 18:36:38 node-2 haproxy[25687]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:38 node-2 haproxy[25687]: proxy keystone-2 has no server available!
<129>Oct 31 18:36:38 node-2 haproxy[25687]: 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 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:39 node-2 haproxy[25691]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:39 node-2 haproxy[25691]: proxy neutron has no server available!
<129>Oct 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:39 node-2 haproxy[25691]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:39 node-2 haproxy[25691]: proxy mysqld has no server available!
<129>Oct 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:39 node-2 haproxy[25691]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:39 node-2 haproxy[25691]: proxy object-storage has no server available!
<129>Oct 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:39 node-2 haproxy[25691]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:39 node-2 haproxy[25691]: proxy aodh has no server available!
<129>Oct 31 18:36:39 node-2 haproxy[25691]: 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 31 18:36:40 node-2 haproxy[25691]: 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 31 18:36:40 node-2 haproxy[25691]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:40 node-2 haproxy[25691]: proxy ceilometer has no server available!
<27>Oct 31 18:36:41 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:41 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:41 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:41 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:41 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:43 node-2 haproxy[26933]: 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 31 18:36:43 node-2 haproxy[26933]: 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 31 18:36:43 node-2 haproxy[26933]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:43 node-2 haproxy[26933]: proxy keystone-1 has no server available!
<129>Oct 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:44 node-2 haproxy[26937]: proxy keystone-2 has no server available!
<129>Oct 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:44 node-2 haproxy[26937]: proxy neutron has no server available!
<129>Oct 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:44 node-2 haproxy[26937]: proxy mysqld has no server available!
<129>Oct 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: 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 31 18:36:44 node-2 haproxy[26937]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:44 node-2 haproxy[26937]: proxy object-storage has no server available!
<129>Oct 31 18:36:45 node-2 haproxy[26937]: 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 31 18:36:45 node-2 haproxy[26937]: 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 31 18:36:45 node-2 haproxy[26937]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:45 node-2 haproxy[26937]: proxy aodh has no server available!
<129>Oct 31 18:36:45 node-2 haproxy[26937]: 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 31 18:36:45 node-2 haproxy[26937]: 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 31 18:36:45 node-2 haproxy[26937]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:45 node-2 haproxy[26937]: proxy ceilometer has no server available!
<27>Oct 31 18:36:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:46 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:49 node-2 haproxy[28180]: 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 31 18:36:49 node-2 haproxy[28180]: 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 31 18:36:49 node-2 haproxy[28180]: 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 31 18:36:49 node-2 haproxy[28180]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:49 node-2 haproxy[28180]: proxy keystone-1 has no server available!
<129>Oct 31 18:36:49 node-2 haproxy[28180]: 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 31 18:36:49 node-2 haproxy[28180]: 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 31 18:36:49 node-2 haproxy[28180]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:49 node-2 haproxy[28180]: proxy keystone-2 has no server available!
<129>Oct 31 18:36:49 node-2 haproxy[28180]: 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 31 18:36:49 node-2 haproxy[28180]: 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 31 18:36:50 node-2 haproxy[28184]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:50 node-2 haproxy[28184]: proxy neutron has no server available!
<129>Oct 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:50 node-2 haproxy[28184]: proxy mysqld has no server available!
<129>Oct 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:50 node-2 haproxy[28184]: proxy object-storage has no server available!
<129>Oct 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:50 node-2 haproxy[28184]: proxy aodh has no server available!
<129>Oct 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: 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 31 18:36:50 node-2 haproxy[28184]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:50 node-2 haproxy[28184]: proxy ceilometer has no server available!
<27>Oct 31 18:36:51 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:51 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:51 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:51 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:52 node-2 multipathd: uevent trigger error
<129>Oct 31 18:36:54 node-2 haproxy[29478]: 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 31 18:36:54 node-2 haproxy[29478]: 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 31 18:36:54 node-2 haproxy[29478]: 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 31 18:36:54 node-2 haproxy[29478]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:54 node-2 haproxy[29478]: proxy keystone-1 has no server available!
<129>Oct 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:55 node-2 haproxy[29482]: proxy keystone-2 has no server available!
<129>Oct 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:55 node-2 haproxy[29482]: proxy glance-api has no server available!
<129>Oct 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:55 node-2 haproxy[29482]: proxy glance-glare has no server available!
<129>Oct 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:55 node-2 haproxy[29482]: proxy neutron has no server available!
<129>Oct 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:55 node-2 haproxy[29482]: proxy glance-registry has no server available!
<129>Oct 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:55 node-2 haproxy[29482]: 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 31 18:36:56 node-2 haproxy[29482]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:56 node-2 haproxy[29482]: proxy mysqld has no server available!
<129>Oct 31 18:36:56 node-2 haproxy[29482]: 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 31 18:36:56 node-2 haproxy[29482]: 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 31 18:36:56 node-2 haproxy[29482]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:56 node-2 haproxy[29482]: proxy object-storage has no server available!
<129>Oct 31 18:36:56 node-2 haproxy[29482]: 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 31 18:36:56 node-2 haproxy[29482]: 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 31 18:36:56 node-2 haproxy[29482]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:56 node-2 haproxy[29482]: proxy aodh has no server available!
<129>Oct 31 18:36:56 node-2 haproxy[29482]: 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 31 18:36:56 node-2 haproxy[29482]: 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 31 18:36:56 node-2 haproxy[29482]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:36:56 node-2 haproxy[29482]: proxy ceilometer has no server available!
<27>Oct 31 18:36:57 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:57 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:57 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:57 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:57 node-2 multipathd: uevent trigger error
<27>Oct 31 18:36:57 node-2 multipathd: uevent trigger error
<129>Oct 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:00 node-2 haproxy[30734]: proxy keystone-1 has no server available!
<129>Oct 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:00 node-2 haproxy[30734]: proxy keystone-2 has no server available!
<129>Oct 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:00 node-2 haproxy[30734]: proxy nova-api has no server available!
<129>Oct 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:00 node-2 haproxy[30734]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:00 node-2 haproxy[30734]: proxy nova-metadata-api has no server available!
<129>Oct 31 18:37:00 node-2 haproxy[30734]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:01 node-2 haproxy[30738]: proxy glance-api has no server available!
<129>Oct 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:01 node-2 haproxy[30738]: proxy glance-glare has no server available!
<129>Oct 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:01 node-2 haproxy[30738]: proxy neutron has no server available!
<129>Oct 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:01 node-2 haproxy[30738]: proxy glance-registry has no server available!
<129>Oct 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:01 node-2 haproxy[30738]: proxy mysqld has no server available!
<129>Oct 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:01 node-2 haproxy[30738]: proxy object-storage has no server available!
<129>Oct 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:01 node-2 haproxy[30738]: proxy aodh has no server available!
<129>Oct 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:01 node-2 haproxy[30738]: 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 31 18:37:02 node-2 haproxy[30738]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:02 node-2 haproxy[30738]: proxy ceilometer has no server available!
<129>Oct 31 18:37:02 node-2 haproxy[30738]: 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 31 18:37:02 node-2 haproxy[30738]: 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 31 18:37:02 node-2 haproxy[30738]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:02 node-2 haproxy[30738]: proxy nova-novncproxy has no server available!
<27>Oct 31 18:37:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:03 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:03 node-2 multipathd: uevent trigger error
<129>Oct 31 18:37:05 node-2 haproxy[31981]: 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 31 18:37:05 node-2 haproxy[31981]: 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 31 18:37:05 node-2 haproxy[31981]: 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 31 18:37:05 node-2 haproxy[31981]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:05 node-2 haproxy[31981]: proxy keystone-1 has no server available!
<129>Oct 31 18:37:05 node-2 haproxy[31981]: 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 31 18:37:05 node-2 haproxy[31981]: 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 31 18:37:05 node-2 haproxy[31981]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:05 node-2 haproxy[31981]: proxy keystone-2 has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy nova-api has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy nova-metadata-api has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy cinder-api has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy glance-api has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy glance-glare has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy neutron has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy glance-registry has no server available!
<129>Oct 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: 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 31 18:37:06 node-2 haproxy[31985]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:06 node-2 haproxy[31985]: proxy mysqld has no server available!
<129>Oct 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:07 node-2 haproxy[31985]: proxy object-storage has no server available!
<129>Oct 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:07 node-2 haproxy[31985]: proxy aodh has no server available!
<129>Oct 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:07 node-2 haproxy[31985]: proxy ceilometer has no server available!
<129>Oct 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: 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 31 18:37:07 node-2 haproxy[31985]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:07 node-2 haproxy[31985]: proxy nova-novncproxy has no server available!
<27>Oct 31 18:37:08 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:08 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:08 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:08 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:08 node-2 multipathd: uevent trigger error
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:11 node-2 haproxy[986]: proxy keystone-1 has no server available!
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:11 node-2 haproxy[986]: proxy keystone-2 has no server available!
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:11 node-2 haproxy[986]: proxy nova-api has no server available!
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:11 node-2 haproxy[986]: proxy nova-metadata-api has no server available!
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:11 node-2 haproxy[986]: proxy cinder-api has no server available!
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:11 node-2 haproxy[986]: proxy glance-api has no server available!
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:11 node-2 haproxy[986]: proxy glance-glare has no server available!
<129>Oct 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:11 node-2 haproxy[986]: 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 31 18:37:12 node-2 haproxy[992]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy neutron has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy glance-registry has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy mysqld has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy object-storage has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy aodh has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy ceilometer has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy heat-api has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy heat-api-cfn has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy heat-api-cloudwatch has no server available!
<129>Oct 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: 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 31 18:37:12 node-2 haproxy[992]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 31 18:37:12 node-2 haproxy[992]: proxy nova-novncproxy has no server available!
<27>Oct 31 18:37:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:17 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:17 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:17 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:17 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:17 node-2 multipathd: uevent trigger error
<27>Oct 31 18:37:24 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 31 18:37:48 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 31 18:37:50 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 31 18:38:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 31 18:38:23 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 31 18:38:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:38:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:38:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:38:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:38:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:38:46 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:18 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 31 18:41:29 node-2 apache2_error [Mon Oct 31 18:41:24.642028 2016] [mpm_event:notice] [pid 11144:tid 140495510493056] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 31 18:41:29 node-2 apache2_error [Mon Oct 31 18:41:24.642163 2016] [core:notice] [pid 11144:tid 140495510493056] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 31 18:41:29 node-2 apache2_error [Mon Oct 31 18:41:27.509628 2016] [mpm_event:notice] [pid 11144:tid 140495510493056] AH00491: caught SIGTERM, shutting down
<43>Oct 31 18:41:29 node-2 apache2_error [Mon Oct 31 18:41:28.580231 2016] [mpm_worker:notice] [pid 11531:tid 140148772153216] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 31 18:41:29 node-2 apache2_error [Mon Oct 31 18:41:28.580248 2016] [core:notice] [pid 11531:tid 140148772153216] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 31 18:41:32 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:32 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:32 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:32 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:32 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:32 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:41:36 node-2 multipathd: uevent trigger error
<43>Oct 31 18:42:39 node-2 apache2_error [Mon Oct 31 18:42:38.086921 2016] [mpm_worker:notice] [pid 11531:tid 140148772153216] AH00295: caught SIGTERM, shutting down
<43>Oct 31 18:42:39 node-2 apache2_error [Mon Oct 31 18:42:38.844445 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 31 18:42:39 node-2 apache2_error [Mon Oct 31 18:42:38.844489 2016] [core:notice] [pid 23504:tid 140375483176832] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 31 18:43:29 node-2 apache2_error [Mon Oct 31 18:43:22.420063 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 31 18:43:29 node-2 apache2_error [Mon Oct 31 18:43:22.616739 2016] [mpm_worker:warn] [pid 23504:tid 140375483176832] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 31 18:43:29 node-2 apache2_error [Mon Oct 31 18:43:22.619764 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 31 18:43:29 node-2 apache2_error [Mon Oct 31 18:43:22.619781 2016] [core:notice] [pid 23504:tid 140375483176832] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 31 18:44:07 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:07 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:07 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:07 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:07 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:07 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:12 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:21 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 31 18:44:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:50 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:50 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:50 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:50 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:50 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:44:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:09 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:57 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:58 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:58 node-2 multipathd: uevent trigger error
<27>Oct 31 18:45:58 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:04 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:22 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 31 18:47:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:47:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:30 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:30 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:48:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:50:24 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 31 18:50:49 node-2 multipathd: uevent trigger error
<27>Oct 31 18:50:49 node-2 multipathd: uevent trigger error
<27>Oct 31 18:50:49 node-2 multipathd: uevent trigger error
<27>Oct 31 18:50:49 node-2 multipathd: uevent trigger error
<27>Oct 31 18:50:49 node-2 multipathd: uevent trigger error
<27>Oct 31 18:50:49 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:16 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:16 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:16 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:16 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:16 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:40 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:41 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:41 node-2 multipathd: uevent trigger error
<27>Oct 31 18:51:41 node-2 multipathd: uevent trigger error
<27>Oct 31 18:52:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:52:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:52:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:52:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:52:22 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:05 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:25 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 31 18:53:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:53:36 node-2 multipathd: uevent trigger error
<27>Oct 31 18:55:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:55:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:55:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:55:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:55:55 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:07 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:08 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:08 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: uevent trigger error
<27>Oct 31 18:56:20 node-2 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct 31 18:56:27 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 31 18:57:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:24 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:57:28 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:06 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:10 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:14 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:25 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:31 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:58:59 node-2 multipathd: uevent trigger error
<27>Oct 31 18:59:28 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 31 19:00:05 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:05 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:05 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:05 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:05 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:21 node-2 multipathd: uevent trigger error
<11>Oct 31 19:00:33 node-2 liberasurecode[60506]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:33 node-2 liberasurecode[60506]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:33 node-2 liberasurecode[60506]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:33 node-2 liberasurecode[60506]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:33 node-2 liberasurecode[60535]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:33 node-2 liberasurecode[60535]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:33 node-2 liberasurecode[60535]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:33 node-2 liberasurecode[60535]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:35 node-2 liberasurecode[60911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:35 node-2 liberasurecode[60911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:35 node-2 liberasurecode[60911]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:35 node-2 liberasurecode[60911]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:39 node-2 liberasurecode[61507]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:39 node-2 liberasurecode[61507]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:39 node-2 liberasurecode[61507]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:39 node-2 liberasurecode[61507]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61546]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61546]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61546]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61546]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61603]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61603]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61660]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61660]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61660]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61660]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61677]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61677]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61677]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61677]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61691]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61691]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61703]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61703]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61703]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:40 node-2 liberasurecode[61703]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:49 node-2 liberasurecode[63059]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:49 node-2 liberasurecode[63059]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:49 node-2 liberasurecode[63059]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:00:49 node-2 liberasurecode[63059]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 31 19:00:57 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:57 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:57 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:57 node-2 multipathd: uevent trigger error
<27>Oct 31 19:00:57 node-2 multipathd: uevent trigger error
<43>Oct 31 19:01:50 node-2 apache2_error [Mon Oct 31 19:01:43.230452 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 31 19:01:50 node-2 apache2_error [Mon Oct 31 19:01:43.612764 2016] [mpm_worker:warn] [pid 23504:tid 140375483176832] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 31 19:01:50 node-2 apache2_error [Mon Oct 31 19:01:43.616829 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 31 19:01:50 node-2 apache2_error [Mon Oct 31 19:01:43.616851 2016] [core:notice] [pid 23504:tid 140375483176832] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 31 19:02:20 node-2 apache2_error [Mon Oct 31 19:02:20.588016 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Oct 31 19:02:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:30 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 31 19:02:30 node-2 apache2_error [Mon Oct 31 19:02:20.781575 2016] [mpm_worker:warn] [pid 23504:tid 140375483176832] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 31 19:02:30 node-2 apache2_error [Mon Oct 31 19:02:20.786141 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 31 19:02:30 node-2 apache2_error [Mon Oct 31 19:02:20.786163 2016] [core:notice] [pid 23504:tid 140375483176832] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 31 19:02:31 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:31 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:31 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:31 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:31 node-2 multipathd: uevent trigger error
<27>Oct 31 19:02:31 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:09 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:09 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:09 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:09 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:09 node-2 multipathd: uevent trigger error
<43>Oct 31 19:03:10 node-2 apache2_error [Mon Oct 31 19:03:05.380421 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 31 19:03:10 node-2 apache2_error [Mon Oct 31 19:03:05.763428 2016] [mpm_worker:warn] [pid 23504:tid 140375483176832] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 31 19:03:10 node-2 apache2_error [Mon Oct 31 19:03:05.769672 2016] [mpm_worker:notice] [pid 23504:tid 140375483176832] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 31 19:03:10 node-2 apache2_error [Mon Oct 31 19:03:05.769703 2016] [core:notice] [pid 23504:tid 140375483176832] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 31 19:03:15 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:15 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:15 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:15 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:15 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:28 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:28 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:28 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:28 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:28 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:44 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:44 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:44 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:44 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:44 node-2 multipathd: uevent trigger error
<27>Oct 31 19:03:44 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:06 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:12 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 31 19:04:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:25 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:25 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:25 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:25 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:25 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:25 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:35 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:35 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:35 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:35 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:40 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:40 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:40 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:40 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:40 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:04:53 node-2 multipathd: uevent trigger error
<11>Oct 31 19:05:02 node-2 liberasurecode[115572]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:05:02 node-2 liberasurecode[115572]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:05:02 node-2 liberasurecode[115572]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 31 19:05:02 node-2 liberasurecode[115572]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 31 19:05:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:20 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:24 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:24 node-2 multipathd: uevent trigger error
<129>Oct 31 19:05:29 node-2 haproxy[992]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 31 19:05:37 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:37 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:37 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:37 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:37 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:37 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:41 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:41 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:41 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:41 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:41 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:05:53 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:08 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:08 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:08 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:08 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:08 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:08 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:12 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:12 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:12 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:12 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:12 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:12 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:17 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:17 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:17 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:17 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:17 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:17 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:21 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:29 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:29 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:29 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:29 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:29 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:29 node-2 multipathd: uevent trigger error
<129>Oct 31 19:06:30 node-2 haproxy[992]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct 31 19:06:33 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:33 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:34 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:34 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:34 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:38 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:38 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:38 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:38 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:42 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:42 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:42 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:42 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:42 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:42 node-2 multipathd: uevent trigger error
<27>Oct 31 19:06:51 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:06:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:06:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:05 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:07:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:17 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:07:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:29 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:07:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:41 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:07:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:53 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:07:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:07:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:05 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:08:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:17 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 31 19:08:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
<27>Oct 31 19:08:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-4df6e2f3-38" in table Interface
