Nov 13 17:57:23 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8388" x-info="http://www.rsyslog.com"] start
Nov 13 17:57:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov 13 17:57:23 node-2 rsyslogd: rsyslogd's groupid changed to 104
Nov 13 17:57:23 node-2 rsyslogd: rsyslogd's userid changed to 101
Nov 13 17:57:23 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 13 17:57:23 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 13 17:57:23 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov 13 17:57:23 node-2 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Nov 13 17:57:23 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=1a563ffb-a918-4b74-bbbe-68b798d2b427 nomdmonddf nomdmonisw
Nov 13 17:57:23 node-2 kernel: [    0.000000] KERNEL supported cpus:
Nov 13 17:57:23 node-2 kernel: [    0.000000]   Intel GenuineIntel
Nov 13 17:57:23 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Nov 13 17:57:23 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Nov 13 17:57:23 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov 13 17:57:23 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov 13 17:57:23 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Nov 13 17:57:23 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Nov 13 17:57:23 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 13 17:57:23 node-2 kernel: [    0.000000] No AGP bridge found
Nov 13 17:57:23 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov 13 17:57:23 node-2 kernel: [    0.000000] MTRR default type: write-back
Nov 13 17:57:23 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov 13 17:57:23 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Nov 13 17:57:23 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov 13 17:57:23 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov 13 17:57:23 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Nov 13 17:57:23 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov 13 17:57:23 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov 13 17:57:23 node-2 kernel: [    0.000000]   2 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000]   3 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000]   4 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000]   5 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000]   6 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000]   7 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000]   8 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000]   9 disabled
Nov 13 17:57:23 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 13 17:57:23 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov 13 17:57:23 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov 13 17:57:23 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov 13 17:57:23 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov 13 17:57:23 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov 13 17:57:23 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov 13 17:57:23 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov 13 17:57:23 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov 13 17:57:23 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov 13 17:57:23 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov 13 17:57:23 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov 13 17:57:23 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov 13 17:57:23 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov 13 17:57:23 node-2 kernel: [    0.000000] Zone ranges:
Nov 13 17:57:23 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] Movable zone start for each node
Nov 13 17:57:23 node-2 kernel: [    0.000000] Early memory node ranges
Nov 13 17:57:23 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] On node 0 totalpages: 4125855
Nov 13 17:57:23 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov 13 17:57:23 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov 13 17:57:23 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov 13 17:57:23 node-2 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Nov 13 17:57:23 node-2 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Nov 13 17:57:23 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov 13 17:57:23 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov 13 17:57:23 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov 13 17:57:23 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov 13 17:57:23 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov 13 17:57:23 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov 13 17:57:23 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov 13 17:57:23 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov 13 17:57:23 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov 13 17:57:23 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov 13 17:57:23 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov 13 17:57:23 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov 13 17:57:23 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov 13 17:57:23 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov 13 17:57:23 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov 13 17:57:23 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov 13 17:57:23 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov 13 17:57:23 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Nov 13 17:57:23 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Nov 13 17:57:23 node-2 kernel: [    0.000000] Policy zone: Normal
Nov 13 17:57:23 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=1a563ffb-a918-4b74-bbbe-68b798d2b427 nomdmonddf nomdmonisw
Nov 13 17:57:23 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov 13 17:57:23 node-2 kernel: [    0.000000] Checking aperture...
Nov 13 17:57:23 node-2 kernel: [    0.000000] No AGP bridge found
Nov 13 17:57:23 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov 13 17:57:23 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov 13 17:57:23 node-2 kernel: [    0.000000] Memory: 32653460K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627176K reserved)
Nov 13 17:57:23 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov 13 17:57:23 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Nov 13 17:57:23 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov 13 17:57:23 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov 13 17:57:23 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov 13 17:57:23 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov 13 17:57:23 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov 13 17:57:23 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Nov 13 17:57:23 node-2 kernel: [    0.000000] console [tty0] enabled
Nov 13 17:57:23 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov 13 17:57:23 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 13 17:57:23 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov 13 17:57:23 node-2 kernel: [    0.000000] hpet clockevent registered
Nov 13 17:57:23 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov 13 17:57:23 node-2 kernel: [    0.004000] tsc: Detected 3491.963 MHz processor
Nov 13 17:57:23 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.92 BogoMIPS (lpj=13967852)
Nov 13 17:57:23 node-2 kernel: [    0.000017] pid_max: default: 32768 minimum: 301
Nov 13 17:57:23 node-2 kernel: [    0.000052] Security Framework initialized
Nov 13 17:57:23 node-2 kernel: [    0.000070] AppArmor: AppArmor initialized
Nov 13 17:57:23 node-2 kernel: [    0.000071] Yama: becoming mindful.
Nov 13 17:57:23 node-2 kernel: [    0.001473] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.006397] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.008324] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.008351] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.008640] Initializing cgroup subsys memory
Nov 13 17:57:23 node-2 kernel: [    0.008648] Initializing cgroup subsys devices
Nov 13 17:57:23 node-2 kernel: [    0.008650] Initializing cgroup subsys freezer
Nov 13 17:57:23 node-2 kernel: [    0.008652] Initializing cgroup subsys blkio
Nov 13 17:57:23 node-2 kernel: [    0.008653] Initializing cgroup subsys perf_event
Nov 13 17:57:23 node-2 kernel: [    0.008656] Initializing cgroup subsys hugetlb
Nov 13 17:57:23 node-2 kernel: [    0.008675] CPU: Physical Processor ID: 0
Nov 13 17:57:23 node-2 kernel: [    0.008677] CPU: Processor Core ID: 0
Nov 13 17:57:23 node-2 kernel: [    0.008680] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov 13 17:57:23 node-2 kernel: [    0.008680] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov 13 17:57:23 node-2 kernel: [    0.009374] mce: CPU supports 22 MCE banks
Nov 13 17:57:23 node-2 kernel: [    0.009402] CPU0: Thermal monitoring enabled (TM1)
Nov 13 17:57:23 node-2 kernel: [    0.009422] process: using mwait in idle threads
Nov 13 17:57:23 node-2 kernel: [    0.009425] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov 13 17:57:23 node-2 kernel: [    0.009425] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov 13 17:57:23 node-2 kernel: [    0.009425] tlb_flushall_shift: 6
Nov 13 17:57:23 node-2 kernel: [    0.009512] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov 13 17:57:23 node-2 kernel: [    0.010234] ACPI: Core revision 20131115
Nov 13 17:57:23 node-2 kernel: [    0.023047] ACPI: All ACPI Tables successfully acquired
Nov 13 17:57:23 node-2 kernel: [    0.023208] ftrace: allocating 28622 entries in 112 pages
Nov 13 17:57:23 node-2 kernel: [    0.031965] dmar: Host address width 46
Nov 13 17:57:23 node-2 kernel: [    0.031967] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov 13 17:57:23 node-2 kernel: [    0.031973] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 17:57:23 node-2 kernel: [    0.031975] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov 13 17:57:23 node-2 kernel: [    0.031979] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov 13 17:57:23 node-2 kernel: [    0.031981] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov 13 17:57:23 node-2 kernel: [    0.031982] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov 13 17:57:23 node-2 kernel: [    0.031983] dmar: ATSR flags: 0x0
Nov 13 17:57:23 node-2 kernel: [    0.031984] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov 13 17:57:23 node-2 kernel: [    0.031985] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov 13 17:57:23 node-2 kernel: [    0.032101] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov 13 17:57:23 node-2 kernel: [    0.032102] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 17:57:23 node-2 kernel: [    0.032103] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov 13 17:57:23 node-2 kernel: [    0.032104] HPET id 0 under DRHD base 0xc7ffc000
Nov 13 17:57:23 node-2 kernel: [    0.032106] Your BIOS is broken and requested that x2apic be disabled.
Nov 13 17:57:23 node-2 kernel: [    0.032106] This will slightly decrease performance.
Nov 13 17:57:23 node-2 kernel: [    0.032106] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov 13 17:57:23 node-2 kernel: [    0.032537] Enabled IRQ remapping in xapic mode
Nov 13 17:57:23 node-2 kernel: [    0.032539] x2apic not enabled, IRQ remapping is in xapic mode
Nov 13 17:57:23 node-2 kernel: [    0.032542] Switched APIC routing to physical flat.
Nov 13 17:57:23 node-2 kernel: [    0.033132] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 13 17:57:23 node-2 kernel: [    0.072782] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov 13 17:57:23 node-2 kernel: [    0.072788] TSC deadline timer enabled
Nov 13 17:57:23 node-2 kernel: [    0.072795] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov 13 17:57:23 node-2 kernel: [    0.072801] ... version:                3
Nov 13 17:57:23 node-2 kernel: [    0.072802] ... bit width:              48
Nov 13 17:57:23 node-2 kernel: [    0.072803] ... generic registers:      4
Nov 13 17:57:23 node-2 kernel: [    0.072804] ... value mask:             0000ffffffffffff
Nov 13 17:57:23 node-2 kernel: [    0.072805] ... max period:             0000ffffffffffff
Nov 13 17:57:23 node-2 kernel: [    0.072806] ... fixed-purpose events:   3
Nov 13 17:57:23 node-2 kernel: [    0.072807] ... event mask:             000000070000000f
Nov 13 17:57:23 node-2 kernel: [    0.074207] x86: Booting SMP configuration:
Nov 13 17:57:23 node-2 kernel: [    0.088315] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 13 17:57:23 node-2 kernel: [    0.074209] .... node  #0, CPUs:        #1  #2  #3
Nov 13 17:57:23 node-2 kernel: [    0.116224] .... node  #1, CPUs:    #4  #5  #6  #7
Nov 13 17:57:23 node-2 kernel: [    0.270062] .... node  #0, CPUs:    #8  #9 #10 #11
Nov 13 17:57:23 node-2 kernel: [    0.325680] .... node  #1, CPUs:   #12 #13 #14 #15
Nov 13 17:57:23 node-2 kernel: [    0.382527] x86: Booted up 2 nodes, 16 CPUs
Nov 13 17:57:23 node-2 kernel: [    0.382530] smpboot: Total of 16 processors activated (111755.29 BogoMIPS)
Nov 13 17:57:23 node-2 kernel: [    0.407366] devtmpfs: initialized
Nov 13 17:57:23 node-2 kernel: [    0.410072] EVM: security.selinux
Nov 13 17:57:23 node-2 kernel: [    0.410073] EVM: security.SMACK64
Nov 13 17:57:23 node-2 kernel: [    0.410074] EVM: security.ima
Nov 13 17:57:23 node-2 kernel: [    0.410075] EVM: security.capability
Nov 13 17:57:23 node-2 kernel: [    0.410126] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.410762] pinctrl core: initialized pinctrl subsystem
Nov 13 17:57:23 node-2 kernel: [    0.410823] regulator-dummy: no parameters
Nov 13 17:57:23 node-2 kernel: [    0.410867] RTC time: 17:56:47, date: 11/13/16
Nov 13 17:57:23 node-2 kernel: [    0.410900] NET: Registered protocol family 16
Nov 13 17:57:23 node-2 kernel: [    0.410985] cpuidle: using governor ladder
Nov 13 17:57:23 node-2 kernel: [    0.410986] cpuidle: using governor menu
Nov 13 17:57:23 node-2 kernel: [    0.411020] ACPI: bus type PCI registered
Nov 13 17:57:23 node-2 kernel: [    0.411022] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 13 17:57:23 node-2 kernel: [    0.411066] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov 13 17:57:23 node-2 kernel: [    0.411069] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov 13 17:57:23 node-2 kernel: [    0.424805] PCI: Using configuration type 1 for base access
Nov 13 17:57:23 node-2 kernel: [    0.425800] bio: create slab <bio-0> at 0
Nov 13 17:57:23 node-2 kernel: [    0.426073] ACPI: Added _OSI(Module Device)
Nov 13 17:57:23 node-2 kernel: [    0.426074] ACPI: Added _OSI(Processor Device)
Nov 13 17:57:23 node-2 kernel: [    0.426075] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 13 17:57:23 node-2 kernel: [    0.426076] ACPI: Added _OSI(Processor Aggregator Device)
Nov 13 17:57:23 node-2 kernel: [    0.438736] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov 13 17:57:23 node-2 kernel: [    0.450339] ACPI: Interpreter enabled
Nov 13 17:57:23 node-2 kernel: [    0.450345] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov 13 17:57:23 node-2 kernel: [    0.450349] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov 13 17:57:23 node-2 kernel: [    0.450352] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov 13 17:57:23 node-2 kernel: [    0.450359] ACPI: (supports S0 S4 S5)
Nov 13 17:57:23 node-2 kernel: [    0.450360] ACPI: Using IOAPIC for interrupt routing
Nov 13 17:57:23 node-2 kernel: [    0.450402] HEST: Table parsing has been initialized.
Nov 13 17:57:23 node-2 kernel: [    0.450405] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 13 17:57:23 node-2 kernel: [    0.450959] ACPI: No dock devices found.
Nov 13 17:57:23 node-2 kernel: [    0.462496] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov 13 17:57:23 node-2 kernel: [    0.462501] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 17:57:23 node-2 kernel: [    0.462505] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 17:57:23 node-2 kernel: [    0.462533] PCI host bridge to bus 0000:ff
Nov 13 17:57:23 node-2 kernel: [    0.462535] pci_bus 0000:ff: root bus resource [bus ff]
Nov 13 17:57:23 node-2 kernel: [    0.462543] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462581] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.462611] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462646] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462676] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.462705] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.462736] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462765] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462795] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462823] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462849] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462875] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462904] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462930] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462956] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.462982] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463011] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463038] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463064] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.463092] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463117] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.463142] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463168] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463197] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.463231] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463261] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463290] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463320] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463351] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463381] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463411] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463440] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463470] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463502] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463535] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463567] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463601] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463631] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463658] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463692] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463724] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463761] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463796] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463829] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463860] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463888] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463918] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463946] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.463976] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464005] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464036] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464066] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464093] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464122] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464152] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464183] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464215] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464272] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov 13 17:57:23 node-2 kernel: [    0.464275] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 17:57:23 node-2 kernel: [    0.464278] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov 13 17:57:23 node-2 kernel: [    0.464296] PCI host bridge to bus 0000:7f
Nov 13 17:57:23 node-2 kernel: [    0.464298] pci_bus 0000:7f: root bus resource [bus 7f]
Nov 13 17:57:23 node-2 kernel: [    0.464303] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464331] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.464360] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464390] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464411] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.464436] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.464462] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464489] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464514] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464539] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464567] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464592] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464619] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464643] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464671] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464696] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464718] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464741] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464763] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.464787] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464809] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.464831] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464853] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464880] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov 13 17:57:23 node-2 kernel: [    0.464914] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464940] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464966] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.464992] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465017] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465043] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465069] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465097] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465122] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465149] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465175] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465201] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465230] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465256] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465281] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465309] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465334] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465361] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465389] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465415] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465440] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465464] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465490] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465519] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465547] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465573] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465603] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465627] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465649] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465674] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465700] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465727] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.465753] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.467008] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov 13 17:57:23 node-2 kernel: [    0.467011] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 17:57:23 node-2 kernel: [    0.468138] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 17:57:23 node-2 kernel: [    0.468651] PCI host bridge to bus 0000:00
Nov 13 17:57:23 node-2 kernel: [    0.468654] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov 13 17:57:23 node-2 kernel: [    0.468655] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov 13 17:57:23 node-2 kernel: [    0.468657] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov 13 17:57:23 node-2 kernel: [    0.468658] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov 13 17:57:23 node-2 kernel: [    0.468659] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov 13 17:57:23 node-2 kernel: [    0.468661] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 13 17:57:23 node-2 kernel: [    0.468662] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov 13 17:57:23 node-2 kernel: [    0.468668] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov 13 17:57:23 node-2 kernel: [    0.468750] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.468781] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.468822] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov 13 17:57:23 node-2 kernel: [    0.468842] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.468871] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.468911] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov 13 17:57:23 node-2 kernel: [    0.468930] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.468959] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.469002] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov 13 17:57:23 node-2 kernel: [    0.469020] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.469091] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.469166] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.469243] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 17:57:23 node-2 kernel: [    0.469248] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov 13 17:57:23 node-2 kernel: [    0.469333] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov 13 17:57:23 node-2 kernel: [    0.469481] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov 13 17:57:23 node-2 kernel: [    0.469498] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov 13 17:57:23 node-2 kernel: [    0.469575] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.469631] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov 13 17:57:23 node-2 kernel: [    0.469652] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.469708] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.469751] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 13 17:57:23 node-2 kernel: [    0.469779] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.469835] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.469878] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov 13 17:57:23 node-2 kernel: [    0.469902] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov 13 17:57:23 node-2 kernel: [    0.469920] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov 13 17:57:23 node-2 kernel: [    0.469997] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.470047] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 13 17:57:23 node-2 kernel: [    0.470075] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov 13 17:57:23 node-2 kernel: [    0.470323] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov 13 17:57:23 node-2 kernel: [    0.470329] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov 13 17:57:23 node-2 kernel: [    0.470335] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.470341] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.470348] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov 13 17:57:23 node-2 kernel: [    0.470378] pci 0000:01:00.0: supports D1 D2
Nov 13 17:57:23 node-2 kernel: [    0.476567] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 17:57:23 node-2 kernel: [    0.476574] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 17:57:23 node-2 kernel: [    0.476578] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 17:57:23 node-2 kernel: [    0.476838] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.476906] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov 13 17:57:23 node-2 kernel: [    0.484564] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 17:57:23 node-2 kernel: [    0.484570] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.484574] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 17:57:23 node-2 kernel: [    0.484658] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.484731] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.484825] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.484908] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 17:57:23 node-2 kernel: [    0.484915] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.484920] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 17:57:23 node-2 kernel: [    0.484991] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.485132] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.485186] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 17:57:23 node-2 kernel: [    0.485188] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.485190] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.485239] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.485363] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.485405] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.485523] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.485562] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.485682] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.485717] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov 13 17:57:23 node-2 kernel: [    0.485836] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov 13 17:57:23 node-2 kernel: [    0.485877] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 17:57:23 node-2 kernel: [    0.485880] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.485882] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.485940] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov 13 17:57:23 node-2 kernel: [    0.486002] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.486054] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.486121] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov 13 17:57:23 node-2 kernel: [    0.486201] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov 13 17:57:23 node-2 kernel: [    0.486311] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 17:57:23 node-2 kernel: [    0.486314] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.486316] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.486371] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov 13 17:57:23 node-2 kernel: [    0.486426] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.486474] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.486687] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 17:57:23 node-2 kernel: [    0.486690] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 17:57:23 node-2 kernel: [    0.486754] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov 13 17:57:23 node-2 kernel: [    0.486806] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.486855] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.487064] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 17:57:23 node-2 kernel: [    0.487067] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 17:57:23 node-2 kernel: [    0.487140] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov 13 17:57:23 node-2 kernel: [    0.487203] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.487255] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov 13 17:57:23 node-2 kernel: [    0.487481] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 17:57:23 node-2 kernel: [    0.487485] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 17:57:23 node-2 kernel: [    0.487659] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 17:57:23 node-2 kernel: [    0.487697] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 17:57:23 node-2 kernel: [    0.487772] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov 13 17:57:23 node-2 kernel: [    0.487791] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov 13 17:57:23 node-2 kernel: [    0.487805] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov 13 17:57:23 node-2 kernel: [    0.487818] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov 13 17:57:23 node-2 kernel: [    0.487868] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov 13 17:57:23 node-2 kernel: [    0.492570] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 17:57:23 node-2 kernel: [    0.492579] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 17:57:23 node-2 kernel: [    0.492626] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov 13 17:57:23 node-2 kernel: [    0.493114] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov 13 17:57:23 node-2 kernel: [    0.493117] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov 13 17:57:23 node-2 kernel: [    0.493242] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov 13 17:57:23 node-2 kernel: [    0.493349] PCI host bridge to bus 0000:80
Nov 13 17:57:23 node-2 kernel: [    0.493351] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov 13 17:57:23 node-2 kernel: [    0.493353] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov 13 17:57:23 node-2 kernel: [    0.493354] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov 13 17:57:23 node-2 kernel: [    0.493362] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.493426] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.493497] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov 13 17:57:23 node-2 kernel: [    0.493559] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov 13 17:57:23 node-2 kernel: [    0.493564] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov 13 17:57:23 node-2 kernel: [    0.493636] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov 13 17:57:23 node-2 kernel: [    0.493936] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 13 17:57:23 node-2 kernel: [    0.493967] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 13 17:57:23 node-2 kernel: [    0.493996] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov 13 17:57:23 node-2 kernel: [    0.494025] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov 13 17:57:23 node-2 kernel: [    0.494055] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 17:57:23 node-2 kernel: [    0.494084] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 17:57:23 node-2 kernel: [    0.494114] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 17:57:23 node-2 kernel: [    0.494144] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 13 17:57:23 node-2 kernel: [    0.494229] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov 13 17:57:23 node-2 kernel: [    0.494233] ACPI: \_SB_.UNC1: notify handler is installed
Nov 13 17:57:23 node-2 kernel: [    0.494234] ACPI: \_SB_.UNC0: notify handler is installed
Nov 13 17:57:23 node-2 kernel: [    0.494249] ACPI: \_SB_.PCI0: notify handler is installed
Nov 13 17:57:23 node-2 kernel: [    0.494302] ACPI: \_SB_.PCI1: notify handler is installed
Nov 13 17:57:23 node-2 kernel: [    0.494381] Found 4 acpi root devices
Nov 13 17:57:23 node-2 kernel: [    0.494491] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov 13 17:57:23 node-2 kernel: [    0.494493] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov 13 17:57:23 node-2 kernel: [    0.494495] vgaarb: loaded
Nov 13 17:57:23 node-2 kernel: [    0.494496] vgaarb: bridge control possible 0000:0c:00.0
Nov 13 17:57:23 node-2 kernel: [    0.494614] SCSI subsystem initialized
Nov 13 17:57:23 node-2 kernel: [    0.494678] libata version 3.00 loaded.
Nov 13 17:57:23 node-2 kernel: [    0.494692] ACPI: bus type USB registered
Nov 13 17:57:23 node-2 kernel: [    0.494702] usbcore: registered new interface driver usbfs
Nov 13 17:57:23 node-2 kernel: [    0.494706] usbcore: registered new interface driver hub
Nov 13 17:57:23 node-2 kernel: [    0.494730] usbcore: registered new device driver usb
Nov 13 17:57:23 node-2 kernel: [    0.494892] PCI: Using ACPI for IRQ routing
Nov 13 17:57:23 node-2 kernel: [    0.498491] PCI: pci_cache_line_size set to 64 bytes
Nov 13 17:57:23 node-2 kernel: [    0.498695] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov 13 17:57:23 node-2 kernel: [    0.498696] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Nov 13 17:57:23 node-2 kernel: [    0.498697] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov 13 17:57:23 node-2 kernel: [    0.498761] NetLabel: Initializing
Nov 13 17:57:23 node-2 kernel: [    0.498763] NetLabel:  domain hash size = 128
Nov 13 17:57:23 node-2 kernel: [    0.498763] NetLabel:  protocols = UNLABELED CIPSOv4
Nov 13 17:57:23 node-2 kernel: [    0.498773] NetLabel:  unlabeled traffic allowed by default
Nov 13 17:57:23 node-2 kernel: [    0.498830] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov 13 17:57:23 node-2 kernel: [    0.498834] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov 13 17:57:23 node-2 kernel: [    0.500901] Switched to clocksource hpet
Nov 13 17:57:23 node-2 kernel: [    0.505466] AppArmor: AppArmor Filesystem Enabled
Nov 13 17:57:23 node-2 kernel: [    0.505505] pnp: PnP ACPI init
Nov 13 17:57:23 node-2 kernel: [    0.505516] ACPI: bus type PNP registered
Nov 13 17:57:23 node-2 kernel: [    0.505696] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov 13 17:57:23 node-2 kernel: [    0.505707] pnp 00:01: [dma 4]
Nov 13 17:57:23 node-2 kernel: [    0.505726] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 13 17:57:23 node-2 kernel: [    0.505760] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 13 17:57:23 node-2 kernel: [    0.505785] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 13 17:57:23 node-2 kernel: [    0.505806] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 13 17:57:23 node-2 kernel: [    0.505854] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov 13 17:57:23 node-2 kernel: [    0.505966] system 00:06: [io  0x0500-0x057f] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505969] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov 13 17:57:23 node-2 kernel: [    0.505970] system 00:06: [io  0x0580-0x059f] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505972] system 00:06: [io  0x0600-0x061f] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505973] system 00:06: [io  0x0880-0x0883] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505975] system 00:06: [io  0x0800-0x081f] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505978] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov 13 17:57:23 node-2 kernel: [    0.505980] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505981] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505983] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505984] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505986] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505987] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov 13 17:57:23 node-2 kernel: [    0.505990] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 13 17:57:23 node-2 kernel: [    0.506090] pnp 00:07: [dma 0 disabled]
Nov 13 17:57:23 node-2 kernel: [    0.506123] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 17:57:23 node-2 kernel: [    0.506203] pnp 00:08: [dma 0 disabled]
Nov 13 17:57:23 node-2 kernel: [    0.506239] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov 13 17:57:23 node-2 kernel: [    0.506297] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov 13 17:57:23 node-2 kernel: [    0.506740] pnp: PnP ACPI: found 10 devices
Nov 13 17:57:23 node-2 kernel: [    0.506742] ACPI: bus type PNP unregistered
Nov 13 17:57:23 node-2 kernel: [    0.512716] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov 13 17:57:23 node-2 kernel: [    0.512720] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov 13 17:57:23 node-2 kernel: [    0.512723] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov 13 17:57:23 node-2 kernel: [    0.512728] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov 13 17:57:23 node-2 kernel: [    0.512730] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.512744] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.512774] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov 13 17:57:23 node-2 kernel: [    0.512788] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov 13 17:57:23 node-2 kernel: [    0.512817] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov 13 17:57:23 node-2 kernel: [    0.512832] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov 13 17:57:23 node-2 kernel: [    0.512860] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov 13 17:57:23 node-2 kernel: [    0.512879] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov 13 17:57:23 node-2 kernel: [    0.512912] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov 13 17:57:23 node-2 kernel: [    0.512914] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.512928] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.512958] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov 13 17:57:23 node-2 kernel: [    0.512960] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.512974] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513003] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov 13 17:57:23 node-2 kernel: [    0.513005] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.513008] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513013] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov 13 17:57:23 node-2 kernel: [    0.513015] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.513017] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513022] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov 13 17:57:23 node-2 kernel: [    0.513028] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov 13 17:57:23 node-2 kernel: [    0.513037] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov 13 17:57:23 node-2 kernel: [    0.513040] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov 13 17:57:23 node-2 kernel: [    0.513047] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov 13 17:57:23 node-2 kernel: [    0.513048] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov 13 17:57:23 node-2 kernel: [    0.513049] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov 13 17:57:23 node-2 kernel: [    0.513050] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov 13 17:57:23 node-2 kernel: [    0.513051] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov 13 17:57:23 node-2 kernel: [    0.513052] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov 13 17:57:23 node-2 kernel: [    0.513053] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov 13 17:57:23 node-2 kernel: [    0.513054] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov 13 17:57:23 node-2 kernel: [    0.513055] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.513056] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513057] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.513058] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513059] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.513060] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513061] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.513061] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513063] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov 13 17:57:23 node-2 kernel: [    0.513063] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513065] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov 13 17:57:23 node-2 kernel: [    0.513066] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov 13 17:57:23 node-2 kernel: [    0.513067] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov 13 17:57:23 node-2 kernel: [    0.513069] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov 13 17:57:23 node-2 kernel: [    0.513071] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov 13 17:57:23 node-2 kernel: [    0.513072] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov 13 17:57:23 node-2 kernel: [    0.513113] NET: Registered protocol family 2
Nov 13 17:57:23 node-2 kernel: [    0.513408] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.513787] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.513955] TCP: Hash tables configured (established 262144 bind 65536)
Nov 13 17:57:23 node-2 kernel: [    0.513997] TCP: reno registered
Nov 13 17:57:23 node-2 kernel: [    0.514029] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.514137] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.514317] NET: Registered protocol family 1
Nov 13 17:57:23 node-2 kernel: [    0.552989] pci 0000:0c:00.0: Video device with shadowed ROM
Nov 13 17:57:23 node-2 kernel: [    0.553004] PCI: CLS 64 bytes, default 64
Nov 13 17:57:23 node-2 kernel: [    0.553069] Trying to unpack rootfs image as initramfs...
Nov 13 17:57:23 node-2 kernel: [    0.775065] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Nov 13 17:57:23 node-2 kernel: [    0.775096] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov 13 17:57:23 node-2 kernel: [    0.775099] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Nov 13 17:57:23 node-2 kernel: [    0.775533] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775541] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775548] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775555] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775564] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775571] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775578] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775583] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775589] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775595] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775605] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775612] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775618] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775624] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775630] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775636] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov 13 17:57:23 node-2 kernel: [    0.775683] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 13 17:57:23 node-2 kernel: [    0.775685] Scanning for low memory corruption every 60 seconds
Nov 13 17:57:23 node-2 kernel: [    0.775979] Initialise system trusted keyring
Nov 13 17:57:23 node-2 kernel: [    0.776026] audit: initializing netlink socket (disabled)
Nov 13 17:57:23 node-2 kernel: [    0.776037] type=2000 audit(1479059807.720:1): initialized
Nov 13 17:57:23 node-2 kernel: [    0.793790] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 13 17:57:23 node-2 kernel: [    0.795262] zbud: loaded
Nov 13 17:57:23 node-2 kernel: [    0.795392] VFS: Disk quotas dquot_6.5.2
Nov 13 17:57:23 node-2 kernel: [    0.795429] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov 13 17:57:23 node-2 kernel: [    0.795778] fuse init (API version 7.22)
Nov 13 17:57:23 node-2 kernel: [    0.795828] msgmni has been set to 32768
Nov 13 17:57:23 node-2 kernel: [    0.795873] Key type big_key registered
Nov 13 17:57:23 node-2 kernel: [    0.796422] Key type asymmetric registered
Nov 13 17:57:23 node-2 kernel: [    0.796424] Asymmetric key parser 'x509' registered
Nov 13 17:57:23 node-2 kernel: [    0.796446] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 13 17:57:23 node-2 kernel: [    0.796512] io scheduler noop registered
Nov 13 17:57:23 node-2 kernel: [    0.796514] io scheduler deadline registered (default)
Nov 13 17:57:23 node-2 kernel: [    0.796532] io scheduler cfq registered
Nov 13 17:57:23 node-2 kernel: [    0.797052] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    0.797201] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    0.797315] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    0.797440] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    0.797554] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    0.797680] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    0.798048] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov 13 17:57:23 node-2 kernel: [    0.798074] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov 13 17:57:23 node-2 kernel: [    0.798090] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov 13 17:57:23 node-2 kernel: [    0.798103] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798105] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798108] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov 13 17:57:23 node-2 kernel: [    0.798113] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798114] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798116] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798117] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798119] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798120] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798122] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798123] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798124] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798126] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798127] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798128] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798131] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov 13 17:57:23 node-2 kernel: [    0.798144] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798146] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov 13 17:57:23 node-2 kernel: [    0.798157] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798160] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov 13 17:57:23 node-2 kernel: [    0.798171] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798173] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov 13 17:57:23 node-2 kernel: [    0.798176] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov 13 17:57:23 node-2 kernel: [    0.798202] ioapic: probe of 0000:00:05.4 failed with error -22
Nov 13 17:57:23 node-2 kernel: [    0.798208] ioapic: probe of 0000:80:05.4 failed with error -22
Nov 13 17:57:23 node-2 kernel: [    0.798211] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 13 17:57:23 node-2 kernel: [    0.798227] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 13 17:57:23 node-2 kernel: [    0.798264] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov 13 17:57:23 node-2 kernel: [    0.798265] vesafb: scrolling: redraw
Nov 13 17:57:23 node-2 kernel: [    0.798267] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov 13 17:57:23 node-2 kernel: [    0.818725] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov 13 17:57:23 node-2 kernel: [    0.827314] Console: switching to colour frame buffer device 80x30
Nov 13 17:57:23 node-2 kernel: [    0.835975] fb0: VESA VGA frame buffer device
Nov 13 17:57:23 node-2 kernel: [    0.836173] intel_idle: MWAIT substates: 0x2120
Nov 13 17:57:23 node-2 kernel: [    0.836174] intel_idle: v0.4 model 0x3F
Nov 13 17:57:23 node-2 kernel: [    0.836174] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov 13 17:57:23 node-2 kernel: [    0.836408] ipmi message handler version 39.2
Nov 13 17:57:23 node-2 kernel: [    0.836689] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov 13 17:57:23 node-2 kernel: [    0.837125] ACPI: AC Adapter [P111] (on-line)
Nov 13 17:57:23 node-2 kernel: [    0.842356] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov 13 17:57:23 node-2 kernel: [    0.853374] ACPI: Power Button [PWRB]
Nov 13 17:57:23 node-2 kernel: [    0.859130] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov 13 17:57:23 node-2 kernel: [    0.870753] ACPI: Power Button [PWRF]
Nov 13 17:57:23 node-2 kernel: [    0.886435] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov 13 17:57:23 node-2 kernel: [    0.898175] pstore: Registered erst as persistent store backend
Nov 13 17:57:23 node-2 kernel: [    0.904385] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov 13 17:57:23 node-2 kernel: [    0.916348] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 13 17:57:23 node-2 kernel: [    0.943111] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov 13 17:57:23 node-2 kernel: [    0.976425] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov 13 17:57:23 node-2 kernel: [    0.990455] Linux agpgart interface v0.103
Nov 13 17:57:23 node-2 kernel: [    0.998124] brd: module loaded
Nov 13 17:57:23 node-2 kernel: [    1.005173] loop: module loaded
Nov 13 17:57:23 node-2 kernel: [    1.011888] libphy: Fixed MDIO Bus: probed
Nov 13 17:57:23 node-2 kernel: [    1.018365] tun: Universal TUN/TAP device driver, 1.6
Nov 13 17:57:23 node-2 kernel: [    1.024845] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 13 17:57:23 node-2 kernel: [    1.031376] PPP generic driver version 2.4.2
Nov 13 17:57:23 node-2 kernel: [    1.037762] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 13 17:57:23 node-2 kernel: [    1.044204] ehci-pci: EHCI PCI platform driver
Nov 13 17:57:23 node-2 kernel: [    1.050723] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov 13 17:57:23 node-2 kernel: [    1.057128] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov 13 17:57:23 node-2 kernel: [    1.069649] ehci-pci 0000:00:1a.0: debug port 2
Nov 13 17:57:23 node-2 kernel: [    1.079847] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov 13 17:57:23 node-2 kernel: [    1.079865] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov 13 17:57:23 node-2 kernel: [    1.096388] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov 13 17:57:23 node-2 kernel: [    1.102540] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 17:57:23 node-2 kernel: [    1.108752] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 17:57:23 node-2 kernel: [    1.120649] usb usb1: Product: EHCI Host Controller
Nov 13 17:57:23 node-2 kernel: [    1.126674] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 17:57:23 node-2 kernel: [    1.132723] usb usb1: SerialNumber: 0000:00:1a.0
Nov 13 17:57:23 node-2 kernel: [    1.138699] hub 1-0:1.0: USB hub found
Nov 13 17:57:23 node-2 kernel: [    1.144471] hub 1-0:1.0: 2 ports detected
Nov 13 17:57:23 node-2 kernel: [    1.150273] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov 13 17:57:23 node-2 kernel: [    1.155855] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov 13 17:57:23 node-2 kernel: [    1.166764] ehci-pci 0000:00:1d.0: debug port 2
Nov 13 17:57:23 node-2 kernel: [    1.176077] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov 13 17:57:23 node-2 kernel: [    1.176080] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov 13 17:57:23 node-2 kernel: [    1.192307] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov 13 17:57:23 node-2 kernel: [    1.197518] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov 13 17:57:23 node-2 kernel: [    1.202825] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 13 17:57:23 node-2 kernel: [    1.213496] usb usb2: Product: EHCI Host Controller
Nov 13 17:57:23 node-2 kernel: [    1.218968] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov 13 17:57:23 node-2 kernel: [    1.224525] usb usb2: SerialNumber: 0000:00:1d.0
Nov 13 17:57:23 node-2 kernel: [    1.230088] hub 2-0:1.0: USB hub found
Nov 13 17:57:23 node-2 kernel: [    1.235459] hub 2-0:1.0: 2 ports detected
Nov 13 17:57:23 node-2 kernel: [    1.240782] ehci-platform: EHCI generic platform driver
Nov 13 17:57:23 node-2 kernel: [    1.246033] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 13 17:57:23 node-2 kernel: [    1.251362] ohci-pci: OHCI PCI platform driver
Nov 13 17:57:23 node-2 kernel: [    1.256678] ohci-platform: OHCI generic platform driver
Nov 13 17:57:23 node-2 kernel: [    1.261895] uhci_hcd: USB Universal Host Controller Interface driver
Nov 13 17:57:23 node-2 kernel: [    1.267308] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov 13 17:57:23 node-2 kernel: [    1.460086] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov 13 17:57:23 node-2 kernel: [    1.771821] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov 13 17:57:23 node-2 kernel: [    1.788142] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov 13 17:57:23 node-2 kernel: [    1.793781] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 17:57:23 node-2 kernel: [    1.799536] hub 1-1:1.0: USB hub found
Nov 13 17:57:23 node-2 kernel: [    1.805127] hub 1-1:1.0: 6 ports detected
Nov 13 17:57:23 node-2 kernel: [    1.919716] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov 13 17:57:23 node-2 kernel: [    2.306472] i8042: No controller found
Nov 13 17:57:23 node-2 kernel: [    2.312027] mousedev: PS/2 mouse device common for all mice
Nov 13 17:57:23 node-2 kernel: [    2.317770] rtc_cmos 00:02: RTC can wake from S4
Nov 13 17:57:23 node-2 kernel: [    2.320133] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov 13 17:57:23 node-2 kernel: [    2.320134] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 13 17:57:23 node-2 kernel: [    2.320772] hub 2-1:1.0: USB hub found
Nov 13 17:57:23 node-2 kernel: [    2.321002] hub 2-1:1.0: 8 ports detected
Nov 13 17:57:23 node-2 kernel: [    2.346168] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov 13 17:57:23 node-2 kernel: [    2.351956] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 13 17:57:23 node-2 kernel: [    2.363328] device-mapper: uevent: version 1.0.3
Nov 13 17:57:23 node-2 kernel: [    2.369061] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov 13 17:57:23 node-2 kernel: [    2.380487] ledtrig-cpu: registered to indicate activity on CPUs
Nov 13 17:57:23 node-2 kernel: [    2.386481] TCP: cubic registered
Nov 13 17:57:23 node-2 kernel: [    2.392347] NET: Registered protocol family 10
Nov 13 17:57:23 node-2 kernel: [    2.398405] NET: Registered protocol family 17
Nov 13 17:57:23 node-2 kernel: [    2.404193] Key type dns_resolver registered
Nov 13 17:57:23 node-2 kernel: [    2.410249] Loading compiled-in X.509 certificates
Nov 13 17:57:23 node-2 kernel: [    2.416479] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov 13 17:57:23 node-2 kernel: [    2.428118] registered taskstats version 1
Nov 13 17:57:23 node-2 kernel: [    2.436204] Key type trusted registered
Nov 13 17:57:23 node-2 kernel: [    2.443802] Key type encrypted registered
Nov 13 17:57:23 node-2 kernel: [    2.449305] AppArmor: AppArmor sha1 policy hashing enabled
Nov 13 17:57:23 node-2 kernel: [    2.454810] IMA: No TPM chip found, activating TPM-bypass!
Nov 13 17:57:23 node-2 kernel: [    2.460874] regulator-dummy: disabling
Nov 13 17:57:23 node-2 kernel: [    2.466353]   Magic number: 8:701:946
Nov 13 17:57:23 node-2 kernel: [    2.471877] tty tty3: hash matches
Nov 13 17:57:23 node-2 kernel: [    2.477402] processor cpu1: hash matches
Nov 13 17:57:23 node-2 kernel: [    2.482769] rtc_cmos 00:02: setting system clock to 2016-11-13 17:56:49 UTC (1479059809)
Nov 13 17:57:23 node-2 kernel: [    2.495121] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov 13 17:57:23 node-2 kernel: [    2.500626] EDD information not available.
Nov 13 17:57:23 node-2 kernel: [    2.506107] PM: Hibernation image not present or could not be loaded.
Nov 13 17:57:23 node-2 kernel: [    2.506981] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov 13 17:57:23 node-2 kernel: [    2.518124] Write protecting the kernel read-only data: 12288k
Nov 13 17:57:23 node-2 kernel: [    2.524383] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov 13 17:57:23 node-2 kernel: [    2.536967] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov 13 17:57:23 node-2 kernel: [    2.568888] device-mapper: multipath: version 1.6.0 loaded
Nov 13 17:57:23 node-2 kernel: [    2.576743] systemd-udevd[216]: starting version 204
Nov 13 17:57:23 node-2 kernel: [    2.595122] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov 13 17:57:23 node-2 kernel: [    2.603377] md: linear personality registered for level -1
Nov 13 17:57:23 node-2 kernel: [    2.618428] md: multipath personality registered for level -4
Nov 13 17:57:23 node-2 kernel: [    2.626557] md: raid0 personality registered for level 0
Nov 13 17:57:23 node-2 kernel: [    2.634805] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov 13 17:57:23 node-2 kernel: [    2.641149] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov 13 17:57:23 node-2 kernel: [    2.641352] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov 13 17:57:23 node-2 kernel: [    2.653708] md: raid1 personality registered for level 1
Nov 13 17:57:23 node-2 kernel: [    2.654615] megasas: FW now in Ready state
Nov 13 17:57:23 node-2 kernel: [    2.654678] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654703] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654742] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654777] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654813] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654850] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654893] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654931] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.654965] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655001] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655034] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655114] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655152] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655186] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655222] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655259] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.655423] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov 13 17:57:23 node-2 kernel: [    2.664828] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Nov 13 17:57:23 node-2 kernel: [    2.664830] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov 13 17:57:23 node-2 kernel: [    2.664831] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 17:57:23 node-2 kernel: [    2.664896] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.664934] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.664973] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.665011] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.665076] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.677079] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Nov 13 17:57:23 node-2 kernel: [    2.677089] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Nov 13 17:57:23 node-2 kernel: [    2.677090] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov 13 17:57:23 node-2 kernel: [    2.677148] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.677185] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.677222] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.677259] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.677298] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.677338] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.677429] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.687075] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Nov 13 17:57:23 node-2 kernel: [    2.687076] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov 13 17:57:23 node-2 kernel: [    2.687077] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 17:57:23 node-2 kernel: [    2.687139] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.687168] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.687207] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.687245] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.687330] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.694573] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Nov 13 17:57:23 node-2 kernel: [    2.694574] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov 13 17:57:23 node-2 kernel: [    2.694575] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov 13 17:57:23 node-2 kernel: [    2.694633] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.694668] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.694707] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.694744] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.694831] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov 13 17:57:23 node-2 kernel: [    2.740453] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov 13 17:57:23 node-2 kernel: [    2.740454] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 17:57:23 node-2 kernel: [    2.740454] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov 13 17:57:23 node-2 kernel: [    2.740455] usb 2-1.4: Manufacturer: Avocent
Nov 13 17:57:23 node-2 kernel: [    2.740456] usb 2-1.4: SerialNumber: 20111102-00000001
Nov 13 17:57:23 node-2 kernel: [    2.914297] Switched to clocksource tsc
Nov 13 17:57:23 node-2 kernel: [    2.929130] hidraw: raw HID events driver (C) Jiri Kosina
Nov 13 17:57:23 node-2 kernel: [    2.939214] usbcore: registered new interface driver usbhid
Nov 13 17:57:23 node-2 kernel: [    2.945805] usbhid: USB HID core driver
Nov 13 17:57:23 node-2 kernel: [    2.953165] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Nov 13 17:57:23 node-2 kernel: [    2.966226] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Nov 13 17:57:23 node-2 kernel: [    2.979585] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Nov 13 17:57:23 node-2 kernel: [    2.982779] megasas:IOC Init cmd success
Nov 13 17:57:23 node-2 kernel: [    2.990807] raid6: sse2x1    9280 MB/s
Nov 13 17:57:23 node-2 kernel: [    3.006302] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Nov 13 17:57:23 node-2 kernel: [    3.010780] megasas: INIT adapter done
Nov 13 17:57:23 node-2 kernel: [    3.026206] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Nov 13 17:57:23 node-2 kernel: [    3.039796] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Nov 13 17:57:23 node-2 kernel: [    3.058713] raid6: sse2x2   14718 MB/s
Nov 13 17:57:23 node-2 kernel: [    3.106676] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov 13 17:57:23 node-2 kernel: [    3.113470] scsi0 : LSI SAS based MegaRAID driver
Nov 13 17:57:23 node-2 kernel: [    3.120990] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 17:57:23 node-2 kernel: [    3.130837] raid6: sse2x4   11179 MB/s
Nov 13 17:57:23 node-2 kernel: [    3.146402] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov 13 17:57:23 node-2 kernel: [    3.162344] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov 13 17:57:23 node-2 kernel: [    3.169154] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov 13 17:57:23 node-2 kernel: [    3.183075] sd 0:2:0:0: [sda] Write Protect is off
Nov 13 17:57:23 node-2 kernel: [    3.189989] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov 13 17:57:23 node-2 kernel: [    3.190009] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov 13 17:57:23 node-2 kernel: [    3.198708] raid6: avx2x1    3777 MB/s
Nov 13 17:57:23 node-2 kernel: [    3.246291]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Nov 13 17:57:23 node-2 kernel: [    3.253574] sd 0:2:0:0: [sda] Attached SCSI disk
Nov 13 17:57:23 node-2 kernel: [    3.266556] raid6: avx2x2   18518 MB/s
Nov 13 17:57:23 node-2 kernel: [    3.338476] raid6: avx2x4   30765 MB/s
Nov 13 17:57:23 node-2 kernel: [    3.344777] raid6: using algorithm avx2x4 (30765 MB/s)
Nov 13 17:57:23 node-2 kernel: [    3.351017] raid6: using avx2x2 recovery algorithm
Nov 13 17:57:23 node-2 kernel: [    3.357918] xor: automatically using best checksumming function:
Nov 13 17:57:23 node-2 kernel: [    3.402241] random: lvm urandom read with 27 bits of entropy available
Nov 13 17:57:23 node-2 kernel: [    3.402474]    avx       : 36175.000 MB/sec
Nov 13 17:57:23 node-2 kernel: [    3.415257] async_tx: api initialized (async)
Nov 13 17:57:23 node-2 kernel: [    3.425032] md: raid6 personality registered for level 6
Nov 13 17:57:23 node-2 kernel: [    3.430981] md: raid5 personality registered for level 5
Nov 13 17:57:23 node-2 kernel: [    3.436681] md: raid4 personality registered for level 4
Nov 13 17:57:23 node-2 kernel: [    3.445230] md: raid10 personality registered for level 10
Nov 13 17:57:23 node-2 kernel: [    3.490787] multipathd (372): /proc/372/oom_adj is deprecated, please use /proc/372/oom_score_adj instead.
Nov 13 17:57:23 node-2 kernel: [    3.519316] bio: create slab <bio-1> at 1
Nov 13 17:57:23 node-2 kernel: [    4.278958] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 17:57:23 node-2 kernel: [    4.969124] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov 13 17:57:23 node-2 kernel: [    5.025651] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov 13 17:57:23 node-2 kernel: [    5.157948] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov 13 17:57:23 node-2 kernel: [    5.199857] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov 13 17:57:23 node-2 kernel: [    5.274961] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 17:57:23 node-2 kernel: [    5.288207] random: nonblocking pool is initialized
Nov 13 17:57:23 node-2 kernel: [    5.458635] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov 13 17:57:23 node-2 kernel: [    5.494396] XFS (dm-0): Mounting Filesystem
Nov 13 17:57:23 node-2 kernel: [    5.744213] XFS (dm-0): Ending clean mount
Nov 13 17:57:23 node-2 kernel: [    5.879910] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov 13 17:57:23 node-2 kernel: [    5.911002] XFS (dm-1): Mounting Filesystem
Nov 13 17:57:23 node-2 kernel: [    6.014202] XFS (dm-1): Ending clean mount
Nov 13 17:57:23 node-2 kernel: [    7.797643] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov 13 17:57:23 node-2 kernel: [    7.824201] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov 13 17:57:23 node-2 kernel: [    8.003095] systemd-udevd[777]: starting version 204
Nov 13 17:57:23 node-2 kernel: [    8.250496] power_meter ACPI000D:00: Found ACPI power meter.
Nov 13 17:57:23 node-2 kernel: [    8.250566] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov 13 17:57:23 node-2 kernel: [    8.260249] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov 13 17:57:23 node-2 kernel: [    8.260255] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 17:57:23 node-2 kernel: [    8.260258] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov 13 17:57:23 node-2 kernel: [    8.260260] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 13 17:57:23 node-2 kernel: [    8.260340] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 13 17:57:23 node-2 kernel: [    8.269272] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov 13 17:57:23 node-2 kernel: [    8.278875] IPMI System Interface driver.
Nov 13 17:57:23 node-2 kernel: [    8.278915] ipmi_si: probing via ACPI
Nov 13 17:57:23 node-2 kernel: [    8.278925] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov 13 17:57:23 node-2 kernel: [    8.278926] ipmi_si: Adding ACPI-specified kcs state machine
Nov 13 17:57:23 node-2 kernel: [    8.278933] ipmi_si: probing via SMBIOS
Nov 13 17:57:23 node-2 kernel: [    8.278934] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 17:57:23 node-2 kernel: [    8.278935] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov 13 17:57:23 node-2 kernel: [    8.278936] ipmi_si: probing via SPMI
Nov 13 17:57:23 node-2 kernel: [    8.278937] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov 13 17:57:23 node-2 kernel: [    8.278937] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov 13 17:57:23 node-2 kernel: [    8.278939] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov 13 17:57:23 node-2 kernel: [    8.306983] wmi: Mapper loaded
Nov 13 17:57:23 node-2 kernel: [    8.386694] systemd-udevd[808]: renamed network interface eth2 to enp8s0
Nov 13 17:57:23 node-2 kernel: [    8.422574] systemd-udevd[816]: renamed network interface eth1 to enp7s0
Nov 13 17:57:23 node-2 kernel: [    8.462716] systemd-udevd[818]: renamed network interface eth3 to enp9s0
Nov 13 17:57:23 node-2 kernel: [    8.466300] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov 13 17:57:23 node-2 kernel: [    8.466393] ipmi_si 00:09: IPMI kcs interface initialized
Nov 13 17:57:23 node-2 kernel: [    8.490485] systemd-udevd[814]: renamed network interface eth0 to enp6s0
Nov 13 17:57:23 node-2 kernel: [    8.728674] type=1400 audit(1479059815.747:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.728834] type=1400 audit(1479059815.747:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1052 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.728961] type=1400 audit(1479059815.747:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1052 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.735866] type=1400 audit(1479059815.755:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.736009] type=1400 audit(1479059815.755:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.736129] type=1400 audit(1479059815.755:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.740732] type=1400 audit(1479059815.759:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.740875] type=1400 audit(1479059815.759:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.740994] type=1400 audit(1479059815.759:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    8.760236] type=1400 audit(1479059815.779:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Nov 13 17:57:23 node-2 kernel: [    9.258286] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov 13 17:57:23 node-2 kernel: [    9.259480] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov 13 17:57:23 node-2 kernel: [    9.442162] enic 0000:06:00.0 enp6s0: Link UP
Nov 13 17:57:23 node-2 kernel: [    9.442595] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov 13 17:57:23 node-2 kernel: [    9.442600] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov 13 17:57:23 node-2 kernel: [   18.765819] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov 13 17:57:23 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov 13 17:57:24 node-2 failsafe: Failsafe of 120 seconds reached.
Nov 13 17:57:24 node-2 kernel: [   37.428030] init: failsafe main process (8415) killed by TERM signal
Nov 13 17:57:25 node-2 dbus[8481]: [system] AppArmor D-Bus mediation is enabled
Nov 13 17:57:25 node-2 kernel: [   37.627787] audit_printk_skb: 30 callbacks suppressed
Nov 13 17:57:25 node-2 kernel: [   37.627790] type=1400 audit(1479059845.167:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8534 comm="apparmor_parser"
Nov 13 17:57:25 node-2 kernel: [   37.628065] type=1400 audit(1479059845.167:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8533 comm="apparmor_parser"
Nov 13 17:57:25 node-2 kernel: [   37.628069] type=1400 audit(1479059845.167:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8533 comm="apparmor_parser"
Nov 13 17:57:25 node-2 kernel: [   37.628073] type=1400 audit(1479059845.167:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8533 comm="apparmor_parser"
Nov 13 17:57:25 node-2 kernel: [   37.628295] type=1400 audit(1479059845.167:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8533 comm="apparmor_parser"
Nov 13 17:57:25 node-2 kernel: [   37.628297] type=1400 audit(1479059845.167:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8533 comm="apparmor_parser"
Nov 13 17:57:25 node-2 kernel: [   37.628413] type=1400 audit(1479059845.167:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8533 comm="apparmor_parser"
Nov 13 17:57:25 node-2 kernel: [   37.748357] type=1400 audit(1479059845.287:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8536 comm="apparmor_parser"
Nov 13 17:57:25 node-2 cron[8574]: (CRON) INFO (pidfile fd = 3)
Nov 13 17:57:25 node-2 anacron[8599]: Anacron 2.3 started on 2016-11-13
Nov 13 17:57:25 node-2 cron[8611]: (CRON) STARTUP (fork ok)
Nov 13 17:57:25 node-2 anacron[8599]: Will run job `cron.daily' in 5 min.
Nov 13 17:57:25 node-2 anacron[8599]: Will run job `cron.weekly' in 10 min.
Nov 13 17:57:25 node-2 anacron[8599]: Will run job `cron.monthly' in 15 min.
Nov 13 17:57:25 node-2 anacron[8599]: Jobs will be executed sequentially
Nov 13 17:57:25 node-2 cron[8611]: (CRON) INFO (Running @reboot jobs)
Nov 13 17:57:25 node-2 multipathd: path checkers start up
Nov 13 17:57:26 node-2 postfix/master[8753]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov 13 17:57:28 node-2 puppet-agent[8938]: Reopening log files
Nov 13 17:57:29 node-2 puppet-agent[8938]: Could not request certificate: Connection refused - connect(2)
Nov 13 17:57:44 node-2 puppet-user[9017]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov 13 17:57:44 node-2 puppet-user[9017]: Compiled catalog for node-2.domain.tld in environment production in 0.01 seconds
Nov 13 17:57:45 node-2 puppet-user[9017]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov 13 17:57:45 node-2 puppet-user[9017]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov 13 17:57:45 node-2 puppet-user[9017]: Finished catalog run in 1.33 seconds
Nov 13 17:57:47 node-2 multipathd: uevent trigger error
Nov 13 17:57:47 node-2 puppet-user[9472]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 17:57:47 node-2 puppet-user[9472]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov 13 17:57:47 node-2 puppet-user[9472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov 13 17:57:47 node-2 puppet-user[9472]: Finished catalog run in 0.05 seconds
Nov 13 17:57:48 node-2 puppet-user[9932]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov 13 17:57:48 node-2 puppet-user[9932]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Nov 13 17:57:48 node-2 puppet-user[9932]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov 13 17:57:48 node-2 puppet-user[9932]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov 13 17:57:48 node-2 puppet-user[9932]: Finished catalog run in 0.02 seconds
Nov 13 17:57:50 node-2 puppet-user[10501]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov 13 17:57:50 node-2 puppet-user[10501]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Nov 13 17:57:50 node-2 puppet-user[10501]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov 13 17:57:50 node-2 puppet-user[10501]: Finished catalog run in 0.03 seconds
Nov 13 17:57:51 node-2 puppet-user[10971]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov 13 17:57:51 node-2 puppet-user[10971]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Nov 13 17:57:51 node-2 puppet-user[10971]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov 13 17:57:52 node-2 puppet-user[10971]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Nov 13 17:57:52 node-2 puppet-user[10971]: Finished catalog run in 0.68 seconds
Nov 13 17:57:53 node-2 puppet-user[11455]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov 13 17:57:53 node-2 puppet-user[11455]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Nov 13 17:57:53 node-2 puppet-user[11455]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov 13 17:57:53 node-2 puppet-user[11455]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov 13 17:57:54 node-2 puppet-user[11455]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Nov 13 17:57:54 node-2 puppet-user[11455]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov 13 17:57:54 node-2 puppet-user[11455]: Finished catalog run in 0.22 seconds
Nov 13 17:57:55 node-2 puppet-user[11928]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov 13 17:57:55 node-2 puppet-user[11928]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Nov 13 17:57:55 node-2 puppet-user[11928]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov 13 17:57:55 node-2 kernel: [   68.217391] nr_pdflush_threads exported in /proc is scheduled for removal
Nov 13 17:57:55 node-2 kernel: [   68.217439] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Nov 13 17:57:55 node-2 puppet-user[11928]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Nov 13 17:57:55 node-2 puppet-user[11928]: Finished catalog run in 0.05 seconds
Nov 13 17:57:57 node-2 puppet-user[12390]: (Scope(Class[main])) MODULAR: sync_time
Nov 13 17:57:57 node-2 puppet-user[12390]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Nov 13 17:57:57 node-2 ntpdate[12805]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov 13 17:58:01 node-2 CRON[12892]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov 13 17:58:03 node-2 ntpdate[12805]: adjust time server 10.20.0.2 offset -0.247496 sec
Nov 13 17:58:03 node-2 puppet-user[12390]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov 13 17:58:03 node-2 puppet-user[12390]: Finished catalog run in 6.18 seconds
Nov 13 17:58:10 node-2 puppet-user[13193]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov 13 17:58:10 node-2 puppet-user[13193]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Nov 13 17:58:11 node-2 puppet-user[13193]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov 13 17:58:11 node-2 puppet-user[13193]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Nov 13 17:58:11 node-2 puppet-user[13193]: Finished catalog run in 0.07 seconds
Nov 13 17:58:12 node-2 puppet-user[13646]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov 13 17:58:12 node-2 puppet-user[13646]: Compiled catalog for node-2.domain.tld in environment production in 0.41 seconds
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov 13 17:58:12 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Nov 13 17:58:13 node-2 puppet-user[13646]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov 13 17:58:13 node-2 puppet-user[13646]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov 13 17:58:13 node-2 puppet-user[13646]: Finished catalog run in 0.82 seconds
Nov 13 17:58:14 node-2 kernel: [   86.664587] init: plymouth-upstart-bridge main process ended, respawning
Nov 13 17:58:14 node-2 puppet-agent[8938]: Could not run: SIGTERM
Nov 13 17:58:14 node-2 kernel: [   86.928284] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 13 17:58:14 node-2 ec2: 
Nov 13 17:58:14 node-2 ec2: #############################################################
Nov 13 17:58:14 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov 13 17:58:14 node-2 ec2: 1024 0f:02:85:f6:f2:a4:4e:97:72:7d:79:a4:f7:1d:aa:2d  root@node-2.domain.tld (DSA)
Nov 13 17:58:14 node-2 ec2: 256 b3:9e:73:3e:a1:83:af:51:33:f5:1e:e5:b4:f4:8a:fa  root@node-2.domain.tld (ECDSA)
Nov 13 17:58:14 node-2 ec2: 256 1c:e7:2c:6f:f7:53:b4:a9:c1:44:b6:9f:39:93:3d:b3  root@node-2.domain.tld (ED25519)
Nov 13 17:58:14 node-2 ec2: 2048 b1:f5:56:05:66:07:dc:98:94:87:d5:b3:47:ed:fc:d7  root@node-2.domain.tld (RSA)
Nov 13 17:58:14 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov 13 17:58:14 node-2 ec2: #############################################################
Nov 13 17:58:15 node-2 puppet-user[14261]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov 13 17:58:15 node-2 puppet-user[14261]: Compiled catalog for node-2.domain.tld in environment production in 0.12 seconds
Nov 13 17:58:15 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 17:58:15 node-2 nailgun-agent: D, [2016-11-13T17:58:01.685627 #12895] DEBUG -- : Sleep for 14 seconds before sending request
Nov 13 17:58:15 node-2 nailgun-agent: I, [2016-11-13T17:58:15.700844 #12895]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov 13 17:58:16 node-2 nailgun-agent: D, [2016-11-13T17:58:16.128957 #12895] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Nov 13 17:58:18 node-2 puppet-user[14261]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.292937 #12895] DEBUG -- : Trying to find block devices
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.293190 #12895] DEBUG -- : Found block device: sda
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.293430 #12895] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.293506 #12895] DEBUG -- : Trying to get list of physical devices
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.293925 #12895] DEBUG -- : Getting udev properties for device: sda
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.297535 #12895] 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"=>"0x618e72837273a7701cc788
Nov 13 17:58:28 node-2 nailgun-agent: 6005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2887", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.297593 #12895] DEBUG -- : Trying to find out if device sda is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.297754 #12895] DEBUG -- : Device sda removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.297788 #12895] DEBUG -- : Device sda seems to be appropriate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.298526 #12895] DEBUG -- : Getting udev properties for device: dm-0
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.301454 #12895] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-B0ejkGgqV0163IUZeKiyrcHnHJ6iJzRaaR2N29ZQajequmwmZJRJJEEpcG5c2kUG /dev/disk/by-uuid/d1f14432-5e58-4c5e-bb12-7c90b83f776e /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-B0ejkGgqV0163IUZeKiyrcHnHJ6iJzRaaR2N29ZQajequmwmZJRJJEEpcG5c2kUG", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d1f14432-5e58-4c5e-bb12-7c90b83f776e", "ID_FS_UUID_ENC"=>"d1f14432-5e58-4c5e-bb12-7c90b83f776e", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"68931", "nomdmonddf"=>"1", "nom
Nov 13 17:58:28 node-2 nailgun-agent: dmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.301506 #12895] DEBUG -- : Trying to find out if device dm-0 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.301566 #12895] DEBUG -- : Device dm-0 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.301597 #12895] DEBUG -- : Device dm-0 seems to be appropriate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.301659 #12895] DEBUG -- : Getting udev properties for device: dm-1
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.304504 #12895] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-tV3lNjWc2Q8xwL2co9NliB08w2VOcrohpRphP85Nm2zNPBfD38oImRmkl9By1noQ /dev/disk/by-uuid/d2a93c79-18a7-4444-9380-f52697e7f2f5 /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-tV3lNjWc2Q8xwL2co9NliB08w2VOcrohpRphP85Nm2zNPBfD38oImRmkl9By1noQ", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d2a93c79-18a7-4444-9380-f52697e7f2f5", "ID_FS_UUID_ENC"=>"d2a93c79-18a7-4444-9380-f52697e7f2f5", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1
Nov 13 17:58:28 node-2 nailgun-agent: 5623", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.304556 #12895] DEBUG -- : Trying to find out if device dm-1 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.304661 #12895] DEBUG -- : Device dm-1 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.304691 #12895] DEBUG -- : Device dm-1 seems to be appropriate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.304762 #12895] DEBUG -- : Getting udev properties for device: dm-2
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.307723 #12895] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-DqYfs2dvkYL4FgkF7HWZlGvF3F5ZT9aGV3o6mWLc8bXz1i0Swi8aPPqpqrpD5Z4G /dev/disk/by-uuid/6d9d9b63-46cd-4929-b92d-aa6fe886204a /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-DqYfs2dvkYL4FgkF7HWZlGvF3F5ZT9aGV3o6mWLc8bXz1i0Swi8aPPqpqrpD5Z4G", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6d9d9b63-46cd-4929-b92d-aa6fe886204a", "ID_FS_UUID_ENC"=>"6d9d9b63-46cd-4929-b92d-aa6fe886204a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18201", "nomdmon
Nov 13 17:58:28 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.307796 #12895] DEBUG -- : Trying to find out if device dm-2 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.307859 #12895] DEBUG -- : Device dm-2 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.307890 #12895] DEBUG -- : Device dm-2 seems to be appropriate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.307918 #12895] DEBUG -- : Getting udev properties for device: dm-3
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.311412 #12895] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-HgFifHdui3VVqTdQj3YdSq9h4uMVkJhRzOAyjeV29ZVGYhnDA2CHdqE2UeFjCCQa /dev/disk/by-uuid/2ca5fb67-8294-4f96-8998-e2b04ccd85d5 /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-HgFifHdui3VVqTdQj3YdSq9h4uMVkJhRzOAyjeV29ZVGYhnDA2CHdqE2UeFjCCQa", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2ca5fb67-8294-4f96-8998-e2b04ccd85d5", "ID_FS_UUID_ENC"=>"2ca5fb67-8294-4f96-8998-e2b04ccd85d5", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15327", "nomdmonddf"=>"1",
Nov 13 17:58:28 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.311465 #12895] DEBUG -- : Trying to find out if device dm-3 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.311572 #12895] DEBUG -- : Device dm-3 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.311602 #12895] DEBUG -- : Device dm-3 seems to be appropriate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.311630 #12895] DEBUG -- : Getting udev properties for device: dm-4
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.314979 #12895] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-qXUfR3NfR78F3I6AltEBEAU6KWqWzVA7ML0fMlkvCePHMLmdVNjxOkjVWJQ4I8Z8 /dev/disk/by-uuid/1a563ffb-a918-4b74-bbbe-68b798d2b427 /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-qXUfR3NfR78F3I6AltEBEAU6KWqWzVA7ML0fMlkvCePHMLmdVNjxOkjVWJQ4I8Z8", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1a563ffb-a918-4b74-bbbe-68b798d2b427", "ID_FS_UUID_ENC"=>"1a563ffb-a918-4b74-bbbe-68b798d2b427", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21312", "nomdmonddf"=>"1", "nom
Nov 13 17:58:28 node-2 nailgun-agent: dmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.315031 #12895] DEBUG -- : Trying to find out if device dm-4 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.315091 #12895] DEBUG -- : Device dm-4 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.315121 #12895] DEBUG -- : Device dm-4 seems to be appropriate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.315163 #12895] DEBUG -- : Getting udev properties for device: dm-5
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.318115 #12895] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-qXUfR3NfR78F3I6AltEBEAU6KWqWzVA7aMdWtHdbwEx8OBvqXU9T2Xk37rvpRSl6 /dev/disk/by-uuid/bd4b6125-f45d-4602-99f5-a6cd14b3a169 /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-qXUfR3NfR78F3I6AltEBEAU6KWqWzVA7aMdWtHdbwEx8OBvqXU9T2Xk37rvpRSl6", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"bd4b6125-f45d-4602-99f5-a6cd14b3a169", "ID_FS_UUID_ENC"=>"bd4b6125-f45d-4602-99f5-a6cd14b3a169", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21705", "nomdmonddf"=>"1", "nomdmonisw
Nov 13 17:58:28 node-2 nailgun-agent: "=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.318166 #12895] DEBUG -- : Trying to find out if device dm-5 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.318328 #12895] DEBUG -- : Device dm-5 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.318357 #12895] DEBUG -- : Device dm-5 seems to be appropriate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.318386 #12895] DEBUG -- : Getting udev properties for device: ram0
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.321403 #12895] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71966", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.321455 #12895] DEBUG -- : Trying to find out if device ram0 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.321525 #12895] DEBUG -- : Device ram0 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.321565 #12895] DEBUG -- : Getting udev properties for device: ram1
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.324599 #12895] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71974", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.324661 #12895] DEBUG -- : Trying to find out if device ram1 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.324775 #12895] DEBUG -- : Device ram1 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.324825 #12895] DEBUG -- : Getting udev properties for device: ram2
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.327737 #12895] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72037", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.327798 #12895] DEBUG -- : Trying to find out if device ram2 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.327892 #12895] DEBUG -- : Device ram2 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.327985 #12895] DEBUG -- : Getting udev properties for device: ram3
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.331150 #12895] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72053", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.331219 #12895] DEBUG -- : Trying to find out if device ram3 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.331335 #12895] DEBUG -- : Device ram3 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.331380 #12895] DEBUG -- : Getting udev properties for device: ram4
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.334557 #12895] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72069", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.334616 #12895] DEBUG -- : Trying to find out if device ram4 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.334690 #12895] DEBUG -- : Device ram4 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.334773 #12895] DEBUG -- : Getting udev properties for device: ram5
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.337826 #12895] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72085", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.337886 #12895] DEBUG -- : Trying to find out if device ram5 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.337967 #12895] DEBUG -- : Device ram5 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.338060 #12895] DEBUG -- : Getting udev properties for device: ram6
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.340884 #12895] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72102", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.340970 #12895] DEBUG -- : Trying to find out if device ram6 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.341049 #12895] DEBUG -- : Device ram6 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.341099 #12895] DEBUG -- : Getting udev properties for device: ram7
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.344144 #12895] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72120", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.344206 #12895] DEBUG -- : Trying to find out if device ram7 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.344296 #12895] DEBUG -- : Device ram7 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.344347 #12895] DEBUG -- : Getting udev properties for device: ram8
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.347350 #12895] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72135", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.347415 #12895] DEBUG -- : Trying to find out if device ram8 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.347563 #12895] DEBUG -- : Device ram8 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.347612 #12895] DEBUG -- : Getting udev properties for device: ram9
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.350829 #12895] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72155", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.350892 #12895] DEBUG -- : Trying to find out if device ram9 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.350983 #12895] DEBUG -- : Device ram9 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.351032 #12895] DEBUG -- : Getting udev properties for device: loop0
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.354291 #12895] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71907", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.354353 #12895] DEBUG -- : Trying to find out if device loop0 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.354436 #12895] DEBUG -- : Device loop0 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.354529 #12895] DEBUG -- : Getting udev properties for device: loop1
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.357652 #12895] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71916", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.357724 #12895] DEBUG -- : Trying to find out if device loop1 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.357815 #12895] DEBUG -- : Device loop1 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.357894 #12895] DEBUG -- : Getting udev properties for device: loop2
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.361176 #12895] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71924", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.361246 #12895] DEBUG -- : Trying to find out if device loop2 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.361494 #12895] DEBUG -- : Device loop2 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.361565 #12895] DEBUG -- : Getting udev properties for device: loop3
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.364869 #12895] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71930", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.364962 #12895] DEBUG -- : Trying to find out if device loop3 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.365087 #12895] DEBUG -- : Device loop3 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.365149 #12895] DEBUG -- : Getting udev properties for device: loop4
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.368327 #12895] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71937", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.368399 #12895] DEBUG -- : Trying to find out if device loop4 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.368533 #12895] DEBUG -- : Device loop4 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.368625 #12895] DEBUG -- : Getting udev properties for device: loop5
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.372019 #12895] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71946", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.372089 #12895] DEBUG -- : Trying to find out if device loop5 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.372211 #12895] DEBUG -- : Device loop5 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.372267 #12895] DEBUG -- : Getting udev properties for device: loop6
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.375698 #12895] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71953", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.375787 #12895] DEBUG -- : Trying to find out if device loop6 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.375908 #12895] DEBUG -- : Device loop6 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.375965 #12895] DEBUG -- : Getting udev properties for device: loop7
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.379318 #12895] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71959", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.379391 #12895] DEBUG -- : Trying to find out if device loop7 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.379537 #12895] DEBUG -- : Device loop7 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.379597 #12895] DEBUG -- : Getting udev properties for device: ram10
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.382966 #12895] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71981", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.383057 #12895] DEBUG -- : Trying to find out if device ram10 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.383166 #12895] DEBUG -- : Device ram10 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.383255 #12895] DEBUG -- : Getting udev properties for device: ram11
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.386408 #12895] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71987", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.386479 #12895] DEBUG -- : Trying to find out if device ram11 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.386625 #12895] DEBUG -- : Device ram11 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.386678 #12895] DEBUG -- : Getting udev properties for device: ram12
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.389949 #12895] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71994", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.390051 #12895] DEBUG -- : Trying to find out if device ram12 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.390154 #12895] DEBUG -- : Device ram12 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.390210 #12895] DEBUG -- : Getting udev properties for device: ram13
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.393555 #12895] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72005", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.393616 #12895] DEBUG -- : Trying to find out if device ram13 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.393726 #12895] DEBUG -- : Device ram13 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.393772 #12895] DEBUG -- : Getting udev properties for device: ram14
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.404586 #12895] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72016", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.404639 #12895] DEBUG -- : Trying to find out if device ram14 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.404721 #12895] DEBUG -- : Device ram14 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.404760 #12895] DEBUG -- : Getting udev properties for device: ram15
Nov 13 17:58:28 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.407871 #12895] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72025", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408006 #12895] DEBUG -- : Trying to find out if device ram15 is removable or not
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408093 #12895] DEBUG -- : Device ram15 removable parameter: "0"
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408157 #12895] 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"}]
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408184 #12895] DEBUG -- : Block device seems to be physical data storage: sda
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408245 #12895] DEBUG -- : Found block device: dm-0
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408273 #12895] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408296 #12895] DEBUG -- : Found block device: dm-1
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408319 #12895] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408337 #12895] DEBUG -- : Found block device: dm-2
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408357 #12895] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408449 #12895] DEBUG -- : Found block device: dm-3
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408470 #12895] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408488 #12895] DEBUG -- : Found block device: dm-4
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408507 #12895] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408529 #12895] DEBUG -- : Found block device: dm-5
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408547 #12895] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408565 #12895] DEBUG -- : Found block device: ram0
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408584 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408600 #12895] DEBUG -- : Found block device: ram1
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408688 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408705 #12895] DEBUG -- : Found block device: ram2
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408722 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408740 #12895] DEBUG -- : Found block device: ram3
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408761 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408778 #12895] DEBUG -- : Found block device: ram4
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408797 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408813 #12895] DEBUG -- : Found block device: ram5
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408832 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408913 #12895] DEBUG -- : Found block device: ram6
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408934 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408951 #12895] DEBUG -- : Found block device: ram7
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408969 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.408986 #12895] DEBUG -- : Found block device: ram8
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409005 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409021 #12895] DEBUG -- : Found block device: ram9
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409038 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409054 #12895] DEBUG -- : Found block device: loop0
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409074 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409153 #12895] DEBUG -- : Found block device: loop1
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409174 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409192 #12895] DEBUG -- : Found block device: loop2
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409212 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409228 #12895] DEBUG -- : Found block device: loop3
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409245 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409262 #12895] DEBUG -- : Found block device: loop4
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409281 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409297 #12895] DEBUG -- : Found block device: loop5
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409409 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409432 #12895] DEBUG -- : Found block device: loop6
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409451 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409467 #12895] DEBUG -- : Found block device: loop7
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409485 #12895] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409501 #12895] DEBUG -- : Found block device: ram10
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409523 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409539 #12895] DEBUG -- : Found block device: ram11
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409557 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409637 #12895] DEBUG -- : Found block device: ram12
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409659 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409675 #12895] DEBUG -- : Found block device: ram13
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409694 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409710 #12895] DEBUG -- : Found block device: ram14
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409727 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409743 #12895] DEBUG -- : Found block device: ram15
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409762 #12895] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.409815 #12895] 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}]
Nov 13 17:58:28 node-2 nailgun-agent: D, [2016-11-13T17:58:28.581779 #12895] DEBUG -- : Response: status: 200 body: {"id": 2}
Nov 13 17:58:28 node-2 nailgun-agent: I, [2016-11-13T17:58:28.582548 #12895]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov 13 17:58:44 node-2 puppet-user[14261]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov 13 17:58:45 node-2 puppet-user[14261]: Finished catalog run in 29.55 seconds
Nov 13 17:58:46 node-2 puppet-user[17031]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov 13 17:58:47 node-2 puppet-user[17031]: Compiled catalog for node-2.domain.tld in environment production in 0.55 seconds
Nov 13 17:58:47 node-2 puppet-user[17031]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov 13 17:58:47 node-2 puppet-user[17031]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov 13 17:58:47 node-2 puppet-user[17031]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov 13 17:58:47 node-2 puppet-user[17031]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov 13 17:58:47 node-2 puppet-user[17031]: Finished catalog run in 0.07 seconds
Nov 13 17:58:49 node-2 puppet-user[17485]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov 13 17:58:50 node-2 puppet-user[17485]: Compiled catalog for node-2.domain.tld in environment production in 0.97 seconds
Nov 13 17:58:50 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov 13 17:58:50 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov 13 17:58:50 node-2 crontab[17926]: (root) LIST (root)
Nov 13 17:58:50 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov 13 17:58:50 node-2 crontab[17927]: (root) REPLACE (root)
Nov 13 17:58:51 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Nov 13 17:58:52 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov 13 17:58:53 node-2 puppet-user[17485]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov 13 17:58:53 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8388" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov 13 17:58:53 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov 13 17:58:55 node-2 multipathd: uevent trigger error
<27>Nov 13 17:58:55 node-2 multipathd: uevent trigger error
<27>Nov 13 17:58:55 node-2 multipathd: uevent trigger error
<27>Nov 13 17:58:55 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:08 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:08 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:08 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:08 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:10 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:10 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:10 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:10 node-2 multipathd: uevent trigger error
<27>Nov 13 17:59:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:05 node-2 ntpdate[28834]: no servers can be used, exiting
<27>Nov 13 18:00:05 node-2 ntpdate[28938]: no servers can be used, exiting
<27>Nov 13 18:00:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:39 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:39 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:39 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:39 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:39 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:39 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:00:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:01:59 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 18:01:59 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 18:02:05 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 18:02:05 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 18:02:11 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 18:02:16 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 18:02:16 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov 13 18:02:23 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:23 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:23 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:23 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:23 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:51 node-2 multipathd: uevent trigger error
<129>Nov 13 18:02:53 node-2 haproxy[18500]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:02:54 node-2 haproxy[18504]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:02:55 node-2 haproxy[18504]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:02:55 node-2 haproxy[18504]: proxy mysqld has no server available!
<27>Nov 13 18:02:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:02:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:00 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:03 node-2 haproxy[21060]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:03 node-2 haproxy[21060]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:03 node-2 haproxy[21060]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:03 node-2 haproxy[21060]: proxy mysqld has no server available!
<129>Nov 13 18:03:04 node-2 haproxy[21069]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:04 node-2 haproxy[21069]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:04 node-2 haproxy[21069]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:04 node-2 haproxy[21069]: proxy object-storage has no server available!
<27>Nov 13 18:03:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:06 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:08 node-2 haproxy[22442]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:08 node-2 haproxy[22442]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:08 node-2 haproxy[22442]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:08 node-2 haproxy[22442]: proxy neutron has no server available!
<129>Nov 13 18:03:09 node-2 haproxy[22453]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:09 node-2 haproxy[22453]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:09 node-2 haproxy[22453]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:09 node-2 haproxy[22453]: proxy mysqld has no server available!
<129>Nov 13 18:03:09 node-2 haproxy[22453]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:09 node-2 haproxy[22453]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:10 node-2 haproxy[22453]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:10 node-2 haproxy[22453]: proxy object-storage has no server available!
<27>Nov 13 18:03:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:11 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:13 node-2 haproxy[23996]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:13 node-2 haproxy[23996]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:14 node-2 haproxy[24000]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:14 node-2 haproxy[24000]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:14 node-2 haproxy[24000]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:14 node-2 haproxy[24000]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:14 node-2 haproxy[24000]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:14 node-2 haproxy[24000]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:14 node-2 haproxy[24000]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:14 node-2 haproxy[24000]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:14 node-2 haproxy[24000]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:14 node-2 haproxy[24000]: proxy neutron has no server available!
<129>Nov 13 18:03:15 node-2 haproxy[24000]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:15 node-2 haproxy[24000]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:15 node-2 haproxy[24000]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:15 node-2 haproxy[24000]: proxy mysqld has no server available!
<129>Nov 13 18:03:15 node-2 haproxy[24000]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:15 node-2 haproxy[24000]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:15 node-2 haproxy[24000]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:15 node-2 haproxy[24000]: proxy object-storage has no server available!
<27>Nov 13 18:03:17 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:17 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:17 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:17 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:17 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:19 node-2 haproxy[25329]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:19 node-2 haproxy[25329]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:19 node-2 haproxy[25329]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:20 node-2 haproxy[25333]: proxy neutron has no server available!
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:20 node-2 haproxy[25333]: proxy mysqld has no server available!
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:20 node-2 haproxy[25333]: proxy object-storage has no server available!
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:20 node-2 haproxy[25333]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:21 node-2 haproxy[25333]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:21 node-2 haproxy[25333]: proxy aodh has no server available!
<27>Nov 13 18:03:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:22 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:24 node-2 haproxy[26859]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:24 node-2 haproxy[26859]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:24 node-2 haproxy[26859]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:24 node-2 haproxy[26859]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:24 node-2 haproxy[26859]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:25 node-2 haproxy[26863]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:25 node-2 haproxy[26863]: proxy neutron has no server available!
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:25 node-2 haproxy[26863]: proxy mysqld has no server available!
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:25 node-2 haproxy[26863]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:26 node-2 haproxy[26863]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:26 node-2 haproxy[26863]: proxy object-storage has no server available!
<129>Nov 13 18:03:26 node-2 haproxy[26863]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:26 node-2 haproxy[26863]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:26 node-2 haproxy[26863]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:26 node-2 haproxy[26863]: proxy aodh has no server available!
<129>Nov 13 18:03:26 node-2 haproxy[26863]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:26 node-2 haproxy[26863]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:26 node-2 haproxy[26863]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:26 node-2 haproxy[26863]: proxy ceilometer has no server available!
<27>Nov 13 18:03:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:28 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:30 node-2 haproxy[28171]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:30 node-2 haproxy[28171]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:30 node-2 haproxy[28171]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:30 node-2 haproxy[28171]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:30 node-2 haproxy[28171]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:30 node-2 haproxy[28171]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:30 node-2 haproxy[28171]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:30 node-2 haproxy[28171]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:30 node-2 haproxy[28171]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:31 node-2 haproxy[28175]: proxy neutron has no server available!
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:31 node-2 haproxy[28175]: proxy mysqld has no server available!
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:31 node-2 haproxy[28175]: proxy object-storage has no server available!
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:31 node-2 haproxy[28175]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:31 node-2 haproxy[28175]: proxy aodh has no server available!
<129>Nov 13 18:03:32 node-2 haproxy[28175]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:32 node-2 haproxy[28175]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:32 node-2 haproxy[28175]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:32 node-2 haproxy[28175]: proxy ceilometer has no server available!
<27>Nov 13 18:03:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:33 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:35 node-2 haproxy[29503]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:35 node-2 haproxy[29503]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:35 node-2 haproxy[29503]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:36 node-2 haproxy[29507]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:36 node-2 haproxy[29507]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:36 node-2 haproxy[29507]: proxy neutron has no server available!
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:36 node-2 haproxy[29507]: proxy mysqld has no server available!
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:36 node-2 haproxy[29507]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:37 node-2 haproxy[29507]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:37 node-2 haproxy[29507]: proxy object-storage has no server available!
<129>Nov 13 18:03:37 node-2 haproxy[29507]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:37 node-2 haproxy[29507]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:37 node-2 haproxy[29507]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:37 node-2 haproxy[29507]: proxy aodh has no server available!
<129>Nov 13 18:03:37 node-2 haproxy[29507]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:37 node-2 haproxy[29507]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:37 node-2 haproxy[29507]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:37 node-2 haproxy[29507]: proxy ceilometer has no server available!
<27>Nov 13 18:03:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:38 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:41 node-2 haproxy[30872]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:41 node-2 haproxy[30872]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:41 node-2 haproxy[30872]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:42 node-2 haproxy[30876]: proxy glance-api has no server available!
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:42 node-2 haproxy[30876]: proxy glance-glare has no server available!
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:42 node-2 haproxy[30876]: proxy neutron has no server available!
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:42 node-2 haproxy[30876]: proxy glance-registry has no server available!
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:42 node-2 haproxy[30876]: proxy mysqld has no server available!
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:42 node-2 haproxy[30876]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:43 node-2 haproxy[30876]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:43 node-2 haproxy[30876]: proxy object-storage has no server available!
<129>Nov 13 18:03:43 node-2 haproxy[30876]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:43 node-2 haproxy[30876]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:43 node-2 haproxy[30876]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:43 node-2 haproxy[30876]: proxy aodh has no server available!
<129>Nov 13 18:03:43 node-2 haproxy[30876]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:43 node-2 haproxy[30876]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:43 node-2 haproxy[30876]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:43 node-2 haproxy[30876]: proxy ceilometer has no server available!
<27>Nov 13 18:03:44 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:44 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:44 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:44 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:44 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:47 node-2 haproxy[32262]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:47 node-2 haproxy[32262]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:47 node-2 haproxy[32262]: proxy nova-api has no server available!
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:47 node-2 haproxy[32262]: proxy nova-metadata-api has no server available!
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:47 node-2 haproxy[32262]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:48 node-2 haproxy[32266]: proxy glance-api has no server available!
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:48 node-2 haproxy[32266]: proxy glance-glare has no server available!
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:48 node-2 haproxy[32266]: proxy neutron has no server available!
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:48 node-2 haproxy[32266]: proxy glance-registry has no server available!
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:48 node-2 haproxy[32266]: proxy mysqld has no server available!
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:48 node-2 haproxy[32266]: proxy object-storage has no server available!
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:48 node-2 haproxy[32266]: proxy aodh has no server available!
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:48 node-2 haproxy[32266]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:49 node-2 haproxy[32266]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:49 node-2 haproxy[32266]: proxy ceilometer has no server available!
<129>Nov 13 18:03:49 node-2 haproxy[32266]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:49 node-2 haproxy[32266]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:49 node-2 haproxy[32266]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:49 node-2 haproxy[32266]: proxy nova-novncproxy has no server available!
<27>Nov 13 18:03:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:50 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:52 node-2 haproxy[1172]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:52 node-2 haproxy[1172]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:52 node-2 haproxy[1172]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:52 node-2 haproxy[1172]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:52 node-2 haproxy[1172]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:52 node-2 haproxy[1172]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:53 node-2 haproxy[1176]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:53 node-2 haproxy[1176]: proxy nova-api has no server available!
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:53 node-2 haproxy[1176]: proxy nova-metadata-api has no server available!
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:53 node-2 haproxy[1176]: proxy cinder-api has no server available!
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:53 node-2 haproxy[1176]: proxy glance-api has no server available!
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:53 node-2 haproxy[1176]: proxy glance-glare has no server available!
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:53 node-2 haproxy[1176]: proxy neutron has no server available!
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:53 node-2 haproxy[1176]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:54 node-2 haproxy[1176]: proxy glance-registry has no server available!
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:54 node-2 haproxy[1176]: proxy mysqld has no server available!
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:54 node-2 haproxy[1176]: proxy object-storage has no server available!
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:54 node-2 haproxy[1176]: proxy aodh has no server available!
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:54 node-2 haproxy[1176]: proxy ceilometer has no server available!
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:54 node-2 haproxy[1176]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:54 node-2 haproxy[1176]: proxy nova-novncproxy has no server available!
<27>Nov 13 18:03:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:03:55 node-2 multipathd: uevent trigger error
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:58 node-2 haproxy[2564]: proxy keystone-1 has no server available!
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:58 node-2 haproxy[2564]: proxy keystone-2 has no server available!
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:58 node-2 haproxy[2564]: proxy nova-api has no server available!
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:58 node-2 haproxy[2564]: proxy nova-metadata-api has no server available!
<129>Nov 13 18:03:58 node-2 haproxy[2564]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy cinder-api has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy glance-api has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy glance-glare has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy neutron has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy glance-registry has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy mysqld has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy object-storage has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy aodh has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:03:59 node-2 haproxy[2568]: proxy ceilometer has no server available!
<129>Nov 13 18:03:59 node-2 haproxy[2568]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:04:00 node-2 haproxy[2568]: proxy heat-api has no server available!
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:04:00 node-2 haproxy[2568]: proxy heat-api-cfn has no server available!
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:04:00 node-2 haproxy[2568]: proxy heat-api-cloudwatch has no server available!
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov 13 18:04:00 node-2 haproxy[2568]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov 13 18:04:00 node-2 haproxy[2568]: proxy nova-novncproxy has no server available!
<27>Nov 13 18:04:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:04 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:04 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:04:12 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov 13 18:04:32 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:04:36 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Nov 13 18:04:38 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov 13 18:05:06 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 13 18:05:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:05:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:05:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:05:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:05:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:35 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:07:42 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:42 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:42 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:42 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:42 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:48 node-2 multipathd: uevent trigger error
<27>Nov 13 18:07:48 node-2 multipathd: uevent trigger error
<43>Nov 13 18:08:04 node-2 apache2_error [Sun Nov 13 18:07:59.420582 2016] [mpm_event:notice] [pid 10864:tid 139902778644352] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 18:08:04 node-2 apache2_error [Sun Nov 13 18:07:59.420659 2016] [core:notice] [pid 10864:tid 139902778644352] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 18:08:04 node-2 apache2_error [Sun Nov 13 18:08:01.447142 2016] [mpm_event:notice] [pid 10864:tid 139902778644352] AH00491: caught SIGTERM, shutting down
<43>Nov 13 18:08:04 node-2 apache2_error [Sun Nov 13 18:08:02.541423 2016] [mpm_worker:notice] [pid 11396:tid 139679891879808] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov 13 18:08:04 node-2 apache2_error [Sun Nov 13 18:08:02.541453 2016] [core:notice] [pid 11396:tid 139679891879808] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 18:08:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:11 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:08:15 node-2 multipathd: uevent trigger error
<43>Nov 13 18:09:24 node-2 apache2_error [Sun Nov 13 18:09:17.236639 2016] [mpm_worker:notice] [pid 11396:tid 139679891879808] AH00295: caught SIGTERM, shutting down
<43>Nov 13 18:09:24 node-2 apache2_error [Sun Nov 13 18:09:17.988593 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 18:09:24 node-2 apache2_error [Sun Nov 13 18:09:17.988638 2016] [core:notice] [pid 25262:tid 140047019050880] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov 13 18:10:04 node-2 apache2_error [Sun Nov 13 18:10:01.471009 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 18:10:04 node-2 apache2_error [Sun Nov 13 18:10:01.667525 2016] [mpm_worker:warn] [pid 25262:tid 140047019050880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 18:10:04 node-2 apache2_error [Sun Nov 13 18:10:01.672306 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 18:10:04 node-2 apache2_error [Sun Nov 13 18:10:01.672342 2016] [core:notice] [pid 25262:tid 140047019050880] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 18:10:40 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:10:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:10:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:06 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:28 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:33 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:47 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:47 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:47 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:47 node-2 multipathd: uevent trigger error
<27>Nov 13 18:11:47 node-2 multipathd: uevent trigger error
<27>Nov 13 18:12:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:12:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:12:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:12:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:12:38 node-2 multipathd: uevent trigger error
<27>Nov 13 18:13:41 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:13:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:13:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:13:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:13:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:13:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:14:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:15:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:15:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:15:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:15:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:15:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:15:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:16:43 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:17:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:17:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:36 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:18:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:40 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:41 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:41 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:41 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:45 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:19:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Nov 13 18:19:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Nov 13 18:19:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Nov 13 18:19:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Nov 13 18:19:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Nov 13 18:19:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:19:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:03 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:03 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:03 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:03 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:03 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:18 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:18 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:18 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:18 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:20:34 node-2 multipathd: uevent trigger error
<27>Nov 13 18:22:47 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:22:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:22:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:22:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:22:51 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:41 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:41 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:41 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:41 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:53 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:23:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:01 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:07 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:24:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:25:48 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov 13 18:26:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:21 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:21 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:21 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:21 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:21 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:21 node-2 multipathd: uevent trigger error
<11>Nov 13 18:26:33 node-2 liberasurecode[2749]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:33 node-2 liberasurecode[2749]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:33 node-2 liberasurecode[2749]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:33 node-2 liberasurecode[2749]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:33 node-2 liberasurecode[2776]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:33 node-2 liberasurecode[2776]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:33 node-2 liberasurecode[2776]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:33 node-2 liberasurecode[2776]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:35 node-2 liberasurecode[3187]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:35 node-2 liberasurecode[3187]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:35 node-2 liberasurecode[3187]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:35 node-2 liberasurecode[3187]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3776]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3776]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3776]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3776]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3823]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3823]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3867]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3867]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3867]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:39 node-2 liberasurecode[3867]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3927]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3927]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3943]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3955]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3955]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3955]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3955]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3969]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3969]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3969]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:40 node-2 liberasurecode[3969]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:48 node-2 liberasurecode[4486]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:48 node-2 liberasurecode[4486]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:48 node-2 liberasurecode[4486]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:26:48 node-2 liberasurecode[4486]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 18:26:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:57 node-2 multipathd: uevent trigger error
<27>Nov 13 18:26:57 node-2 multipathd: uevent trigger error
<43>Nov 13 18:27:45 node-2 apache2_error [Sun Nov 13 18:27:42.904317 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 18:27:45 node-2 apache2_error [Sun Nov 13 18:27:43.288427 2016] [mpm_worker:warn] [pid 25262:tid 140047019050880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 18:27:45 node-2 apache2_error [Sun Nov 13 18:27:43.291519 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 18:27:45 node-2 apache2_error [Sun Nov 13 18:27:43.291534 2016] [core:notice] [pid 25262:tid 140047019050880] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 18:28:24 node-2 multipathd: uevent trigger error
<27>Nov 13 18:28:24 node-2 multipathd: uevent trigger error
<27>Nov 13 18:28:24 node-2 multipathd: uevent trigger error
<27>Nov 13 18:28:24 node-2 multipathd: uevent trigger error
<43>Nov 13 18:28:26 node-2 apache2_error [Sun Nov 13 18:28:20.052922 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov 13 18:28:26 node-2 apache2_error [Sun Nov 13 18:28:20.251007 2016] [mpm_worker:warn] [pid 25262:tid 140047019050880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 18:28:26 node-2 apache2_error [Sun Nov 13 18:28:20.255126 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 18:28:26 node-2 apache2_error [Sun Nov 13 18:28:20.255149 2016] [core:notice] [pid 25262:tid 140047019050880] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 18:28:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:28:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:28:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:28:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:28:50 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov 13 18:29:06 node-2 apache2_error [Sun Nov 13 18:29:06.051534 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Nov 13 18:29:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:10 node-2 multipathd: uevent trigger error
<43>Nov 13 18:29:16 node-2 apache2_error [Sun Nov 13 18:29:06.245791 2016] [mpm_worker:warn] [pid 25262:tid 140047019050880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov 13 18:29:16 node-2 apache2_error [Sun Nov 13 18:29:06.254083 2016] [mpm_worker:notice] [pid 25262:tid 140047019050880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov 13 18:29:16 node-2 apache2_error [Sun Nov 13 18:29:06.254133 2016] [core:notice] [pid 25262:tid 140047019050880] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov 13 18:29:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:16 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:22 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:31 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:29:45 node-2 multipathd: uevent trigger error
<11>Nov 13 18:30:01 node-2 liberasurecode[11024]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:30:01 node-2 liberasurecode[11024]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:30:01 node-2 liberasurecode[11024]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov 13 18:30:01 node-2 liberasurecode[11024]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov 13 18:30:05 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:11 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov 13 18:30:20 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:20 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:20 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:20 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:25 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:25 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:25 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:25 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:30 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:43 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:43 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:43 node-2 multipathd: uevent trigger error
<27>Nov 13 18:30:43 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:10 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:15 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:27 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:27 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:27 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:27 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:27 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:32 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:32 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:32 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:32 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:32 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:45 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:46 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:50 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:31:55 node-2 multipathd: uevent trigger error
<27>Nov 13 18:32:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:32:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:32:00 node-2 multipathd: uevent trigger error
<27>Nov 13 18:32:00 node-2 multipathd: uevent trigger error
