Oct 19 19:05:49 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8422" x-info="http://www.rsyslog.com"] start
Oct 19 19:05:49 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 19 19:05:49 node-2 rsyslogd: rsyslogd's groupid changed to 104
Oct 19 19:05:49 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct 19 19:05:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 19 19:05:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 19 19:05:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 19 19:05:49 node-2 kernel: [    0.000000] Linux version 3.13.0-98-generic (buildd@lgw01-45) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #145-Ubuntu SMP Sat Oct 8 20:13:07 UTC 2016 (Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39)
Oct 19 19:05:49 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=b18955f7-6356-4729-ae35-20d2bbd51a6e nomdmonddf nomdmonisw
Oct 19 19:05:49 node-2 kernel: [    0.000000] KERNEL supported cpus:
Oct 19 19:05:49 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct 19 19:05:49 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct 19 19:05:49 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct 19 19:05:49 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 19 19:05:49 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 19 19:05:49 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 19 19:05:49 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct 19 19:05:49 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 19 19:05:49 node-2 kernel: [    0.000000] No AGP bridge found
Oct 19 19:05:49 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 19 19:05:49 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct 19 19:05:49 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 19 19:05:49 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct 19 19:05:49 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 19 19:05:49 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 19 19:05:49 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 19 19:05:49 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 19 19:05:49 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 19 19:05:49 node-2 kernel: [    0.000000]   2 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000]   3 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000]   4 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000]   5 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000]   6 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000]   7 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000]   8 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000]   9 disabled
Oct 19 19:05:49 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 19 19:05:49 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 19 19:05:49 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 19 19:05:49 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 19 19:05:49 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 19 19:05:49 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 19 19:05:49 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 19 19:05:49 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 19 19:05:49 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 19 19:05:49 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 19 19:05:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 19 19:05:49 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 19 19:05:49 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 19 19:05:49 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 19 19:05:49 node-2 kernel: [    0.000000] Zone ranges:
Oct 19 19:05:49 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] Movable zone start for each node
Oct 19 19:05:49 node-2 kernel: [    0.000000] Early memory node ranges
Oct 19 19:05:49 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 19 19:05:49 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 19 19:05:49 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 19 19:05:49 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 19 19:05:49 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 19 19:05:49 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 19 19:05:49 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 19 19:05:49 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 19 19:05:49 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 19 19:05:49 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 19 19:05:49 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 19 19:05:49 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 19 19:05:49 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 19 19:05:49 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 19 19:05:49 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 19 19:05:49 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 19 19:05:49 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 19 19:05:49 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 19 19:05:49 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 19 19:05:49 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 19 19:05:49 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 19 19:05:49 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 19 19:05:49 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 19 19:05:49 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 19 19:05:49 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct 19 19:05:49 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 19 19:05:49 node-2 kernel: [    0.000000] Policy zone: Normal
Oct 19 19:05:49 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=b18955f7-6356-4729-ae35-20d2bbd51a6e nomdmonddf nomdmonisw
Oct 19 19:05:49 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 19 19:05:49 node-2 kernel: [    0.000000] Checking aperture...
Oct 19 19:05:49 node-2 kernel: [    0.000000] No AGP bridge found
Oct 19 19:05:49 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 19 19:05:49 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 19 19:05:49 node-2 kernel: [    0.000000] Memory: 32653320K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct 19 19:05:49 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 19 19:05:49 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 19 19:05:49 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 19 19:05:49 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 19 19:05:49 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 19 19:05:49 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 19 19:05:49 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 19 19:05:49 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 19 19:05:49 node-2 kernel: [    0.000000] console [tty0] enabled
Oct 19 19:05:49 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 19 19:05:49 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 19 19:05:49 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 19 19:05:49 node-2 kernel: [    0.000000] hpet clockevent registered
Oct 19 19:05:49 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 19 19:05:49 node-2 kernel: [    0.004000] tsc: Detected 3492.015 MHz processor
Oct 19 19:05:49 node-2 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.03 BogoMIPS (lpj=13968060)
Oct 19 19:05:49 node-2 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 19 19:05:49 node-2 kernel: [    0.000043] Security Framework initialized
Oct 19 19:05:49 node-2 kernel: [    0.000061] AppArmor: AppArmor initialized
Oct 19 19:05:49 node-2 kernel: [    0.000062] Yama: becoming mindful.
Oct 19 19:05:49 node-2 kernel: [    0.001467] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.006315] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.008245] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.008273] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.008559] Initializing cgroup subsys memory
Oct 19 19:05:49 node-2 kernel: [    0.008568] Initializing cgroup subsys devices
Oct 19 19:05:49 node-2 kernel: [    0.008570] Initializing cgroup subsys freezer
Oct 19 19:05:49 node-2 kernel: [    0.008571] Initializing cgroup subsys blkio
Oct 19 19:05:49 node-2 kernel: [    0.008573] Initializing cgroup subsys perf_event
Oct 19 19:05:49 node-2 kernel: [    0.008575] Initializing cgroup subsys hugetlb
Oct 19 19:05:49 node-2 kernel: [    0.008595] CPU: Physical Processor ID: 0
Oct 19 19:05:49 node-2 kernel: [    0.008596] CPU: Processor Core ID: 0
Oct 19 19:05:49 node-2 kernel: [    0.008600] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 19 19:05:49 node-2 kernel: [    0.008600] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 19 19:05:49 node-2 kernel: [    0.009294] mce: CPU supports 22 MCE banks
Oct 19 19:05:49 node-2 kernel: [    0.009321] CPU0: Thermal monitoring enabled (TM1)
Oct 19 19:05:49 node-2 kernel: [    0.009342] process: using mwait in idle threads
Oct 19 19:05:49 node-2 kernel: [    0.009345] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 19 19:05:49 node-2 kernel: [    0.009345] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 19 19:05:49 node-2 kernel: [    0.009345] tlb_flushall_shift: 6
Oct 19 19:05:49 node-2 kernel: [    0.009432] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 19 19:05:49 node-2 kernel: [    0.010157] ACPI: Core revision 20131115
Oct 19 19:05:49 node-2 kernel: [    0.022964] ACPI: All ACPI Tables successfully acquired
Oct 19 19:05:49 node-2 kernel: [    0.023124] ftrace: allocating 28622 entries in 112 pages
Oct 19 19:05:49 node-2 kernel: [    0.031884] dmar: Host address width 46
Oct 19 19:05:49 node-2 kernel: [    0.031886] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 19 19:05:49 node-2 kernel: [    0.031892] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 19 19:05:49 node-2 kernel: [    0.031894] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 19 19:05:49 node-2 kernel: [    0.031898] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 19 19:05:49 node-2 kernel: [    0.031900] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 19 19:05:49 node-2 kernel: [    0.031901] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 19 19:05:49 node-2 kernel: [    0.031902] dmar: ATSR flags: 0x0
Oct 19 19:05:49 node-2 kernel: [    0.031903] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 19 19:05:49 node-2 kernel: [    0.031904] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 19 19:05:49 node-2 kernel: [    0.032019] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 19 19:05:49 node-2 kernel: [    0.032020] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 19 19:05:49 node-2 kernel: [    0.032021] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 19 19:05:49 node-2 kernel: [    0.032022] HPET id 0 under DRHD base 0xc7ffc000
Oct 19 19:05:49 node-2 kernel: [    0.032024] Your BIOS is broken and requested that x2apic be disabled.
Oct 19 19:05:49 node-2 kernel: [    0.032024] This will slightly decrease performance.
Oct 19 19:05:49 node-2 kernel: [    0.032024] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 19 19:05:49 node-2 kernel: [    0.032455] Enabled IRQ remapping in xapic mode
Oct 19 19:05:49 node-2 kernel: [    0.032457] x2apic not enabled, IRQ remapping is in xapic mode
Oct 19 19:05:49 node-2 kernel: [    0.032460] Switched APIC routing to physical flat.
Oct 19 19:05:49 node-2 kernel: [    0.033079] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 19 19:05:49 node-2 kernel: [    0.072729] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 19 19:05:49 node-2 kernel: [    0.072735] TSC deadline timer enabled
Oct 19 19:05:49 node-2 kernel: [    0.072742] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 19 19:05:49 node-2 kernel: [    0.072748] ... version:                3
Oct 19 19:05:49 node-2 kernel: [    0.072749] ... bit width:              48
Oct 19 19:05:49 node-2 kernel: [    0.072750] ... generic registers:      4
Oct 19 19:05:49 node-2 kernel: [    0.072751] ... value mask:             0000ffffffffffff
Oct 19 19:05:49 node-2 kernel: [    0.072752] ... max period:             0000ffffffffffff
Oct 19 19:05:49 node-2 kernel: [    0.072753] ... fixed-purpose events:   3
Oct 19 19:05:49 node-2 kernel: [    0.072754] ... event mask:             000000070000000f
Oct 19 19:05:49 node-2 kernel: [    0.074188] x86: Booting SMP configuration:
Oct 19 19:05:49 node-2 kernel: [    0.088293] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 19 19:05:49 node-2 kernel: [    0.074190] .... node  #0, CPUs:        #1  #2  #3
Oct 19 19:05:49 node-2 kernel: [    0.116200] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 19 19:05:49 node-2 kernel: [    0.270380] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 19 19:05:49 node-2 kernel: [    0.326006] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 19 19:05:49 node-2 kernel: [    0.383065] x86: Booted up 2 nodes, 16 CPUs
Oct 19 19:05:49 node-2 kernel: [    0.383068] smpboot: Total of 16 processors activated (111756.82 BogoMIPS)
Oct 19 19:05:49 node-2 kernel: [    0.407901] devtmpfs: initialized
Oct 19 19:05:49 node-2 kernel: [    0.410361] EVM: security.selinux
Oct 19 19:05:49 node-2 kernel: [    0.410362] EVM: security.SMACK64
Oct 19 19:05:49 node-2 kernel: [    0.410363] EVM: security.ima
Oct 19 19:05:49 node-2 kernel: [    0.410364] EVM: security.capability
Oct 19 19:05:49 node-2 kernel: [    0.410413] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.411066] pinctrl core: initialized pinctrl subsystem
Oct 19 19:05:49 node-2 kernel: [    0.411126] regulator-dummy: no parameters
Oct 19 19:05:49 node-2 kernel: [    0.411158] RTC time: 19:05:13, date: 10/19/16
Oct 19 19:05:49 node-2 kernel: [    0.411191] NET: Registered protocol family 16
Oct 19 19:05:49 node-2 kernel: [    0.411275] cpuidle: using governor ladder
Oct 19 19:05:49 node-2 kernel: [    0.411276] cpuidle: using governor menu
Oct 19 19:05:49 node-2 kernel: [    0.411310] ACPI: bus type PCI registered
Oct 19 19:05:49 node-2 kernel: [    0.411313] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 19 19:05:49 node-2 kernel: [    0.411356] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 19 19:05:49 node-2 kernel: [    0.411359] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 19 19:05:49 node-2 kernel: [    0.425123] PCI: Using configuration type 1 for base access
Oct 19 19:05:49 node-2 kernel: [    0.426108] bio: create slab <bio-0> at 0
Oct 19 19:05:49 node-2 kernel: [    0.426378] ACPI: Added _OSI(Module Device)
Oct 19 19:05:49 node-2 kernel: [    0.426380] ACPI: Added _OSI(Processor Device)
Oct 19 19:05:49 node-2 kernel: [    0.426381] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 19 19:05:49 node-2 kernel: [    0.426382] ACPI: Added _OSI(Processor Aggregator Device)
Oct 19 19:05:49 node-2 kernel: [    0.439136] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 19 19:05:49 node-2 kernel: [    0.449863] ACPI: Interpreter enabled
Oct 19 19:05:49 node-2 kernel: [    0.449868] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 19 19:05:49 node-2 kernel: [    0.449872] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 19 19:05:49 node-2 kernel: [    0.449875] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 19 19:05:49 node-2 kernel: [    0.449882] ACPI: (supports S0 S4 S5)
Oct 19 19:05:49 node-2 kernel: [    0.449883] ACPI: Using IOAPIC for interrupt routing
Oct 19 19:05:49 node-2 kernel: [    0.449924] HEST: Table parsing has been initialized.
Oct 19 19:05:49 node-2 kernel: [    0.449927] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 19 19:05:49 node-2 kernel: [    0.450482] ACPI: No dock devices found.
Oct 19 19:05:49 node-2 kernel: [    0.462067] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 19 19:05:49 node-2 kernel: [    0.462072] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 19:05:49 node-2 kernel: [    0.462075] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 19 19:05:49 node-2 kernel: [    0.462104] PCI host bridge to bus 0000:ff
Oct 19 19:05:49 node-2 kernel: [    0.462106] pci_bus 0000:ff: root bus resource [bus ff]
Oct 19 19:05:49 node-2 kernel: [    0.462114] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462153] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.462183] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462218] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462248] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.462278] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.462309] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462338] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462369] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462397] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462424] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462450] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462481] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462507] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462533] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462560] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462588] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462616] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462642] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.462671] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462696] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.462722] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462748] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462778] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.462813] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462844] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462874] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462905] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462936] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462967] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.462997] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463028] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463058] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463090] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463122] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463155] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463188] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463218] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463246] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463280] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463312] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463350] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463385] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463418] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463448] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463476] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463506] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463534] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463566] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463597] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463629] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463658] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463687] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463715] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463745] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463775] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463806] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463863] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 19 19:05:49 node-2 kernel: [    0.463866] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 19:05:49 node-2 kernel: [    0.463869] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 19 19:05:49 node-2 kernel: [    0.463887] PCI host bridge to bus 0000:7f
Oct 19 19:05:49 node-2 kernel: [    0.463888] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 19 19:05:49 node-2 kernel: [    0.463893] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463924] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.463953] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.463982] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464004] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.464028] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.464054] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464079] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464102] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464124] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464146] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464169] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464192] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464214] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464239] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464264] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464285] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464308] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464330] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.464354] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464376] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.464398] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464420] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464446] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 19 19:05:49 node-2 kernel: [    0.464478] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464504] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464530] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464556] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464581] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464608] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464635] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464664] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464688] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464714] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464740] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464767] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464796] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464821] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464845] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464873] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464898] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464924] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464952] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.464978] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465002] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465026] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465052] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465079] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465105] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465131] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465158] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465183] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465205] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465230] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465256] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465284] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.465310] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.466566] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 19 19:05:49 node-2 kernel: [    0.466570] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 19:05:49 node-2 kernel: [    0.467691] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 19 19:05:49 node-2 kernel: [    0.468205] PCI host bridge to bus 0000:00
Oct 19 19:05:49 node-2 kernel: [    0.468208] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 19 19:05:49 node-2 kernel: [    0.468210] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 19 19:05:49 node-2 kernel: [    0.468211] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 19 19:05:49 node-2 kernel: [    0.468212] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 19 19:05:49 node-2 kernel: [    0.468214] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 19 19:05:49 node-2 kernel: [    0.468215] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 19 19:05:49 node-2 kernel: [    0.468217] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 19 19:05:49 node-2 kernel: [    0.468222] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 19 19:05:49 node-2 kernel: [    0.468305] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.468336] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.468377] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 19 19:05:49 node-2 kernel: [    0.468397] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.468427] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.468467] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 19 19:05:49 node-2 kernel: [    0.468488] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.468518] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.468561] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 19 19:05:49 node-2 kernel: [    0.468579] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.468650] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.468727] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.468801] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 19 19:05:49 node-2 kernel: [    0.468806] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 19 19:05:49 node-2 kernel: [    0.468891] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 19 19:05:49 node-2 kernel: [    0.469040] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 19 19:05:49 node-2 kernel: [    0.469058] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 19 19:05:49 node-2 kernel: [    0.469136] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.469191] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 19 19:05:49 node-2 kernel: [    0.469212] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.469268] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.469311] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 19 19:05:49 node-2 kernel: [    0.469338] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.469394] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.469437] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 19 19:05:49 node-2 kernel: [    0.469461] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 19 19:05:49 node-2 kernel: [    0.469479] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 19 19:05:49 node-2 kernel: [    0.469556] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.469606] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 19 19:05:49 node-2 kernel: [    0.469632] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 19 19:05:49 node-2 kernel: [    0.469879] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 19 19:05:49 node-2 kernel: [    0.469884] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 19 19:05:49 node-2 kernel: [    0.469891] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.469896] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.469904] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 19 19:05:49 node-2 kernel: [    0.469934] pci 0000:01:00.0: supports D1 D2
Oct 19 19:05:49 node-2 kernel: [    0.475932] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 19 19:05:49 node-2 kernel: [    0.475938] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 19 19:05:49 node-2 kernel: [    0.475942] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 19 19:05:49 node-2 kernel: [    0.476134] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.476167] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 19 19:05:49 node-2 kernel: [    0.483930] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 19 19:05:49 node-2 kernel: [    0.483936] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.483940] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 19:05:49 node-2 kernel: [    0.484024] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.484108] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.484185] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.484232] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 19 19:05:49 node-2 kernel: [    0.484235] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.484237] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 19:05:49 node-2 kernel: [    0.484289] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.484411] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.484483] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 19 19:05:49 node-2 kernel: [    0.484486] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.484488] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.484537] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.484656] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.484697] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.484817] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.484855] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.484974] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.485011] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 19 19:05:49 node-2 kernel: [    0.485131] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 19 19:05:49 node-2 kernel: [    0.485173] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 19 19:05:49 node-2 kernel: [    0.485176] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.485178] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.485236] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 19 19:05:49 node-2 kernel: [    0.485299] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.485351] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.485392] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 19 19:05:49 node-2 kernel: [    0.485508] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 19 19:05:49 node-2 kernel: [    0.485624] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 19 19:05:49 node-2 kernel: [    0.485626] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.485628] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.485687] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 19 19:05:49 node-2 kernel: [    0.485748] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.485795] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.486012] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 19 19:05:49 node-2 kernel: [    0.486015] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 19 19:05:49 node-2 kernel: [    0.486085] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 19 19:05:49 node-2 kernel: [    0.486142] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.486190] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.486409] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 19 19:05:49 node-2 kernel: [    0.486412] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 19 19:05:49 node-2 kernel: [    0.486503] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 19 19:05:49 node-2 kernel: [    0.486568] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.486621] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 19 19:05:49 node-2 kernel: [    0.486843] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 19 19:05:49 node-2 kernel: [    0.486847] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 19 19:05:49 node-2 kernel: [    0.487021] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 19 19:05:49 node-2 kernel: [    0.487059] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 19 19:05:49 node-2 kernel: [    0.487134] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 19 19:05:49 node-2 kernel: [    0.487153] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 19 19:05:49 node-2 kernel: [    0.487166] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 19 19:05:49 node-2 kernel: [    0.487179] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 19 19:05:49 node-2 kernel: [    0.487230] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 19 19:05:49 node-2 kernel: [    0.491936] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 19 19:05:49 node-2 kernel: [    0.491945] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 19 19:05:49 node-2 kernel: [    0.491997] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 19 19:05:49 node-2 kernel: [    0.492550] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 19 19:05:49 node-2 kernel: [    0.492553] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 19 19:05:49 node-2 kernel: [    0.492677] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 19 19:05:49 node-2 kernel: [    0.492782] PCI host bridge to bus 0000:80
Oct 19 19:05:49 node-2 kernel: [    0.492784] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 19 19:05:49 node-2 kernel: [    0.492785] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 19 19:05:49 node-2 kernel: [    0.492787] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 19 19:05:49 node-2 kernel: [    0.492795] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.492857] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.492925] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 19 19:05:49 node-2 kernel: [    0.492986] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 19 19:05:49 node-2 kernel: [    0.492992] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 19 19:05:49 node-2 kernel: [    0.493064] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 19 19:05:49 node-2 kernel: [    0.493362] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 19 19:05:49 node-2 kernel: [    0.493393] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 19 19:05:49 node-2 kernel: [    0.493423] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 19 19:05:49 node-2 kernel: [    0.493452] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 19 19:05:49 node-2 kernel: [    0.493481] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 19:05:49 node-2 kernel: [    0.493511] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 19:05:49 node-2 kernel: [    0.493541] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 19:05:49 node-2 kernel: [    0.493570] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 19 19:05:49 node-2 kernel: [    0.493655] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 19 19:05:49 node-2 kernel: [    0.493659] ACPI: \_SB_.UNC1: notify handler is installed
Oct 19 19:05:49 node-2 kernel: [    0.493660] ACPI: \_SB_.UNC0: notify handler is installed
Oct 19 19:05:49 node-2 kernel: [    0.493675] ACPI: \_SB_.PCI0: notify handler is installed
Oct 19 19:05:49 node-2 kernel: [    0.493728] ACPI: \_SB_.PCI1: notify handler is installed
Oct 19 19:05:49 node-2 kernel: [    0.493807] Found 4 acpi root devices
Oct 19 19:05:49 node-2 kernel: [    0.493913] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 19 19:05:49 node-2 kernel: [    0.493915] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 19 19:05:49 node-2 kernel: [    0.493917] vgaarb: loaded
Oct 19 19:05:49 node-2 kernel: [    0.493918] vgaarb: bridge control possible 0000:0c:00.0
Oct 19 19:05:49 node-2 kernel: [    0.494038] SCSI subsystem initialized
Oct 19 19:05:49 node-2 kernel: [    0.494103] libata version 3.00 loaded.
Oct 19 19:05:49 node-2 kernel: [    0.494119] ACPI: bus type USB registered
Oct 19 19:05:49 node-2 kernel: [    0.494129] usbcore: registered new interface driver usbfs
Oct 19 19:05:49 node-2 kernel: [    0.494134] usbcore: registered new interface driver hub
Oct 19 19:05:49 node-2 kernel: [    0.494158] usbcore: registered new device driver usb
Oct 19 19:05:49 node-2 kernel: [    0.494321] PCI: Using ACPI for IRQ routing
Oct 19 19:05:49 node-2 kernel: [    0.497914] PCI: pci_cache_line_size set to 64 bytes
Oct 19 19:05:49 node-2 kernel: [    0.498120] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 19 19:05:49 node-2 kernel: [    0.498121] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 19 19:05:49 node-2 kernel: [    0.498122] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 19 19:05:49 node-2 kernel: [    0.498186] NetLabel: Initializing
Oct 19 19:05:49 node-2 kernel: [    0.498187] NetLabel:  domain hash size = 128
Oct 19 19:05:49 node-2 kernel: [    0.498188] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 19 19:05:49 node-2 kernel: [    0.498198] NetLabel:  unlabeled traffic allowed by default
Oct 19 19:05:49 node-2 kernel: [    0.498254] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 19 19:05:49 node-2 kernel: [    0.498258] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 19 19:05:49 node-2 kernel: [    0.500318] Switched to clocksource hpet
Oct 19 19:05:49 node-2 kernel: [    0.504321] AppArmor: AppArmor Filesystem Enabled
Oct 19 19:05:49 node-2 kernel: [    0.504335] pnp: PnP ACPI init
Oct 19 19:05:49 node-2 kernel: [    0.504342] ACPI: bus type PNP registered
Oct 19 19:05:49 node-2 kernel: [    0.504451] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504459] pnp 00:01: [dma 4]
Oct 19 19:05:49 node-2 kernel: [    0.504471] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504498] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504517] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504536] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504569] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504622] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504624] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 19 19:05:49 node-2 kernel: [    0.504626] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504627] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504629] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504633] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504636] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 19 19:05:49 node-2 kernel: [    0.504637] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504639] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504640] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504642] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504643] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504644] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 19 19:05:49 node-2 kernel: [    0.504646] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504730] pnp 00:07: [dma 0 disabled]
Oct 19 19:05:49 node-2 kernel: [    0.504758] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504833] pnp 00:08: [dma 0 disabled]
Oct 19 19:05:49 node-2 kernel: [    0.504865] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 19 19:05:49 node-2 kernel: [    0.504916] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 19 19:05:49 node-2 kernel: [    0.505260] pnp: PnP ACPI: found 10 devices
Oct 19 19:05:49 node-2 kernel: [    0.505262] ACPI: bus type PNP unregistered
Oct 19 19:05:49 node-2 kernel: [    0.511560] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 19 19:05:49 node-2 kernel: [    0.511563] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 19 19:05:49 node-2 kernel: [    0.511565] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 19 19:05:49 node-2 kernel: [    0.511570] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 19 19:05:49 node-2 kernel: [    0.511571] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511586] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511615] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 19 19:05:49 node-2 kernel: [    0.511630] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511659] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 19 19:05:49 node-2 kernel: [    0.511673] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 19 19:05:49 node-2 kernel: [    0.511702] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 19 19:05:49 node-2 kernel: [    0.511716] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 19 19:05:49 node-2 kernel: [    0.511745] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 19 19:05:49 node-2 kernel: [    0.511747] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511761] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511790] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 19 19:05:49 node-2 kernel: [    0.511792] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511806] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511837] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 19 19:05:49 node-2 kernel: [    0.511839] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511842] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511846] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 19 19:05:49 node-2 kernel: [    0.511847] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511850] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511853] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 19 19:05:49 node-2 kernel: [    0.511858] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 19 19:05:49 node-2 kernel: [    0.511866] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 19 19:05:49 node-2 kernel: [    0.511870] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 19 19:05:49 node-2 kernel: [    0.511876] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 19 19:05:49 node-2 kernel: [    0.511877] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 19 19:05:49 node-2 kernel: [    0.511878] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 19 19:05:49 node-2 kernel: [    0.511878] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 19 19:05:49 node-2 kernel: [    0.511879] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 19 19:05:49 node-2 kernel: [    0.511880] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 19 19:05:49 node-2 kernel: [    0.511881] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 19 19:05:49 node-2 kernel: [    0.511882] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 19 19:05:49 node-2 kernel: [    0.511883] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511884] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511885] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511885] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511886] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511887] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511888] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511889] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511890] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 19 19:05:49 node-2 kernel: [    0.511891] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511892] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 19 19:05:49 node-2 kernel: [    0.511893] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 19 19:05:49 node-2 kernel: [    0.511894] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 19 19:05:49 node-2 kernel: [    0.511895] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 19 19:05:49 node-2 kernel: [    0.511897] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 19 19:05:49 node-2 kernel: [    0.511898] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 19 19:05:49 node-2 kernel: [    0.511936] NET: Registered protocol family 2
Oct 19 19:05:49 node-2 kernel: [    0.512187] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.512523] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.512667] TCP: Hash tables configured (established 262144 bind 65536)
Oct 19 19:05:49 node-2 kernel: [    0.512710] TCP: reno registered
Oct 19 19:05:49 node-2 kernel: [    0.512739] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.512832] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.512977] NET: Registered protocol family 1
Oct 19 19:05:49 node-2 kernel: [    0.552409] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 19 19:05:49 node-2 kernel: [    0.552423] PCI: CLS 64 bytes, default 64
Oct 19 19:05:49 node-2 kernel: [    0.552499] Trying to unpack rootfs image as initramfs...
Oct 19 19:05:49 node-2 kernel: [    0.771766] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct 19 19:05:49 node-2 kernel: [    0.771802] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 19 19:05:49 node-2 kernel: [    0.771804] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 19 19:05:49 node-2 kernel: [    0.772213] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772219] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772224] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772229] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772254] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772265] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772273] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772282] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772290] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772299] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772305] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772311] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772318] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772325] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772333] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772340] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 19 19:05:49 node-2 kernel: [    0.772417] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 19 19:05:49 node-2 kernel: [    0.772420] Scanning for low memory corruption every 60 seconds
Oct 19 19:05:49 node-2 kernel: [    0.772793] Initialise system trusted keyring
Oct 19 19:05:49 node-2 kernel: [    0.772847] audit: initializing netlink socket (disabled)
Oct 19 19:05:49 node-2 kernel: [    0.772863] type=2000 audit(1476903912.724:1): initialized
Oct 19 19:05:49 node-2 kernel: [    0.790624] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 19 19:05:49 node-2 kernel: [    0.792156] zbud: loaded
Oct 19 19:05:49 node-2 kernel: [    0.792281] VFS: Disk quotas dquot_6.5.2
Oct 19 19:05:49 node-2 kernel: [    0.792318] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 19 19:05:49 node-2 kernel: [    0.792687] fuse init (API version 7.22)
Oct 19 19:05:49 node-2 kernel: [    0.792749] msgmni has been set to 32768
Oct 19 19:05:49 node-2 kernel: [    0.792799] Key type big_key registered
Oct 19 19:05:49 node-2 kernel: [    0.793313] Key type asymmetric registered
Oct 19 19:05:49 node-2 kernel: [    0.793315] Asymmetric key parser 'x509' registered
Oct 19 19:05:49 node-2 kernel: [    0.793339] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 19 19:05:49 node-2 kernel: [    0.793407] io scheduler noop registered
Oct 19 19:05:49 node-2 kernel: [    0.793409] io scheduler deadline registered (default)
Oct 19 19:05:49 node-2 kernel: [    0.793430] io scheduler cfq registered
Oct 19 19:05:49 node-2 kernel: [    0.793937] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    0.794101] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    0.794220] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    0.794331] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    0.794446] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    0.794543] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    0.794939] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 19 19:05:49 node-2 kernel: [    0.794965] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 19 19:05:49 node-2 kernel: [    0.794981] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 19 19:05:49 node-2 kernel: [    0.794990] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.794993] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.794996] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 19 19:05:49 node-2 kernel: [    0.795001] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795002] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795004] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795005] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795007] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795008] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795010] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795011] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795012] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795014] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795015] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795017] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795019] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 19 19:05:49 node-2 kernel: [    0.795024] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795026] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 19 19:05:49 node-2 kernel: [    0.795041] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795045] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 19 19:05:49 node-2 kernel: [    0.795056] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795058] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 19 19:05:49 node-2 kernel: [    0.795060] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 19 19:05:49 node-2 kernel: [    0.795115] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 19 19:05:49 node-2 kernel: [    0.795121] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 19 19:05:49 node-2 kernel: [    0.795125] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 19 19:05:49 node-2 kernel: [    0.795135] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 19 19:05:49 node-2 kernel: [    0.795174] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 19 19:05:49 node-2 kernel: [    0.795175] vesafb: scrolling: redraw
Oct 19 19:05:49 node-2 kernel: [    0.795177] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 19 19:05:49 node-2 kernel: [    0.815962] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 19 19:05:49 node-2 kernel: [    0.824587] Console: switching to colour frame buffer device 80x30
Oct 19 19:05:49 node-2 kernel: [    0.833250] fb0: VESA VGA frame buffer device
Oct 19 19:05:49 node-2 kernel: [    0.833446] intel_idle: MWAIT substates: 0x2120
Oct 19 19:05:49 node-2 kernel: [    0.833447] intel_idle: v0.4 model 0x3F
Oct 19 19:05:49 node-2 kernel: [    0.833447] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 19 19:05:49 node-2 kernel: [    0.833673] ipmi message handler version 39.2
Oct 19 19:05:49 node-2 kernel: [    0.833949] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 19 19:05:49 node-2 kernel: [    0.834383] ACPI: AC Adapter [P111] (on-line)
Oct 19 19:05:49 node-2 kernel: [    0.839606] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 19 19:05:49 node-2 kernel: [    0.850601] ACPI: Power Button [PWRB]
Oct 19 19:05:49 node-2 kernel: [    0.856359] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 19 19:05:49 node-2 kernel: [    0.867982] ACPI: Power Button [PWRF]
Oct 19 19:05:49 node-2 kernel: [    0.885799] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 19 19:05:49 node-2 kernel: [    0.897415] pstore: Registered erst as persistent store backend
Oct 19 19:05:49 node-2 kernel: [    0.903626] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 19 19:05:49 node-2 kernel: [    0.915575] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 19 19:05:49 node-2 kernel: [    0.942317] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 19 19:05:49 node-2 kernel: [    0.975579] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 19 19:05:49 node-2 kernel: [    0.989779] Linux agpgart interface v0.103
Oct 19 19:05:49 node-2 kernel: [    0.997471] brd: module loaded
Oct 19 19:05:49 node-2 kernel: [    1.004591] loop: module loaded
Oct 19 19:05:49 node-2 kernel: [    1.011423] libphy: Fixed MDIO Bus: probed
Oct 19 19:05:49 node-2 kernel: [    1.018007] tun: Universal TUN/TAP device driver, 1.6
Oct 19 19:05:49 node-2 kernel: [    1.024571] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 19 19:05:49 node-2 kernel: [    1.031158] PPP generic driver version 2.4.2
Oct 19 19:05:49 node-2 kernel: [    1.037656] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 19 19:05:49 node-2 kernel: [    1.044157] ehci-pci: EHCI PCI platform driver
Oct 19 19:05:49 node-2 kernel: [    1.050681] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 19 19:05:49 node-2 kernel: [    1.057086] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 19 19:05:49 node-2 kernel: [    1.069623] ehci-pci 0000:00:1a.0: debug port 2
Oct 19 19:05:49 node-2 kernel: [    1.079826] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 19 19:05:49 node-2 kernel: [    1.079845] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 19 19:05:49 node-2 kernel: [    1.095813] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 19 19:05:49 node-2 kernel: [    1.101889] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 19 19:05:49 node-2 kernel: [    1.108067] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 19 19:05:49 node-2 kernel: [    1.119985] usb usb1: Product: EHCI Host Controller
Oct 19 19:05:49 node-2 kernel: [    1.126007] usb usb1: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 19 19:05:49 node-2 kernel: [    1.132054] usb usb1: SerialNumber: 0000:00:1a.0
Oct 19 19:05:49 node-2 kernel: [    1.137996] hub 1-0:1.0: USB hub found
Oct 19 19:05:49 node-2 kernel: [    1.143766] hub 1-0:1.0: 2 ports detected
Oct 19 19:05:49 node-2 kernel: [    1.149546] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 19 19:05:49 node-2 kernel: [    1.155115] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 19 19:05:49 node-2 kernel: [    1.165991] ehci-pci 0000:00:1d.0: debug port 2
Oct 19 19:05:49 node-2 kernel: [    1.175292] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 19 19:05:49 node-2 kernel: [    1.175295] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 19 19:05:49 node-2 kernel: [    1.191732] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 19 19:05:49 node-2 kernel: [    1.196919] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 19 19:05:49 node-2 kernel: [    1.202200] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 19 19:05:49 node-2 kernel: [    1.212760] usb usb2: Product: EHCI Host Controller
Oct 19 19:05:49 node-2 kernel: [    1.218226] usb usb2: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 19 19:05:49 node-2 kernel: [    1.223767] usb usb2: SerialNumber: 0000:00:1d.0
Oct 19 19:05:49 node-2 kernel: [    1.229274] hub 2-0:1.0: USB hub found
Oct 19 19:05:49 node-2 kernel: [    1.234611] hub 2-0:1.0: 2 ports detected
Oct 19 19:05:49 node-2 kernel: [    1.239911] ehci-platform: EHCI generic platform driver
Oct 19 19:05:49 node-2 kernel: [    1.245127] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 19 19:05:49 node-2 kernel: [    1.250424] ohci-pci: OHCI PCI platform driver
Oct 19 19:05:49 node-2 kernel: [    1.255712] ohci-platform: OHCI generic platform driver
Oct 19 19:05:49 node-2 kernel: [    1.260899] uhci_hcd: USB Universal Host Controller Interface driver
Oct 19 19:05:49 node-2 kernel: [    1.266241] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 19 19:05:49 node-2 kernel: [    1.459512] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 19 19:05:49 node-2 kernel: [    1.767281] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 19 19:05:49 node-2 kernel: [    1.783618] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 19 19:05:49 node-2 kernel: [    1.789227] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 19 19:05:49 node-2 kernel: [    1.795010] hub 1-1:1.0: USB hub found
Oct 19 19:05:49 node-2 kernel: [    1.800603] hub 1-1:1.0: 6 ports detected
Oct 19 19:05:49 node-2 kernel: [    1.915144] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 19 19:05:49 node-2 kernel: [    2.305036] i8042: No controller found
Oct 19 19:05:49 node-2 kernel: [    2.310561] mousedev: PS/2 mouse device common for all mice
Oct 19 19:05:49 node-2 kernel: [    2.316288] rtc_cmos 00:02: RTC can wake from S4
Oct 19 19:05:49 node-2 kernel: [    2.319610] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 19 19:05:49 node-2 kernel: [    2.319611] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 19 19:05:49 node-2 kernel: [    2.320128] hub 2-1:1.0: USB hub found
Oct 19 19:05:49 node-2 kernel: [    2.320359] hub 2-1:1.0: 8 ports detected
Oct 19 19:05:49 node-2 kernel: [    2.344635] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 19 19:05:49 node-2 kernel: [    2.350399] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 19 19:05:49 node-2 kernel: [    2.361753] device-mapper: uevent: version 1.0.3
Oct 19 19:05:49 node-2 kernel: [    2.367469] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 19 19:05:49 node-2 kernel: [    2.378876] ledtrig-cpu: registered to indicate activity on CPUs
Oct 19 19:05:49 node-2 kernel: [    2.384863] TCP: cubic registered
Oct 19 19:05:49 node-2 kernel: [    2.390750] NET: Registered protocol family 10
Oct 19 19:05:49 node-2 kernel: [    2.396798] NET: Registered protocol family 17
Oct 19 19:05:49 node-2 kernel: [    2.402591] Key type dns_resolver registered
Oct 19 19:05:49 node-2 kernel: [    2.408679] Loading compiled-in X.509 certificates
Oct 19 19:05:49 node-2 kernel: [    2.414916] Loaded X.509 cert 'Magrathea: Glacier signing key: c29c39823a6b07000b1e1e4c1cabc3708bc09796'
Oct 19 19:05:49 node-2 kernel: [    2.426587] registered taskstats version 1
Oct 19 19:05:49 node-2 kernel: [    2.434630] Key type trusted registered
Oct 19 19:05:49 node-2 kernel: [    2.442260] Key type encrypted registered
Oct 19 19:05:49 node-2 kernel: [    2.447774] AppArmor: AppArmor sha1 policy hashing enabled
Oct 19 19:05:49 node-2 kernel: [    2.453294] IMA: No TPM chip found, activating TPM-bypass!
Oct 19 19:05:49 node-2 kernel: [    2.459398] regulator-dummy: disabling
Oct 19 19:05:49 node-2 kernel: [    2.464879]   Magic number: 4:980:91
Oct 19 19:05:49 node-2 kernel: [    2.470512] memory memory244: hash matches
Oct 19 19:05:49 node-2 kernel: [    2.476026] rtc_cmos 00:02: setting system clock to 2016-10-19 19:05:15 UTC (1476903915)
Oct 19 19:05:49 node-2 kernel: [    2.488439] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 19 19:05:49 node-2 kernel: [    2.494064] EDD information not available.
Oct 19 19:05:49 node-2 kernel: [    2.499610] PM: Hibernation image not present or could not be loaded.
Oct 19 19:05:49 node-2 kernel: [    2.500470] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 19 19:05:49 node-2 kernel: [    2.511741] Write protecting the kernel read-only data: 12288k
Oct 19 19:05:49 node-2 kernel: [    2.518126] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 19 19:05:49 node-2 kernel: [    2.530952] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 19 19:05:49 node-2 kernel: [    2.562572] device-mapper: multipath: version 1.6.0 loaded
Oct 19 19:05:49 node-2 kernel: [    2.570367] systemd-udevd[218]: starting version 204
Oct 19 19:05:49 node-2 kernel: [    2.594888] md: linear personality registered for level -1
Oct 19 19:05:49 node-2 kernel: [    2.598699] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 19 19:05:49 node-2 kernel: [    2.615822] md: multipath personality registered for level -4
Oct 19 19:05:49 node-2 kernel: [    2.623810] md: raid0 personality registered for level 0
Oct 19 19:05:49 node-2 kernel: [    2.632664] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 19 19:05:49 node-2 kernel: [    2.632666] md: raid1 personality registered for level 1
Oct 19 19:05:49 node-2 kernel: [    2.645469] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 19 19:05:49 node-2 kernel: [    2.651941] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 19 19:05:49 node-2 kernel: [    2.652565] megasas: FW now in Ready state
Oct 19 19:05:49 node-2 kernel: [    2.652639] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.652677] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.652719] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.652762] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.652811] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.652850] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.652911] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.652961] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653003] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653038] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653089] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653127] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653160] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653196] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653235] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653285] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.653523] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 19 19:05:49 node-2 kernel: [    2.686989] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct 19 19:05:49 node-2 kernel: [    2.700770] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 19 19:05:49 node-2 kernel: [    2.715226] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 19 19:05:49 node-2 kernel: [    2.722553] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.722557] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.722565] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.722569] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.722606] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.742428] raid6: sse2x1    2918 MB/s
Oct 19 19:05:49 node-2 kernel: [    2.748912] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct 19 19:05:49 node-2 kernel: [    2.748941] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct 19 19:05:49 node-2 kernel: [    2.748954] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 19 19:05:49 node-2 kernel: [    2.750038] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.750175] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.750310] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.750588] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.750705] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.750816] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.751112] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 19 19:05:49 node-2 kernel: [    2.770972] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct 19 19:05:49 node-2 kernel: [    2.771008] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 19 19:05:49 node-2 kernel: [    2.771018] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 19 19:05:49 node-2 kernel: [    2.898300] raid6: sse2x2    9785 MB/s
Oct 19 19:05:49 node-2 kernel: [    2.970240] raid6: sse2x4   10139 MB/s
Oct 19 19:05:49 node-2 kernel: [    3.042172] raid6: avx2x1   14953 MB/s
Oct 19 19:05:49 node-2 kernel: [    3.114111] raid6: avx2x2   18884 MB/s
Oct 19 19:05:49 node-2 kernel: [    3.186046] raid6: avx2x4   21394 MB/s
Oct 19 19:05:49 node-2 kernel: [    3.192364] raid6: using algorithm avx2x4 (21394 MB/s)
Oct 19 19:05:49 node-2 kernel: [    3.198632] raid6: using avx2x2 recovery algorithm
Oct 19 19:05:49 node-2 kernel: [    3.204838] megasas:IOC Init cmd success
Oct 19 19:05:49 node-2 kernel: [    3.204840] Switched to clocksource tsc
Oct 19 19:05:49 node-2 kernel: [    3.204842] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 19 19:05:49 node-2 kernel: [    3.204846] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 19 19:05:49 node-2 kernel: [    3.204847] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 19 19:05:49 node-2 kernel: [    3.204848] usb 2-1.4: Manufacturer: Avocent
Oct 19 19:05:49 node-2 kernel: [    3.204849] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 19 19:05:49 node-2 kernel: [    3.204995] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.205001] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.205037] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.205073] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.205179] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.212107] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct 19 19:05:49 node-2 kernel: [    3.212108] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 19 19:05:49 node-2 kernel: [    3.212110] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 19 19:05:49 node-2 kernel: [    3.212166] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.212203] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.212243] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.212279] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.212366] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 19 19:05:49 node-2 kernel: [    3.226026] megasas: INIT adapter done
Oct 19 19:05:49 node-2 kernel: [    3.291936] xor: automatically using best checksumming function:
Oct 19 19:05:49 node-2 kernel: [    3.297962] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 19 19:05:49 node-2 kernel: [    3.298331] scsi0 : LSI SAS based MegaRAID driver
Oct 19 19:05:49 node-2 kernel: [    3.303436] hidraw: raw HID events driver (C) Jiri Kosina
Oct 19 19:05:49 node-2 kernel: [    3.305436] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 19 19:05:49 node-2 kernel: [    3.316314] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 19 19:05:49 node-2 kernel: [    3.321202] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 19 19:05:49 node-2 kernel: [    3.321335] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 19 19:05:49 node-2 kernel: [    3.321631] sd 0:2:0:0: [sda] Write Protect is off
Oct 19 19:05:49 node-2 kernel: [    3.321632] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 19 19:05:49 node-2 kernel: [    3.321688] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 19 19:05:49 node-2 kernel: [    3.334943]    avx       : 52252.000 MB/sec
Oct 19 19:05:49 node-2 kernel: [    3.351852]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 19 19:05:49 node-2 kernel: [    3.352426] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 19 19:05:49 node-2 kernel: [    3.399466] usbcore: registered new interface driver usbhid
Oct 19 19:05:49 node-2 kernel: [    3.399467] usbhid: USB HID core driver
Oct 19 19:05:49 node-2 kernel: [    3.415379] async_tx: api initialized (async)
Oct 19 19:05:49 node-2 kernel: [    3.428138] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Oct 19 19:05:49 node-2 kernel: [    3.440791] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Oct 19 19:05:49 node-2 kernel: [    3.453591] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Oct 19 19:05:49 node-2 kernel: [    3.466340] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Oct 19 19:05:49 node-2 kernel: [    3.479682] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Oct 19 19:05:49 node-2 kernel: [    3.493362] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Oct 19 19:05:49 node-2 kernel: [    3.493376] md: raid6 personality registered for level 6
Oct 19 19:05:49 node-2 kernel: [    3.493376] md: raid5 personality registered for level 5
Oct 19 19:05:49 node-2 kernel: [    3.493377] md: raid4 personality registered for level 4
Oct 19 19:05:49 node-2 kernel: [    3.530222] random: lvm urandom read with 31 bits of entropy available
Oct 19 19:05:49 node-2 kernel: [    3.537014] md: raid10 personality registered for level 10
Oct 19 19:05:49 node-2 kernel: [    3.592859] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Oct 19 19:05:49 node-2 kernel: [    3.694141] bio: create slab <bio-1> at 1
Oct 19 19:05:49 node-2 kernel: [    4.642717] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 19:05:49 node-2 kernel: [    5.030042] random: nonblocking pool is initialized
Oct 19 19:05:49 node-2 kernel: [    5.194343] init: plymouth-upstart-bridge main process (574) terminated with status 1
Oct 19 19:05:49 node-2 kernel: [    5.206938] init: plymouth-upstart-bridge main process ended, respawning
Oct 19 19:05:49 node-2 kernel: [    5.370443] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Oct 19 19:05:49 node-2 kernel: [    5.396377] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 19 19:05:49 node-2 kernel: [    5.542115] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 19 19:05:49 node-2 kernel: [    5.572067] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 19 19:05:49 node-2 kernel: [    5.708227] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 19:05:49 node-2 kernel: [    5.868631] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 19 19:05:49 node-2 kernel: [    5.898051] XFS (dm-1): Mounting Filesystem
Oct 19 19:05:49 node-2 kernel: [    6.165542] XFS (dm-1): Ending clean mount
Oct 19 19:05:49 node-2 kernel: [    6.226746] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 19:05:49 node-2 kernel: [    6.266332] XFS (dm-2): Mounting Filesystem
Oct 19 19:05:49 node-2 kernel: [    6.379725] XFS (dm-2): Ending clean mount
Oct 19 19:05:49 node-2 kernel: [    6.504498] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Oct 19 19:05:49 node-2 kernel: [    8.250118] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 19 19:05:49 node-2 kernel: [    8.264843] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 19 19:05:49 node-2 kernel: [    8.468461] systemd-udevd[806]: starting version 204
Oct 19 19:05:49 node-2 kernel: [    8.653550] power_meter ACPI000D:00: Found ACPI power meter.
Oct 19 19:05:49 node-2 kernel: [    8.653562] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 19 19:05:49 node-2 kernel: [    8.666725] wmi: Mapper loaded
Oct 19 19:05:49 node-2 kernel: [    8.700013] IPMI System Interface driver.
Oct 19 19:05:49 node-2 kernel: [    8.700071] ipmi_si: probing via ACPI
Oct 19 19:05:49 node-2 kernel: [    8.700088] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 19 19:05:49 node-2 kernel: [    8.700088] ipmi_si: Adding ACPI-specified kcs state machine
Oct 19 19:05:49 node-2 kernel: [    8.700096] ipmi_si: probing via SMBIOS
Oct 19 19:05:49 node-2 kernel: [    8.700097] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 19 19:05:49 node-2 kernel: [    8.700098] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 19 19:05:49 node-2 kernel: [    8.700099] ipmi_si: probing via SPMI
Oct 19 19:05:49 node-2 kernel: [    8.700100] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 19 19:05:49 node-2 kernel: [    8.700101] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 19 19:05:49 node-2 kernel: [    8.700102] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 19 19:05:49 node-2 kernel: [    8.701415] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 19 19:05:49 node-2 kernel: [    8.706446] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 19 19:05:49 node-2 kernel: [    8.706451] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 19 19:05:49 node-2 kernel: [    8.706453] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 19 19:05:49 node-2 kernel: [    8.706455] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 19 19:05:49 node-2 kernel: [    8.706473] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 19 19:05:49 node-2 kernel: [    8.761811] systemd-udevd[834]: renamed network interface eth0 to enp6s0
Oct 19 19:05:49 node-2 kernel: [    8.792270] systemd-udevd[858]: renamed network interface eth1 to enp7s0
Oct 19 19:05:49 node-2 kernel: [    8.816605] systemd-udevd[824]: renamed network interface eth2 to enp8s0
Oct 19 19:05:49 node-2 kernel: [    8.840779] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 19 19:05:49 node-2 kernel: [    8.840785] ipmi_si 00:09: IPMI kcs interface initialized
Oct 19 19:05:49 node-2 kernel: [    8.845635] systemd-udevd[847]: renamed network interface eth3 to enp9s0
Oct 19 19:05:49 node-2 kernel: [    9.053309] type=1400 audit(1476903922.078:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.053464] type=1400 audit(1476903922.078:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1096 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.053587] type=1400 audit(1476903922.078:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1096 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.062024] type=1400 audit(1476903922.086:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1095 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.062165] type=1400 audit(1476903922.086:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1095 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.062285] type=1400 audit(1476903922.086:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1095 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.069401] type=1400 audit(1476903922.094:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1093 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.069640] type=1400 audit(1476903922.094:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1093 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.069834] type=1400 audit(1476903922.094:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1093 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.072231] type=1400 audit(1476903922.094:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1097 comm="apparmor_parser"
Oct 19 19:05:49 node-2 kernel: [    9.605247] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 19 19:05:49 node-2 kernel: [    9.606802] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 19 19:05:49 node-2 kernel: [    9.800088] enic 0000:06:00.0 enp6s0: Link UP
Oct 19 19:05:49 node-2 kernel: [    9.800612] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 19 19:05:49 node-2 kernel: [    9.800621] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 19 19:05:49 node-2 kernel: [   19.733236] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 19 19:05:50 node-2 failsafe: Failsafe of 120 seconds reached.
Oct 19 19:05:51 node-2 kernel: [   37.882148] init: failsafe main process (8449) killed by TERM signal
Oct 19 19:05:51 node-2 dbus[8536]: [system] AppArmor D-Bus mediation is enabled
Oct 19 19:05:51 node-2 kernel: [   38.041182] audit_printk_skb: 30 callbacks suppressed
Oct 19 19:05:51 node-2 kernel: [   38.041183] type=1400 audit(1476903951.169:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8575 comm="apparmor_parser"
Oct 19 19:05:51 node-2 kernel: [   38.048095] type=1400 audit(1476903951.177:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8574 comm="apparmor_parser"
Oct 19 19:05:51 node-2 kernel: [   38.048100] type=1400 audit(1476903951.177:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8574 comm="apparmor_parser"
Oct 19 19:05:51 node-2 kernel: [   38.048103] type=1400 audit(1476903951.177:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Oct 19 19:05:51 node-2 kernel: [   38.048334] type=1400 audit(1476903951.177:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8574 comm="apparmor_parser"
Oct 19 19:05:51 node-2 kernel: [   38.048336] type=1400 audit(1476903951.177:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Oct 19 19:05:51 node-2 kernel: [   38.048448] type=1400 audit(1476903951.177:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Oct 19 19:05:51 node-2 kernel: [   38.114537] type=1400 audit(1476903951.241:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8577 comm="apparmor_parser"
Oct 19 19:05:51 node-2 cron[8607]: (CRON) INFO (pidfile fd = 3)
Oct 19 19:05:51 node-2 anacron[8664]: Anacron 2.3 started on 2016-10-19
Oct 19 19:05:51 node-2 anacron[8664]: Will run job `cron.daily' in 5 min.
Oct 19 19:05:51 node-2 anacron[8664]: Will run job `cron.weekly' in 10 min.
Oct 19 19:05:51 node-2 anacron[8664]: Will run job `cron.monthly' in 15 min.
Oct 19 19:05:51 node-2 anacron[8664]: Jobs will be executed sequentially
Oct 19 19:05:51 node-2 multipathd: path checkers start up
Oct 19 19:05:51 node-2 cron[8679]: (CRON) STARTUP (fork ok)
Oct 19 19:05:51 node-2 cron[8679]: (CRON) INFO (Running @reboot jobs)
Oct 19 19:05:51 node-2 postfix/master[8786]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 19 19:05:55 node-2 puppet-agent[8970]: Reopening log files
Oct 19 19:05:56 node-2 puppet-agent[8970]: Could not request certificate: Connection refused - connect(2)
Oct 19 19:06:01 node-2 CRON[9001]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct 19 19:06:03 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 19 19:06:03 node-2 nailgun-agent: D, [2016-10-19T19:06:01.640702 #9004] DEBUG -- : Sleep for 2 seconds before sending request
Oct 19 19:06:03 node-2 nailgun-agent: I, [2016-10-19T19:06:03.674734 #9004]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 19 19:06:04 node-2 nailgun-agent: D, [2016-10-19T19:06:04.391608 #9004] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 19 19:06:09 node-2 puppet-user[9189]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 19 19:06:09 node-2 puppet-user[9189]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct 19 19:06:10 node-2 puppet-user[9189]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 19 19:06:10 node-2 puppet-user[9189]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 19 19:06:10 node-2 puppet-user[9189]: Finished catalog run in 0.84 seconds
Oct 19 19:06:11 node-2 multipathd: uevent trigger error
Oct 19 19:06:11 node-2 puppet-user[9624]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 19 19:06:12 node-2 puppet-user[9624]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 19 19:06:12 node-2 puppet-user[9624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 19 19:06:12 node-2 puppet-user[9624]: Finished catalog run in 0.07 seconds
Oct 19 19:06:13 node-2 puppet-user[10224]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 19 19:06:13 node-2 puppet-user[10224]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Oct 19 19:06:13 node-2 puppet-user[10224]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 19 19:06:13 node-2 puppet-user[10224]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 19 19:06:13 node-2 puppet-user[10224]: Finished catalog run in 0.04 seconds
Oct 19 19:06:15 node-2 puppet-user[10698]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 19 19:06:15 node-2 puppet-user[10698]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 19 19:06:15 node-2 puppet-user[10698]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 19 19:06:15 node-2 puppet-user[10698]: Finished catalog run in 0.06 seconds
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.462210 #9004] DEBUG -- : Trying to find block devices
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.462340 #9004] DEBUG -- : Found block device: sda
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.462386 #9004] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.462410 #9004] DEBUG -- : Trying to get list of physical devices
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.462606 #9004] DEBUG -- : Getting udev properties for device: sda
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.464558 #9004] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /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"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Oct 19 19:06:16 node-2 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6522", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.464586 #9004] DEBUG -- : Trying to find out if device sda is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.464632 #9004] DEBUG -- : Device sda removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.464649 #9004] DEBUG -- : Device sda seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.465101 #9004] DEBUG -- : Getting udev properties for device: dm-0
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.466727 #9004] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-DzHoOlfkGRizAeTli3HuAoFpDciERuZpb0m7RDLKp2dp7ggMEsto4BBqmMJ4Xiw0 /dev/disk/by-uuid/58704be7-e7cc-4ffb-aa94-248b9cd01841 /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-DzHoOlfkGRizAeTli3HuAoFpDciERuZpb0m7RDLKp2dp7ggMEsto4BBqmMJ4Xiw0", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"58704be7-e7cc-4ffb-aa94-248b9cd01841", "ID_FS_UUID_ENC"=>"58704be7-e7cc-4ffb-aa94-248b9cd01841", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48
Oct 19 19:06:16 node-2 nailgun-agent: 536", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.466756 #9004] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.466827 #9004] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.466842 #9004] DEBUG -- : Device dm-0 seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.466857 #9004] DEBUG -- : Getting udev properties for device: dm-1
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.468533 #9004] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-AdZ92TWWJPKf222xaNQ1tFt336cOt8cfiLU0uxTrZc6fbG0qyYGXRLHL6GGv8rvj /dev/disk/by-uuid/27f96da2-1b26-4e86-8567-acad98d3e80a /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-AdZ92TWWJPKf222xaNQ1tFt336cOt8cfiLU0uxTrZc6fbG0qyYGXRLHL6GGv8rvj", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"27f96da2-1b26-4e86-8567-acad98d3e80a", "ID_FS_UUID_ENC"=>"27f96da2-1b26-4e86-8567-acad98d3e80a", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69817", "nomdmonddf"=>"1", "nomd
Oct 19 19:06:16 node-2 nailgun-agent: monisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.468570 #9004] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.468601 #9004] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.468615 #9004] DEBUG -- : Device dm-1 seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.468647 #9004] DEBUG -- : Getting udev properties for device: dm-2
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.470216 #9004] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-GHk1s1K1ZPS106f66UBDjHvVyJblBPMQe1eYSn7Rv3qR4qYrdHpbp4AgMvtvwHSB /dev/disk/by-uuid/2a193b11-ec68-4ca3-993d-23c792aebc60 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-GHk1s1K1ZPS106f66UBDjHvVyJblBPMQe1eYSn7Rv3qR4qYrdHpbp4AgMvtvwHSB", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2a193b11-ec68-4ca3-993d-23c792aebc60", "ID_FS_UUID_ENC"=>"2a193b11-ec68-4ca3-993d-23c792aebc60", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"92
Oct 19 19:06:16 node-2 nailgun-agent: 967", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.470242 #9004] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.470276 #9004] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.470292 #9004] DEBUG -- : Device dm-2 seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.470346 #9004] DEBUG -- : Getting udev properties for device: dm-3
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.471919 #9004] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-qCEBs5qHJW4SKLG70hXiAtnN0UZa6AxfagWZlzrltcH2UNmWVPldri0ReRsnmdbG /dev/disk/by-uuid/889a1893-49cc-437d-b06b-ef276690b52c /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-qCEBs5qHJW4SKLG70hXiAtnN0UZa6AxfagWZlzrltcH2UNmWVPldri0ReRsnmdbG", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"889a1893-49cc-437d-b06b-ef276690b52c", "ID_FS_UUID_ENC"=>"889a1893-49cc-437d-b06b-ef276690b52c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11960", "nomdmond
Oct 19 19:06:16 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.471945 #9004] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.472013 #9004] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.472027 #9004] DEBUG -- : Device dm-3 seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.472041 #9004] DEBUG -- : Getting udev properties for device: dm-4
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.473596 #9004] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-QKU2DdzapCOr7UfkdG220r0OkYJdn36UDE7fbPmJdonnkHnrHgubPBUdAeqowmrD /dev/disk/by-uuid/4fb0c348-0891-45f5-b210-16779eedfc96 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-QKU2DdzapCOr7UfkdG220r0OkYJdn36UDE7fbPmJdonnkHnrHgubPBUdAeqowmrD", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4fb0c348-0891-45f5-b210-16779eedfc96", "ID_FS_UUID_ENC"=>"4fb0c348-0891-45f5-b210-16779eedfc96", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12764", "nomdmonddf"=>"1", 
Oct 19 19:06:16 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.473648 #9004] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.473679 #9004] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.473693 #9004] DEBUG -- : Device dm-4 seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.473718 #9004] DEBUG -- : Getting udev properties for device: dm-5
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.475316 #9004] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-NTCo0ThNwYWl3edpR0dOnyQ0w505u0ColyISPpTSbdu1QSqBPVVA9p1xgAgDK0Dn /dev/disk/by-uuid/b18955f7-6356-4729-ae35-20d2bbd51a6e /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-NTCo0ThNwYWl3edpR0dOnyQ0w505u0ColyISPpTSbdu1QSqBPVVA9p1xgAgDK0Dn", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b18955f7-6356-4729-ae35-20d2bbd51a6e", "ID_FS_UUID_ENC"=>"b18955f7-6356-4729-ae35-20d2bbd51a6e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13392", "nomdmonddf"=>"1", "nomd
Oct 19 19:06:16 node-2 nailgun-agent: monisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.475354 #9004] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.475387 #9004] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.475402 #9004] DEBUG -- : Device dm-5 seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.475417 #9004] DEBUG -- : Getting udev properties for device: dm-6
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.477099 #9004] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-NTCo0ThNwYWl3edpR0dOnyQ0w505u0Co6Kn7Jxm4IcbelD1pIUrCvADgHgYcHpLA /dev/disk/by-uuid/214093b8-ea62-417f-a4ad-86a06e6ab6e6 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-NTCo0ThNwYWl3edpR0dOnyQ0w505u0Co6Kn7Jxm4IcbelD1pIUrCvADgHgYcHpLA", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"214093b8-ea62-417f-a4ad-86a06e6ab6e6", "ID_FS_UUID_ENC"=>"214093b8-ea62-417f-a4ad-86a06e6ab6e6", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13860", "nomdmonddf"=>"1", "nomdmonisw"
Oct 19 19:06:16 node-2 nailgun-agent: =>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.477133 #9004] DEBUG -- : Trying to find out if device dm-6 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.477174 #9004] DEBUG -- : Device dm-6 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.477189 #9004] DEBUG -- : Device dm-6 seems to be appropriate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.477242 #9004] DEBUG -- : Getting udev properties for device: ram0
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.478636 #9004] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34797", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.478685 #9004] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.478723 #9004] DEBUG -- : Device ram0 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.478744 #9004] DEBUG -- : Getting udev properties for device: ram1
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.480256 #9004] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34813", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.480290 #9004] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.480338 #9004] DEBUG -- : Device ram1 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.480367 #9004] DEBUG -- : Getting udev properties for device: ram2
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.482021 #9004] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34955", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.482047 #9004] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.482079 #9004] DEBUG -- : Device ram2 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.482109 #9004] DEBUG -- : Getting udev properties for device: ram3
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.483609 #9004] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34974", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.483635 #9004] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.483682 #9004] DEBUG -- : Device ram3 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.483704 #9004] DEBUG -- : Getting udev properties for device: ram4
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.485184 #9004] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34994", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.485206 #9004] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.485245 #9004] DEBUG -- : Device ram4 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.485291 #9004] DEBUG -- : Getting udev properties for device: ram5
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.486792 #9004] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35015", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.486813 #9004] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.486847 #9004] DEBUG -- : Device ram5 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.486865 #9004] DEBUG -- : Getting udev properties for device: ram6
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.488242 #9004] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35043", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.488263 #9004] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.488308 #9004] DEBUG -- : Device ram6 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.488327 #9004] DEBUG -- : Getting udev properties for device: ram7
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.489762 #9004] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35060", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.489783 #9004] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.489812 #9004] DEBUG -- : Device ram7 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.489843 #9004] DEBUG -- : Getting udev properties for device: ram8
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.491246 #9004] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35080", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.491267 #9004] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.491298 #9004] DEBUG -- : Device ram8 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.491317 #9004] DEBUG -- : Getting udev properties for device: ram9
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.492788 #9004] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35098", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.492811 #9004] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.492868 #9004] DEBUG -- : Device ram9 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.492887 #9004] DEBUG -- : Getting udev properties for device: loop0
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.494342 #9004] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34692", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.494382 #9004] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.494416 #9004] DEBUG -- : Device loop0 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.494435 #9004] DEBUG -- : Getting udev properties for device: loop1
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.495830 #9004] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34706", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.495852 #9004] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.495881 #9004] DEBUG -- : Device loop1 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.495915 #9004] DEBUG -- : Getting udev properties for device: loop2
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.497341 #9004] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34718", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.497362 #9004] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.497402 #9004] DEBUG -- : Device loop2 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.497421 #9004] DEBUG -- : Getting udev properties for device: loop3
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.498853 #9004] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34732", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.498875 #9004] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.498917 #9004] DEBUG -- : Device loop3 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.498953 #9004] DEBUG -- : Getting udev properties for device: loop4
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.500384 #9004] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34743", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.500405 #9004] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.500444 #9004] DEBUG -- : Device loop4 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.500462 #9004] DEBUG -- : Getting udev properties for device: loop5
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.501842 #9004] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34755", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.501883 #9004] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.501916 #9004] DEBUG -- : Device loop5 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.501935 #9004] DEBUG -- : Getting udev properties for device: loop6
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.503377 #9004] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34765", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.503409 #9004] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.503438 #9004] DEBUG -- : Device loop6 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.503456 #9004] DEBUG -- : Getting udev properties for device: loop7
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.504847 #9004] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34782", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.504867 #9004] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.504904 #9004] DEBUG -- : Device loop7 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.504928 #9004] DEBUG -- : Getting udev properties for device: ram10
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.506376 #9004] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34834", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.506416 #9004] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.506447 #9004] DEBUG -- : Device ram10 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.506465 #9004] DEBUG -- : Getting udev properties for device: ram11
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.507914 #9004] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34855", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.507936 #9004] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.507977 #9004] DEBUG -- : Device ram11 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.508010 #9004] DEBUG -- : Getting udev properties for device: ram12
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.509424 #9004] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34875", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.509446 #9004] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.509478 #9004] DEBUG -- : Device ram12 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.509519 #9004] DEBUG -- : Getting udev properties for device: ram13
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.510933 #9004] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34894", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.510962 #9004] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.511009 #9004] DEBUG -- : Device ram13 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.511037 #9004] DEBUG -- : Getting udev properties for device: ram14
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.517667 #9004] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34914", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.517718 #9004] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.517786 #9004] DEBUG -- : Device ram14 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.517810 #9004] DEBUG -- : Getting udev properties for device: ram15
Oct 19 19:06:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.519915 #9004] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34933", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.519977 #9004] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520021 #9004] DEBUG -- : Device ram15 removable parameter: "0"
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520057 #9004] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520072 #9004] DEBUG -- : Block device seems to be physical data storage: sda
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520117 #9004] DEBUG -- : Found block device: dm-0
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520132 #9004] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520146 #9004] DEBUG -- : Found block device: dm-1
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520156 #9004] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520166 #9004] DEBUG -- : Found block device: dm-2
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520218 #9004] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520227 #9004] DEBUG -- : Found block device: dm-3
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520236 #9004] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520245 #9004] DEBUG -- : Found block device: dm-4
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520255 #9004] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520264 #9004] DEBUG -- : Found block device: dm-5
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520274 #9004] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520283 #9004] DEBUG -- : Found block device: dm-6
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520293 #9004] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520348 #9004] DEBUG -- : Found block device: ram0
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520359 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520369 #9004] DEBUG -- : Found block device: ram1
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520379 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520388 #9004] DEBUG -- : Found block device: ram2
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520398 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520407 #9004] DEBUG -- : Found block device: ram3
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520417 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520426 #9004] DEBUG -- : Found block device: ram4
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520469 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520479 #9004] DEBUG -- : Found block device: ram5
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520490 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520499 #9004] DEBUG -- : Found block device: ram6
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520511 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520521 #9004] DEBUG -- : Found block device: ram7
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520531 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520540 #9004] DEBUG -- : Found block device: ram8
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520550 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520558 #9004] DEBUG -- : Found block device: ram9
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520601 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520620 #9004] DEBUG -- : Found block device: loop0
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520631 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520640 #9004] DEBUG -- : Found block device: loop1
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520649 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520657 #9004] DEBUG -- : Found block device: loop2
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520667 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520676 #9004] DEBUG -- : Found block device: loop3
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520686 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520734 #9004] DEBUG -- : Found block device: loop4
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520747 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520756 #9004] DEBUG -- : Found block device: loop5
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520767 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520776 #9004] DEBUG -- : Found block device: loop6
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520786 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520794 #9004] DEBUG -- : Found block device: loop7
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520803 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520812 #9004] DEBUG -- : Found block device: ram10
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520867 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520876 #9004] DEBUG -- : Found block device: ram11
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520888 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520897 #9004] DEBUG -- : Found block device: ram12
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520907 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520916 #9004] DEBUG -- : Found block device: ram13
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520926 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520934 #9004] DEBUG -- : Found block device: ram14
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520945 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520954 #9004] DEBUG -- : Found block device: ram15
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.520989 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.521019 #9004] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.610971 #9004] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 19 19:06:16 node-2 nailgun-agent: D, [2016-10-19T19:06:16.611036 #9004] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 19 19:06:17 node-2 puppet-user[11157]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 19 19:06:17 node-2 puppet-user[11157]: Compiled catalog for node-2.domain.tld in environment production in 0.24 seconds
Oct 19 19:06:17 node-2 puppet-user[11157]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 19 19:06:17 node-2 puppet-user[11157]: (/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
Oct 19 19:06:17 node-2 puppet-user[11157]: Finished catalog run in 0.45 seconds
Oct 19 19:06:19 node-2 puppet-user[11825]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 19 19:06:19 node-2 puppet-user[11825]: Compiled catalog for node-2.domain.tld in environment production in 0.27 seconds
Oct 19 19:06:19 node-2 puppet-user[11825]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 19 19:06:19 node-2 puppet-user[11825]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 19 19:06:19 node-2 puppet-user[11825]: (/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
Oct 19 19:06:19 node-2 puppet-user[11825]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 19 19:06:20 node-2 puppet-user[11825]: Finished catalog run in 0.39 seconds
Oct 19 19:06:21 node-2 puppet-user[12310]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 19 19:06:21 node-2 puppet-user[12310]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Oct 19 19:06:21 node-2 puppet-user[12310]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 19 19:06:21 node-2 kernel: [   68.578771] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 19 19:06:21 node-2 kernel: [   68.578819] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Oct 19 19:06:21 node-2 puppet-user[12310]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Oct 19 19:06:21 node-2 puppet-user[12310]: Finished catalog run in 0.06 seconds
Oct 19 19:06:23 node-2 puppet-user[12764]: (Scope(Class[main])) MODULAR: sync_time
Oct 19 19:06:23 node-2 puppet-user[12764]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 19 19:06:23 node-2 ntpdate[13373]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 19 19:06:28 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481358 #9004] DEBUG -- : Trying to find block devices
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481454 #9004] DEBUG -- : Found block device: sda
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481487 #9004] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481514 #9004] DEBUG -- : Block device seems to be physical data storage: sda
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481541 #9004] DEBUG -- : Found block device: dm-0
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481585 #9004] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481599 #9004] DEBUG -- : Found block device: dm-1
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481621 #9004] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481632 #9004] DEBUG -- : Found block device: dm-2
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481643 #9004] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481651 #9004] DEBUG -- : Found block device: dm-3
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481662 #9004] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481671 #9004] DEBUG -- : Found block device: dm-4
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481681 #9004] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481719 #9004] DEBUG -- : Found block device: dm-5
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481731 #9004] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481740 #9004] DEBUG -- : Found block device: dm-6
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481750 #9004] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481759 #9004] DEBUG -- : Found block device: ram0
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481769 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481777 #9004] DEBUG -- : Found block device: ram1
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481786 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481795 #9004] DEBUG -- : Found block device: ram2
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481804 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481849 #9004] DEBUG -- : Found block device: ram3
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481859 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481867 #9004] DEBUG -- : Found block device: ram4
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481877 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481886 #9004] DEBUG -- : Found block device: ram5
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481896 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481905 #9004] DEBUG -- : Found block device: ram6
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481915 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481924 #9004] DEBUG -- : Found block device: ram7
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481935 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481970 #9004] DEBUG -- : Found block device: ram8
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481981 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.481990 #9004] DEBUG -- : Found block device: ram9
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482000 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482008 #9004] DEBUG -- : Found block device: loop0
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482018 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482027 #9004] DEBUG -- : Found block device: loop1
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482036 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482044 #9004] DEBUG -- : Found block device: loop2
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482053 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482062 #9004] DEBUG -- : Found block device: loop3
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482101 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482110 #9004] DEBUG -- : Found block device: loop4
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482120 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482129 #9004] DEBUG -- : Found block device: loop5
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482147 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482169 #9004] DEBUG -- : Found block device: loop6
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482179 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482188 #9004] DEBUG -- : Found block device: loop7
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482199 #9004] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482208 #9004] DEBUG -- : Found block device: ram10
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482241 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482250 #9004] DEBUG -- : Found block device: ram11
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482260 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482270 #9004] DEBUG -- : Found block device: ram12
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482281 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482289 #9004] DEBUG -- : Found block device: ram13
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482299 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482307 #9004] DEBUG -- : Found block device: ram14
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482317 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482326 #9004] DEBUG -- : Found block device: ram15
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482359 #9004] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.482396 #9004] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct 19 19:06:28 node-2 nailgun-agent: D, [2016-10-19T19:06:28.657806 #9004] DEBUG -- : Response: status: 200 body: {"id": 2}
Oct 19 19:06:28 node-2 nailgun-agent: I, [2016-10-19T19:06:28.657984 #9004]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 19 19:06:29 node-2 ntpdate[13373]: adjust time server 10.20.0.2 offset -0.041785 sec
Oct 19 19:06:29 node-2 puppet-user[12764]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 19 19:06:29 node-2 puppet-user[12764]: Finished catalog run in 6.19 seconds
Oct 19 19:06:34 node-2 puppet-user[13696]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 19 19:06:34 node-2 puppet-user[13696]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Oct 19 19:06:34 node-2 puppet-user[13696]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 19 19:06:34 node-2 puppet-user[13696]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Oct 19 19:06:35 node-2 puppet-user[13696]: Finished catalog run in 0.07 seconds
Oct 19 19:06:35 node-2 kernel: [   82.724676] init: plymouth-upstart-bridge main process ended, respawning
Oct 19 19:06:36 node-2 puppet-agent[8970]: Could not run: SIGTERM
Oct 19 19:06:36 node-2 kernel: [   83.051253] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 19 19:06:36 node-2 ec2: 
Oct 19 19:06:36 node-2 ec2: #############################################################
Oct 19 19:06:36 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 19 19:06:36 node-2 ec2: 1024 3a:30:3d:d4:71:bb:50:e0:86:3e:97:cc:de:37:86:ff  root@node-2.domain.tld (DSA)
Oct 19 19:06:36 node-2 ec2: 256 df:da:ae:13:80:7a:ca:a5:28:e4:f9:7b:c3:11:da:a6  root@node-2.domain.tld (ECDSA)
Oct 19 19:06:36 node-2 ec2: 256 32:4b:67:13:eb:da:09:6a:a6:83:4f:99:a0:30:f6:f6  root@node-2.domain.tld (ED25519)
Oct 19 19:06:36 node-2 ec2: 2048 ba:a1:f0:aa:1a:de:4c:21:b0:b8:22:95:84:84:6c:6f  root@node-2.domain.tld (RSA)
Oct 19 19:06:36 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 19 19:06:36 node-2 ec2: #############################################################
Oct 19 19:06:36 node-2 puppet-user[14157]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 19 19:06:36 node-2 puppet-user[14157]: Compiled catalog for node-2.domain.tld in environment production in 0.50 seconds
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 19 19:06:37 node-2 puppet-user[14157]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 19 19:06:37 node-2 puppet-user[14157]: Finished catalog run in 0.82 seconds
Oct 19 19:06:39 node-2 puppet-user[14839]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 19 19:06:39 node-2 puppet-user[14839]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Oct 19 19:06:43 node-2 puppet-user[14839]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 19 19:07:01 node-2 CRON[16526]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct 19 19:07:11 node-2 puppet-user[14839]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 19 19:07:11 node-2 puppet-user[14839]: Finished catalog run in 31.17 seconds
Oct 19 19:07:13 node-2 puppet-user[17308]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 19 19:07:13 node-2 puppet-user[17308]: Compiled catalog for node-2.domain.tld in environment production in 0.62 seconds
Oct 19 19:07:13 node-2 puppet-user[17308]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 19 19:07:13 node-2 puppet-user[17308]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 19 19:07:13 node-2 puppet-user[17308]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 19 19:07:13 node-2 puppet-user[17308]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 19 19:07:13 node-2 puppet-user[17308]: Finished catalog run in 0.11 seconds
Oct 19 19:07:15 node-2 puppet-user[17773]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 19 19:07:16 node-2 puppet-user[17773]: Compiled catalog for node-2.domain.tld in environment production in 0.86 seconds
Oct 19 19:07:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 19 19:07:16 node-2 nailgun-agent: I, [2016-10-19T19:07:16.843198 #16529]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 19 19:07:16 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 19 19:07:16 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 19 19:07:16 node-2 crontab[18268]: (root) LIST (root)
Oct 19 19:07:16 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 19 19:07:16 node-2 crontab[18272]: (root) REPLACE (root)
Oct 19 19:07:18 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Oct 19 19:07:19 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 19 19:07:20 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Oct 19 19:07:20 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Oct 19 19:07:20 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 19 19:07:20 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 19 19:07:20 node-2 puppet-user[17773]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 19 19:07:20 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8422" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 19 19:07:20 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 19 19:07:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:34 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:34 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:34 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:34 node-2 multipathd: uevent trigger error
<27>Oct 19 19:07:34 node-2 multipathd: uevent trigger error
<27>Oct 19 19:08:30 node-2 ntpdate[28851]: no servers can be used, exiting
<27>Oct 19 19:08:30 node-2 ntpdate[29095]: no servers can be used, exiting
<27>Oct 19 19:09:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:02 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:19 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:19 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:19 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:19 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:19 node-2 multipathd: uevent trigger error
<27>Oct 19 19:09:19 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:26 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 19:10:26 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 19:10:32 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 19:10:32 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 19:10:38 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 19:10:43 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 19:10:43 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 19 19:10:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:10:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:04 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:04 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:06 node-2 haproxy[16887]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:07 node-2 haproxy[16893]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:07 node-2 haproxy[16893]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:07 node-2 haproxy[16893]: proxy mysqld has no server available!
<27>Oct 19 19:11:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:13 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:15 node-2 haproxy[19430]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:16 node-2 haproxy[19434]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:16 node-2 haproxy[19434]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:16 node-2 haproxy[19434]: proxy mysqld has no server available!
<129>Oct 19 19:11:16 node-2 haproxy[19434]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:17 node-2 haproxy[19434]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:17 node-2 haproxy[19434]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:17 node-2 haproxy[19434]: proxy object-storage has no server available!
<27>Oct 19 19:11:18 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:18 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:18 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:18 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:18 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:21 node-2 haproxy[20779]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:21 node-2 haproxy[20779]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:21 node-2 haproxy[20779]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:21 node-2 haproxy[20779]: proxy neutron has no server available!
<129>Oct 19 19:11:21 node-2 haproxy[20779]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:21 node-2 haproxy[20779]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:22 node-2 haproxy[20785]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:22 node-2 haproxy[20785]: proxy mysqld has no server available!
<129>Oct 19 19:11:22 node-2 haproxy[20785]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:22 node-2 haproxy[20785]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:22 node-2 haproxy[20785]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:22 node-2 haproxy[20785]: proxy object-storage has no server available!
<27>Oct 19 19:11:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:24 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:26 node-2 haproxy[22302]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:26 node-2 haproxy[22302]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:26 node-2 haproxy[22302]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:26 node-2 haproxy[22302]: proxy keystone-1 has no server available!
<129>Oct 19 19:11:26 node-2 haproxy[22302]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:27 node-2 haproxy[22306]: proxy keystone-2 has no server available!
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:27 node-2 haproxy[22306]: proxy neutron has no server available!
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:27 node-2 haproxy[22306]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:27 node-2 haproxy[22306]: proxy mysqld has no server available!
<129>Oct 19 19:11:28 node-2 haproxy[22306]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:28 node-2 haproxy[22306]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:28 node-2 haproxy[22306]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:28 node-2 haproxy[22306]: proxy object-storage has no server available!
<27>Oct 19 19:11:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:29 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:31 node-2 haproxy[23675]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:31 node-2 haproxy[23675]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:32 node-2 haproxy[23679]: proxy keystone-1 has no server available!
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:32 node-2 haproxy[23679]: proxy keystone-2 has no server available!
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:32 node-2 haproxy[23679]: proxy neutron has no server available!
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:32 node-2 haproxy[23679]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:33 node-2 haproxy[23679]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:33 node-2 haproxy[23679]: proxy mysqld has no server available!
<129>Oct 19 19:11:33 node-2 haproxy[23679]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:33 node-2 haproxy[23679]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:33 node-2 haproxy[23679]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:33 node-2 haproxy[23679]: proxy object-storage has no server available!
<129>Oct 19 19:11:33 node-2 haproxy[23679]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:33 node-2 haproxy[23679]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:33 node-2 haproxy[23679]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:33 node-2 haproxy[23679]: proxy aodh has no server available!
<27>Oct 19 19:11:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:35 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:37 node-2 haproxy[25213]: proxy keystone-1 has no server available!
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:37 node-2 haproxy[25213]: proxy keystone-2 has no server available!
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:37 node-2 haproxy[25213]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:38 node-2 haproxy[25217]: proxy neutron has no server available!
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:38 node-2 haproxy[25217]: proxy mysqld has no server available!
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:38 node-2 haproxy[25217]: proxy object-storage has no server available!
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:38 node-2 haproxy[25217]: proxy aodh has no server available!
<129>Oct 19 19:11:38 node-2 haproxy[25217]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:39 node-2 haproxy[25217]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:39 node-2 haproxy[25217]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:39 node-2 haproxy[25217]: proxy ceilometer has no server available!
<27>Oct 19 19:11:40 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:40 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:40 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:40 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:40 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:42 node-2 haproxy[26567]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:42 node-2 haproxy[26567]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:42 node-2 haproxy[26567]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:42 node-2 haproxy[26567]: proxy keystone-1 has no server available!
<129>Oct 19 19:11:42 node-2 haproxy[26567]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:43 node-2 haproxy[26571]: proxy keystone-2 has no server available!
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:43 node-2 haproxy[26571]: proxy neutron has no server available!
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:43 node-2 haproxy[26571]: proxy mysqld has no server available!
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:43 node-2 haproxy[26571]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:43 node-2 haproxy[26571]: proxy object-storage has no server available!
<129>Oct 19 19:11:44 node-2 haproxy[26571]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:44 node-2 haproxy[26571]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:44 node-2 haproxy[26571]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:44 node-2 haproxy[26571]: proxy aodh has no server available!
<129>Oct 19 19:11:44 node-2 haproxy[26571]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:44 node-2 haproxy[26571]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:44 node-2 haproxy[26571]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:44 node-2 haproxy[26571]: proxy ceilometer has no server available!
<27>Oct 19 19:11:45 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:45 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:45 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:45 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:45 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:45 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:48 node-2 haproxy[27933]: proxy keystone-1 has no server available!
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:48 node-2 haproxy[27933]: proxy keystone-2 has no server available!
<129>Oct 19 19:11:48 node-2 haproxy[27933]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:49 node-2 haproxy[27937]: proxy neutron has no server available!
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:49 node-2 haproxy[27937]: proxy mysqld has no server available!
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:49 node-2 haproxy[27937]: proxy object-storage has no server available!
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:49 node-2 haproxy[27937]: proxy aodh has no server available!
<129>Oct 19 19:11:49 node-2 haproxy[27937]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:50 node-2 haproxy[27937]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:50 node-2 haproxy[27937]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:50 node-2 haproxy[27937]: proxy ceilometer has no server available!
<27>Oct 19 19:11:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:51 node-2 multipathd: uevent trigger error
<129>Oct 19 19:11:53 node-2 haproxy[29318]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:54 node-2 haproxy[29322]: proxy keystone-1 has no server available!
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:54 node-2 haproxy[29322]: proxy keystone-2 has no server available!
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:54 node-2 haproxy[29322]: proxy glance-api has no server available!
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:54 node-2 haproxy[29322]: proxy glance-glare has no server available!
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:54 node-2 haproxy[29322]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:54 node-2 haproxy[29322]: proxy neutron has no server available!
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:55 node-2 haproxy[29322]: proxy glance-registry has no server available!
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:55 node-2 haproxy[29322]: proxy mysqld has no server available!
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:55 node-2 haproxy[29322]: proxy object-storage has no server available!
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:55 node-2 haproxy[29322]: proxy aodh has no server available!
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:11:55 node-2 haproxy[29322]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:11:55 node-2 haproxy[29322]: proxy ceilometer has no server available!
<27>Oct 19 19:11:57 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:57 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:57 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:57 node-2 multipathd: uevent trigger error
<27>Oct 19 19:11:57 node-2 multipathd: uevent trigger error
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:00 node-2 haproxy[30708]: proxy keystone-1 has no server available!
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:00 node-2 haproxy[30708]: proxy keystone-2 has no server available!
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:00 node-2 haproxy[30708]: proxy nova-api has no server available!
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:00 node-2 haproxy[30708]: proxy nova-metadata-api has no server available!
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:00 node-2 haproxy[30708]: proxy glance-api has no server available!
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:00 node-2 haproxy[30708]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:00 node-2 haproxy[30708]: proxy glance-glare has no server available!
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:01 node-2 haproxy[30714]: proxy neutron has no server available!
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:01 node-2 haproxy[30714]: proxy glance-registry has no server available!
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:01 node-2 haproxy[30714]: proxy mysqld has no server available!
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:01 node-2 haproxy[30714]: proxy object-storage has no server available!
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:01 node-2 haproxy[30714]: proxy aodh has no server available!
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:01 node-2 haproxy[30714]: proxy ceilometer has no server available!
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:01 node-2 haproxy[30714]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:01 node-2 haproxy[30714]: proxy nova-novncproxy has no server available!
<27>Oct 19 19:12:03 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:03 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:03 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:03 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:03 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:03 node-2 multipathd: uevent trigger error
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:05 node-2 haproxy[32063]: proxy keystone-1 has no server available!
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:05 node-2 haproxy[32063]: proxy keystone-2 has no server available!
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:05 node-2 haproxy[32063]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy nova-api has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy nova-metadata-api has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy cinder-api has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy glance-api has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy glance-glare has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy neutron has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy glance-registry has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:06 node-2 haproxy[32080]: proxy mysqld has no server available!
<129>Oct 19 19:12:06 node-2 haproxy[32080]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:07 node-2 haproxy[32080]: proxy object-storage has no server available!
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:07 node-2 haproxy[32080]: proxy aodh has no server available!
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:07 node-2 haproxy[32080]: proxy ceilometer has no server available!
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:07 node-2 haproxy[32080]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:07 node-2 haproxy[32080]: proxy nova-novncproxy has no server available!
<27>Oct 19 19:12:08 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:08 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:08 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:08 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:08 node-2 multipathd: uevent trigger error
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:11 node-2 haproxy[1137]: proxy keystone-1 has no server available!
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:11 node-2 haproxy[1137]: proxy keystone-2 has no server available!
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:11 node-2 haproxy[1137]: proxy nova-api has no server available!
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:11 node-2 haproxy[1137]: proxy nova-metadata-api has no server available!
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:11 node-2 haproxy[1137]: proxy cinder-api has no server available!
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:11 node-2 haproxy[1137]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:11 node-2 haproxy[1137]: proxy glance-api has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy glance-glare has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy neutron has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy glance-registry has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy mysqld has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy object-storage has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy aodh has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy ceilometer has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy heat-api has no server available!
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:12 node-2 haproxy[1141]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:12 node-2 haproxy[1141]: proxy heat-api-cfn has no server available!
<129>Oct 19 19:12:13 node-2 haproxy[1141]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:13 node-2 haproxy[1141]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:13 node-2 haproxy[1141]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:13 node-2 haproxy[1141]: proxy heat-api-cloudwatch has no server available!
<129>Oct 19 19:12:13 node-2 haproxy[1141]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:13 node-2 haproxy[1141]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 19 19:12:13 node-2 haproxy[1141]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 19 19:12:13 node-2 haproxy[1141]: proxy nova-novncproxy has no server available!
<27>Oct 19 19:12:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:12:25 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 19 19:12:50 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Oct 19 19:12:52 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 19 19:13:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 19:13:19 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 19:13:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:13:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:13:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:13:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:13:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:15:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:15:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:15:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:15:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:15:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:15:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 19 19:16:21 node-2 apache2_error [Wed Oct 19 19:16:17.103891 2016] [mpm_event:notice] [pid 10068:tid 139690755012480] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 19 19:16:21 node-2 apache2_error [Wed Oct 19 19:16:17.113101 2016] [core:notice] [pid 10068:tid 139690755012480] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 19 19:16:21 node-2 apache2_error [Wed Oct 19 19:16:19.035640 2016] [mpm_event:notice] [pid 10068:tid 139690755012480] AH00491: caught SIGTERM, shutting down
<43>Oct 19 19:16:21 node-2 apache2_error [Wed Oct 19 19:16:20.129723 2016] [mpm_worker:notice] [pid 11764:tid 139911948515200] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 19 19:16:21 node-2 apache2_error [Wed Oct 19 19:16:20.129796 2016] [core:notice] [pid 11764:tid 139911948515200] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 19:16:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:16:33 node-2 multipathd: uevent trigger error
<43>Oct 19 19:17:41 node-2 apache2_error [Wed Oct 19 19:17:38.009963 2016] [mpm_worker:notice] [pid 11764:tid 139911948515200] AH00295: caught SIGTERM, shutting down
<43>Oct 19 19:17:41 node-2 apache2_error [Wed Oct 19 19:17:38.762668 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 19:17:41 node-2 apache2_error [Wed Oct 19 19:17:38.762700 2016] [core:notice] [pid 25932:tid 139944704968576] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 19 19:18:31 node-2 apache2_error [Wed Oct 19 19:18:24.044179 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 19:18:31 node-2 apache2_error [Wed Oct 19 19:18:24.238425 2016] [mpm_worker:warn] [pid 25932:tid 139944704968576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 19:18:31 node-2 apache2_error [Wed Oct 19 19:18:24.241099 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 19:18:31 node-2 apache2_error [Wed Oct 19 19:18:24.241114 2016] [core:notice] [pid 25932:tid 139944704968576] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 19:19:08 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:08 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:13 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:18 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 19:19:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:19:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:33 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:20:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:21:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:21:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:21:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:21:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:21:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:22:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 19:22:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:22:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:22:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:22:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:22:51 node-2 multipathd: uevent trigger error
<27>Oct 19 19:23:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:23:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:23:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:23:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:23:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:24:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:25:21 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 19:26:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:26:59 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:27:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:28:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:28:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:28:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:28:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:28:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:28:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 19:29:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:01 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct 19 19:29:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct 19 19:29:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct 19 19:29:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct 19 19:29:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct 19 19:29:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:09 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:55 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:55 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:55 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:55 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:55 node-2 multipathd: uevent trigger error
<27>Oct 19 19:29:55 node-2 multipathd: uevent trigger error
<27>Oct 19 19:31:25 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 19:32:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:56 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:56 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:56 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:56 node-2 multipathd: uevent trigger error
<27>Oct 19 19:32:56 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:25 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:25 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:25 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:25 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:25 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:25 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:41 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:41 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:41 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:41 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:41 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:46 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:33:52 node-2 multipathd: uevent trigger error
<27>Oct 19 19:34:26 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 19 19:34:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:34:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:34:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:34:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:34:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:34:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:35:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:35:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:35:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:35:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:35:49 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:06 node-2 multipathd: uevent trigger error
<11>Oct 19 19:36:19 node-2 liberasurecode[23064]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:19 node-2 liberasurecode[23064]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:19 node-2 liberasurecode[23064]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:19 node-2 liberasurecode[23064]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:19 node-2 liberasurecode[23091]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:19 node-2 liberasurecode[23091]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:19 node-2 liberasurecode[23091]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:19 node-2 liberasurecode[23091]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:21 node-2 liberasurecode[23813]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:21 node-2 liberasurecode[23813]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:21 node-2 liberasurecode[23813]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:21 node-2 liberasurecode[23813]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24416]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24416]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24416]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24416]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24455]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24455]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24455]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:25 node-2 liberasurecode[24455]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24501]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24501]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24501]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24501]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24558]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24558]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24578]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24578]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24590]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24590]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24590]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24590]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24609]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24609]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24609]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:26 node-2 liberasurecode[24609]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:35 node-2 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:35 node-2 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:35 node-2 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:36:35 node-2 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 19 19:36:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:36:44 node-2 multipathd: uevent trigger error
<27>Oct 19 19:37:28 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 19 19:37:42 node-2 apache2_error [Wed Oct 19 19:37:32.959611 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 19:37:42 node-2 apache2_error [Wed Oct 19 19:37:33.343569 2016] [mpm_worker:warn] [pid 25932:tid 139944704968576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 19:37:42 node-2 apache2_error [Wed Oct 19 19:37:33.349127 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 19:37:42 node-2 apache2_error [Wed Oct 19 19:37:33.349165 2016] [core:notice] [pid 25932:tid 139944704968576] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 19 19:38:12 node-2 apache2_error [Wed Oct 19 19:38:10.179876 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 19:38:12 node-2 apache2_error [Wed Oct 19 19:38:10.377056 2016] [mpm_worker:warn] [pid 25932:tid 139944704968576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 19:38:12 node-2 apache2_error [Wed Oct 19 19:38:10.385201 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 19:38:12 node-2 apache2_error [Wed Oct 19 19:38:10.385228 2016] [core:notice] [pid 25932:tid 139944704968576] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 19:38:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:14 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:38:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:00 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:00 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:00 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:00 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:00 node-2 multipathd: uevent trigger error
<43>Oct 19 19:39:02 node-2 apache2_error [Wed Oct 19 19:38:56.018820 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 19 19:39:02 node-2 apache2_error [Wed Oct 19 19:38:56.212751 2016] [mpm_worker:warn] [pid 25932:tid 139944704968576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 19 19:39:02 node-2 apache2_error [Wed Oct 19 19:38:56.222064 2016] [mpm_worker:notice] [pid 25932:tid 139944704968576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 19 19:39:02 node-2 apache2_error [Wed Oct 19 19:38:56.222097 2016] [core:notice] [pid 25932:tid 139944704968576] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 19 19:39:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:11 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:28 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:39:42 node-2 multipathd: uevent trigger error
<11>Oct 19 19:40:01 node-2 liberasurecode[4717]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:40:01 node-2 liberasurecode[4717]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:40:01 node-2 liberasurecode[4717]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:40:01 node-2 liberasurecode[4717]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 19 19:40:06 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:13 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 19 19:40:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:22 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:26 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:26 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:26 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:26 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:26 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:26 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:32 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:32 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:32 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:32 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:32 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:37 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:38 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:38 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:38 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:49 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 19 19:40:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:40:50 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:16 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:17 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:21 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:35 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:42 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:41:47 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:05 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:10 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:10 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:10 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:10 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:10 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:10 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:15 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:20 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:20 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:20 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:20 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:20 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:24 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:29 node-2 multipathd: uevent trigger error
<27>Oct 19 19:43:29 node-2 multipathd: uevent trigger error
<11>Oct 19 19:45:02 node-2 liberasurecode[874]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:45:02 node-2 liberasurecode[874]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:45:02 node-2 liberasurecode[874]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 19 19:45:02 node-2 liberasurecode[874]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
