Sep 11 18:30:21 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] start
Sep 11 18:30:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 11 18:30:21 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep 11 18:30:21 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep 11 18:30:21 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 11 18:30:21 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 11 18:30:21 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 11 18:30:21 node-2 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 11 18:30:21 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4ae3f936-c6bd-4661-b29f-0fa5a7d189a1 nomdmonddf nomdmonisw
Sep 11 18:30:21 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep 11 18:30:21 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep 11 18:30:21 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep 11 18:30:21 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep 11 18:30:21 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 11 18:30:21 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 11 18:30:21 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 11 18:30:21 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
Sep 11 18:30:21 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 11 18:30:21 node-2 kernel: [    0.000000] No AGP bridge found
Sep 11 18:30:21 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 11 18:30:21 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep 11 18:30:21 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 11 18:30:21 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep 11 18:30:21 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 11 18:30:21 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 11 18:30:21 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 11 18:30:21 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 11 18:30:21 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 11 18:30:21 node-2 kernel: [    0.000000]   2 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000]   3 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000]   4 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000]   5 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000]   6 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000]   7 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000]   8 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000]   9 disabled
Sep 11 18:30:21 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 11 18:30:21 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 11 18:30:21 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 11 18:30:21 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 11 18:30:21 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 11 18:30:21 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 11 18:30:21 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 11 18:30:21 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 11 18:30:21 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 11 18:30:21 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 11 18:30:21 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 11 18:30:21 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 11 18:30:21 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 11 18:30:21 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 11 18:30:21 node-2 kernel: [    0.000000] Zone ranges:
Sep 11 18:30:21 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] Movable zone start for each node
Sep 11 18:30:21 node-2 kernel: [    0.000000] Early memory node ranges
Sep 11 18:30:21 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 11 18:30:21 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 11 18:30:21 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 11 18:30:21 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 11 18:30:21 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 11 18:30:21 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 11 18:30:21 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 11 18:30:21 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 11 18:30:21 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 11 18:30:21 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 11 18:30:21 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 11 18:30:21 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 11 18:30:21 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 11 18:30:21 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 11 18:30:21 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 11 18:30:21 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 11 18:30:21 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 11 18:30:21 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 11 18:30:21 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 11 18:30:21 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 11 18:30:21 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 11 18:30:21 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 11 18:30:21 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 11 18:30:21 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 
Sep 11 18:30:21 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 11 18:30:21 node-2 kernel: [    0.000000] Policy zone: Normal
Sep 11 18:30:21 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4ae3f936-c6bd-4661-b29f-0fa5a7d189a1 nomdmonddf nomdmonisw
Sep 11 18:30:21 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 11 18:30:21 node-2 kernel: [    0.000000] Checking aperture...
Sep 11 18:30:21 node-2 kernel: [    0.000000] No AGP bridge found
Sep 11 18:30:21 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 11 18:30:21 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 11 18:30:21 node-2 kernel: [    0.000000] Memory: 32653324K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Sep 11 18:30:21 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 11 18:30:21 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 11 18:30:21 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 11 18:30:21 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 11 18:30:21 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 11 18:30:21 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 11 18:30:21 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 11 18:30:21 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 11 18:30:21 node-2 kernel: [    0.000000] console [tty0] enabled
Sep 11 18:30:21 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 11 18:30:21 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 11 18:30:21 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 11 18:30:21 node-2 kernel: [    0.000000] hpet clockevent registered
Sep 11 18:30:21 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 11 18:30:21 node-2 kernel: [    0.004000] tsc: Detected 3491.929 MHz processor
Sep 11 18:30:21 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.85 BogoMIPS (lpj=13967716)
Sep 11 18:30:21 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 11 18:30:21 node-2 kernel: [    0.000043] Security Framework initialized
Sep 11 18:30:21 node-2 kernel: [    0.000062] AppArmor: AppArmor initialized
Sep 11 18:30:21 node-2 kernel: [    0.000063] Yama: becoming mindful.
Sep 11 18:30:21 node-2 kernel: [    0.001456] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.006403] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.008329] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.008357] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.008645] Initializing cgroup subsys memory
Sep 11 18:30:21 node-2 kernel: [    0.008653] Initializing cgroup subsys devices
Sep 11 18:30:21 node-2 kernel: [    0.008654] Initializing cgroup subsys freezer
Sep 11 18:30:21 node-2 kernel: [    0.008656] Initializing cgroup subsys blkio
Sep 11 18:30:21 node-2 kernel: [    0.008658] Initializing cgroup subsys perf_event
Sep 11 18:30:21 node-2 kernel: [    0.008660] Initializing cgroup subsys hugetlb
Sep 11 18:30:21 node-2 kernel: [    0.008680] CPU: Physical Processor ID: 0
Sep 11 18:30:21 node-2 kernel: [    0.008681] CPU: Processor Core ID: 0
Sep 11 18:30:21 node-2 kernel: [    0.008685] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 11 18:30:21 node-2 kernel: [    0.008685] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 11 18:30:21 node-2 kernel: [    0.009378] mce: CPU supports 22 MCE banks
Sep 11 18:30:21 node-2 kernel: [    0.009406] CPU0: Thermal monitoring enabled (TM1)
Sep 11 18:30:21 node-2 kernel: [    0.009426] process: using mwait in idle threads
Sep 11 18:30:21 node-2 kernel: [    0.009429] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 11 18:30:21 node-2 kernel: [    0.009429] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 11 18:30:21 node-2 kernel: [    0.009429] tlb_flushall_shift: 6
Sep 11 18:30:21 node-2 kernel: [    0.009518] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 11 18:30:21 node-2 kernel: [    0.010244] ACPI: Core revision 20131115
Sep 11 18:30:21 node-2 kernel: [    0.022949] ACPI: All ACPI Tables successfully acquired
Sep 11 18:30:21 node-2 kernel: [    0.023110] ftrace: allocating 28617 entries in 112 pages
Sep 11 18:30:21 node-2 kernel: [    0.032075] dmar: Host address width 46
Sep 11 18:30:21 node-2 kernel: [    0.032078] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 11 18:30:21 node-2 kernel: [    0.032084] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 11 18:30:21 node-2 kernel: [    0.032085] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 11 18:30:21 node-2 kernel: [    0.032089] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 11 18:30:21 node-2 kernel: [    0.032091] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 11 18:30:21 node-2 kernel: [    0.032092] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 11 18:30:21 node-2 kernel: [    0.032093] dmar: ATSR flags: 0x0
Sep 11 18:30:21 node-2 kernel: [    0.032094] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 11 18:30:21 node-2 kernel: [    0.032095] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 11 18:30:21 node-2 kernel: [    0.032210] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 11 18:30:21 node-2 kernel: [    0.032212] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 11 18:30:21 node-2 kernel: [    0.032213] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 11 18:30:21 node-2 kernel: [    0.032214] HPET id 0 under DRHD base 0xc7ffc000
Sep 11 18:30:21 node-2 kernel: [    0.032215] Your BIOS is broken and requested that x2apic be disabled.
Sep 11 18:30:21 node-2 kernel: [    0.032215] This will slightly decrease performance.
Sep 11 18:30:21 node-2 kernel: [    0.032215] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 11 18:30:21 node-2 kernel: [    0.032647] Enabled IRQ remapping in xapic mode
Sep 11 18:30:21 node-2 kernel: [    0.032648] x2apic not enabled, IRQ remapping is in xapic mode
Sep 11 18:30:21 node-2 kernel: [    0.032652] Switched APIC routing to physical flat.
Sep 11 18:30:21 node-2 kernel: [    0.033269] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 11 18:30:21 node-2 kernel: [    0.072919] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 11 18:30:21 node-2 kernel: [    0.072925] TSC deadline timer enabled
Sep 11 18:30:21 node-2 kernel: [    0.072933] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 11 18:30:21 node-2 kernel: [    0.072939] ... version:                3
Sep 11 18:30:21 node-2 kernel: [    0.072940] ... bit width:              48
Sep 11 18:30:21 node-2 kernel: [    0.072941] ... generic registers:      4
Sep 11 18:30:21 node-2 kernel: [    0.072942] ... value mask:             0000ffffffffffff
Sep 11 18:30:21 node-2 kernel: [    0.072943] ... max period:             0000ffffffffffff
Sep 11 18:30:21 node-2 kernel: [    0.072944] ... fixed-purpose events:   3
Sep 11 18:30:21 node-2 kernel: [    0.072945] ... event mask:             000000070000000f
Sep 11 18:30:21 node-2 kernel: [    0.074315] x86: Booting SMP configuration:
Sep 11 18:30:21 node-2 kernel: [    0.088419] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 11 18:30:21 node-2 kernel: [    0.074317] .... node  #0, CPUs:        #1  #2  #3
Sep 11 18:30:21 node-2 kernel: [    0.116326] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 11 18:30:21 node-2 kernel: [    0.270479] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 11 18:30:21 node-2 kernel: [    0.326148] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 11 18:30:21 node-2 kernel: [    0.383198] x86: Booted up 2 nodes, 16 CPUs
Sep 11 18:30:21 node-2 kernel: [    0.383201] smpboot: Total of 16 processors activated (111753.62 BogoMIPS)
Sep 11 18:30:21 node-2 kernel: [    0.407924] devtmpfs: initialized
Sep 11 18:30:21 node-2 kernel: [    0.411019] EVM: security.selinux
Sep 11 18:30:21 node-2 kernel: [    0.411021] EVM: security.SMACK64
Sep 11 18:30:21 node-2 kernel: [    0.411022] EVM: security.ima
Sep 11 18:30:21 node-2 kernel: [    0.411023] EVM: security.capability
Sep 11 18:30:21 node-2 kernel: [    0.411074] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.411767] pinctrl core: initialized pinctrl subsystem
Sep 11 18:30:21 node-2 kernel: [    0.411828] regulator-dummy: no parameters
Sep 11 18:30:21 node-2 kernel: [    0.411860] RTC time: 18:29:44, date: 09/11/16
Sep 11 18:30:21 node-2 kernel: [    0.411894] NET: Registered protocol family 16
Sep 11 18:30:21 node-2 kernel: [    0.411980] cpuidle: using governor ladder
Sep 11 18:30:21 node-2 kernel: [    0.411982] cpuidle: using governor menu
Sep 11 18:30:21 node-2 kernel: [    0.412018] ACPI: bus type PCI registered
Sep 11 18:30:21 node-2 kernel: [    0.412020] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 11 18:30:21 node-2 kernel: [    0.412063] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 11 18:30:21 node-2 kernel: [    0.412066] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 11 18:30:21 node-2 kernel: [    0.425797] PCI: Using configuration type 1 for base access
Sep 11 18:30:21 node-2 kernel: [    0.426789] bio: create slab <bio-0> at 0
Sep 11 18:30:21 node-2 kernel: [    0.427067] ACPI: Added _OSI(Module Device)
Sep 11 18:30:21 node-2 kernel: [    0.427068] ACPI: Added _OSI(Processor Device)
Sep 11 18:30:21 node-2 kernel: [    0.427069] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 11 18:30:21 node-2 kernel: [    0.427071] ACPI: Added _OSI(Processor Aggregator Device)
Sep 11 18:30:21 node-2 kernel: [    0.439761] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 11 18:30:21 node-2 kernel: [    0.450440] ACPI: Interpreter enabled
Sep 11 18:30:21 node-2 kernel: [    0.450445] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 11 18:30:21 node-2 kernel: [    0.450449] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 11 18:30:21 node-2 kernel: [    0.450452] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 11 18:30:21 node-2 kernel: [    0.450459] ACPI: (supports S0 S4 S5)
Sep 11 18:30:21 node-2 kernel: [    0.450460] ACPI: Using IOAPIC for interrupt routing
Sep 11 18:30:21 node-2 kernel: [    0.450504] HEST: Table parsing has been initialized.
Sep 11 18:30:21 node-2 kernel: [    0.450506] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 11 18:30:21 node-2 kernel: [    0.451060] ACPI: No dock devices found.
Sep 11 18:30:21 node-2 kernel: [    0.462757] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 11 18:30:21 node-2 kernel: [    0.462761] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 11 18:30:21 node-2 kernel: [    0.462765] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 11 18:30:21 node-2 kernel: [    0.462794] PCI host bridge to bus 0000:ff
Sep 11 18:30:21 node-2 kernel: [    0.462796] pci_bus 0000:ff: root bus resource [bus ff]
Sep 11 18:30:21 node-2 kernel: [    0.462804] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.462843] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.462874] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.462910] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.462940] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.462970] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.463002] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463031] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463063] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463092] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463118] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463145] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463173] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463200] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463227] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463254] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463282] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463310] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463337] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.463366] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463392] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.463418] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463445] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463475] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.463510] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463541] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463572] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463603] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463636] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463669] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463700] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463730] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463762] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463793] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463826] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463859] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463893] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463923] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463951] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.463983] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464016] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464055] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464090] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464124] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464153] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464182] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464214] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464245] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464277] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464309] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464341] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464371] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464401] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464432] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464462] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464494] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464526] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464588] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 11 18:30:21 node-2 kernel: [    0.464591] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 11 18:30:21 node-2 kernel: [    0.464594] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 11 18:30:21 node-2 kernel: [    0.464611] PCI host bridge to bus 0000:7f
Sep 11 18:30:21 node-2 kernel: [    0.464613] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 11 18:30:21 node-2 kernel: [    0.464618] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464645] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.464673] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464702] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464725] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.464749] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.464775] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464802] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464825] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464847] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464870] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464892] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464917] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464941] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464967] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.464997] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465019] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465042] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465065] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.465089] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465111] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.465133] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465157] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465185] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 11 18:30:21 node-2 kernel: [    0.465218] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465244] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465271] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465298] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465324] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465351] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465378] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465406] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465432] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465460] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465487] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465515] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465543] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465568] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465594] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465622] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465647] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465675] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465706] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465733] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465760] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465785] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465812] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465841] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465868] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465894] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465925] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465951] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465974] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.465999] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.466025] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.466054] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.466080] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.467323] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 11 18:30:21 node-2 kernel: [    0.467327] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 11 18:30:21 node-2 kernel: [    0.468444] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 11 18:30:21 node-2 kernel: [    0.468955] PCI host bridge to bus 0000:00
Sep 11 18:30:21 node-2 kernel: [    0.468958] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 11 18:30:21 node-2 kernel: [    0.468959] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 11 18:30:21 node-2 kernel: [    0.468961] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 11 18:30:21 node-2 kernel: [    0.468962] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 11 18:30:21 node-2 kernel: [    0.468963] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 11 18:30:21 node-2 kernel: [    0.468965] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 11 18:30:21 node-2 kernel: [    0.468966] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 11 18:30:21 node-2 kernel: [    0.468972] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 11 18:30:21 node-2 kernel: [    0.469054] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.469085] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.469127] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 11 18:30:21 node-2 kernel: [    0.469146] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.469175] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.469216] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 11 18:30:21 node-2 kernel: [    0.469234] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.469264] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.469304] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 11 18:30:21 node-2 kernel: [    0.469321] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.469391] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.469468] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.469543] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 11 18:30:21 node-2 kernel: [    0.469548] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 11 18:30:21 node-2 kernel: [    0.469634] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 11 18:30:21 node-2 kernel: [    0.469781] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 11 18:30:21 node-2 kernel: [    0.469799] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 11 18:30:21 node-2 kernel: [    0.469876] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.469931] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 11 18:30:21 node-2 kernel: [    0.469954] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.470009] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.470053] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 11 18:30:21 node-2 kernel: [    0.470081] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.470137] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.470180] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 11 18:30:21 node-2 kernel: [    0.470205] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 11 18:30:21 node-2 kernel: [    0.470223] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 11 18:30:21 node-2 kernel: [    0.470300] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.470350] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 11 18:30:21 node-2 kernel: [    0.470377] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 11 18:30:21 node-2 kernel: [    0.470627] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 11 18:30:21 node-2 kernel: [    0.470633] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 11 18:30:21 node-2 kernel: [    0.470639] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.470644] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.470652] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 11 18:30:21 node-2 kernel: [    0.470682] pci 0000:01:00.0: supports D1 D2
Sep 11 18:30:21 node-2 kernel: [    0.480554] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 11 18:30:21 node-2 kernel: [    0.480560] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 11 18:30:21 node-2 kernel: [    0.480564] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 11 18:30:21 node-2 kernel: [    0.480824] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.480857] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 11 18:30:21 node-2 kernel: [    0.488551] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 11 18:30:21 node-2 kernel: [    0.488557] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.488561] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 11 18:30:21 node-2 kernel: [    0.488646] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.488722] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.488817] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.488899] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 11 18:30:21 node-2 kernel: [    0.488907] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.488911] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 11 18:30:21 node-2 kernel: [    0.489002] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.489125] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.489179] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 11 18:30:21 node-2 kernel: [    0.489182] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.489184] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.489233] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.489355] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.489397] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.489516] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.489555] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.489674] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.489713] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 11 18:30:21 node-2 kernel: [    0.489834] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 11 18:30:21 node-2 kernel: [    0.489878] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 11 18:30:21 node-2 kernel: [    0.489880] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.489882] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.489952] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 11 18:30:21 node-2 kernel: [    0.490016] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.490068] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.490110] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 11 18:30:21 node-2 kernel: [    0.490192] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 11 18:30:21 node-2 kernel: [    0.490298] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 11 18:30:21 node-2 kernel: [    0.490301] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.490303] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.490359] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 11 18:30:21 node-2 kernel: [    0.490412] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.490460] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.490674] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 11 18:30:21 node-2 kernel: [    0.490678] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 11 18:30:21 node-2 kernel: [    0.490741] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 11 18:30:21 node-2 kernel: [    0.490796] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.490845] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.491081] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 11 18:30:21 node-2 kernel: [    0.491085] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 11 18:30:21 node-2 kernel: [    0.491143] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 11 18:30:21 node-2 kernel: [    0.491204] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.491256] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 11 18:30:21 node-2 kernel: [    0.491482] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 11 18:30:21 node-2 kernel: [    0.491486] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 11 18:30:21 node-2 kernel: [    0.491661] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 11 18:30:21 node-2 kernel: [    0.491699] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 11 18:30:21 node-2 kernel: [    0.491777] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 11 18:30:21 node-2 kernel: [    0.491795] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 11 18:30:21 node-2 kernel: [    0.491809] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 11 18:30:21 node-2 kernel: [    0.491822] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 11 18:30:21 node-2 kernel: [    0.491872] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 11 18:30:21 node-2 kernel: [    0.496557] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 11 18:30:21 node-2 kernel: [    0.496566] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 11 18:30:21 node-2 kernel: [    0.496619] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 11 18:30:21 node-2 kernel: [    0.497369] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 11 18:30:21 node-2 kernel: [    0.497372] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 11 18:30:21 node-2 kernel: [    0.497492] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 11 18:30:21 node-2 kernel: [    0.497601] PCI host bridge to bus 0000:80
Sep 11 18:30:21 node-2 kernel: [    0.497603] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 11 18:30:21 node-2 kernel: [    0.497604] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 11 18:30:21 node-2 kernel: [    0.497606] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 11 18:30:21 node-2 kernel: [    0.497614] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.497677] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.497746] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 11 18:30:21 node-2 kernel: [    0.497809] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 11 18:30:21 node-2 kernel: [    0.497814] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 11 18:30:21 node-2 kernel: [    0.497887] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 11 18:30:21 node-2 kernel: [    0.498185] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 11 18:30:21 node-2 kernel: [    0.498216] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 11 18:30:21 node-2 kernel: [    0.498246] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 11 18:30:21 node-2 kernel: [    0.498275] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 11 18:30:21 node-2 kernel: [    0.498305] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 11 18:30:21 node-2 kernel: [    0.498335] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 11 18:30:21 node-2 kernel: [    0.498365] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 11 18:30:21 node-2 kernel: [    0.498394] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 11 18:30:21 node-2 kernel: [    0.498479] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 11 18:30:21 node-2 kernel: [    0.498484] ACPI: \_SB_.UNC1: notify handler is installed
Sep 11 18:30:21 node-2 kernel: [    0.498485] ACPI: \_SB_.UNC0: notify handler is installed
Sep 11 18:30:21 node-2 kernel: [    0.498500] ACPI: \_SB_.PCI0: notify handler is installed
Sep 11 18:30:21 node-2 kernel: [    0.498553] ACPI: \_SB_.PCI1: notify handler is installed
Sep 11 18:30:21 node-2 kernel: [    0.498632] Found 4 acpi root devices
Sep 11 18:30:21 node-2 kernel: [    0.498742] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 11 18:30:21 node-2 kernel: [    0.498744] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 11 18:30:21 node-2 kernel: [    0.498746] vgaarb: loaded
Sep 11 18:30:21 node-2 kernel: [    0.498747] vgaarb: bridge control possible 0000:0c:00.0
Sep 11 18:30:21 node-2 kernel: [    0.498866] SCSI subsystem initialized
Sep 11 18:30:21 node-2 kernel: [    0.498930] libata version 3.00 loaded.
Sep 11 18:30:21 node-2 kernel: [    0.498945] ACPI: bus type USB registered
Sep 11 18:30:21 node-2 kernel: [    0.498955] usbcore: registered new interface driver usbfs
Sep 11 18:30:21 node-2 kernel: [    0.498960] usbcore: registered new interface driver hub
Sep 11 18:30:21 node-2 kernel: [    0.498984] usbcore: registered new device driver usb
Sep 11 18:30:21 node-2 kernel: [    0.499155] PCI: Using ACPI for IRQ routing
Sep 11 18:30:21 node-2 kernel: [    0.502744] PCI: pci_cache_line_size set to 64 bytes
Sep 11 18:30:21 node-2 kernel: [    0.502968] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 11 18:30:21 node-2 kernel: [    0.502969] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 11 18:30:21 node-2 kernel: [    0.502970] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 11 18:30:21 node-2 kernel: [    0.503034] NetLabel: Initializing
Sep 11 18:30:21 node-2 kernel: [    0.503035] NetLabel:  domain hash size = 128
Sep 11 18:30:21 node-2 kernel: [    0.503036] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 11 18:30:21 node-2 kernel: [    0.503045] NetLabel:  unlabeled traffic allowed by default
Sep 11 18:30:21 node-2 kernel: [    0.503114] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 11 18:30:21 node-2 kernel: [    0.503118] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 11 18:30:21 node-2 kernel: [    0.505174] Switched to clocksource hpet
Sep 11 18:30:21 node-2 kernel: [    0.509082] AppArmor: AppArmor Filesystem Enabled
Sep 11 18:30:21 node-2 kernel: [    0.509095] pnp: PnP ACPI init
Sep 11 18:30:21 node-2 kernel: [    0.509101] ACPI: bus type PNP registered
Sep 11 18:30:21 node-2 kernel: [    0.509223] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509231] pnp 00:01: [dma 4]
Sep 11 18:30:21 node-2 kernel: [    0.509243] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509269] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509288] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509306] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509339] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509390] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509392] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 11 18:30:21 node-2 kernel: [    0.509394] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509396] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509397] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509401] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509403] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 11 18:30:21 node-2 kernel: [    0.509405] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509406] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509408] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509409] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509411] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509412] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 11 18:30:21 node-2 kernel: [    0.509415] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509498] pnp 00:07: [dma 0 disabled]
Sep 11 18:30:21 node-2 kernel: [    0.509527] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509601] pnp 00:08: [dma 0 disabled]
Sep 11 18:30:21 node-2 kernel: [    0.509633] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 11 18:30:21 node-2 kernel: [    0.509684] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 11 18:30:21 node-2 kernel: [    0.510035] pnp: PnP ACPI: found 10 devices
Sep 11 18:30:21 node-2 kernel: [    0.510037] ACPI: bus type PNP unregistered
Sep 11 18:30:21 node-2 kernel: [    0.516336] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 11 18:30:21 node-2 kernel: [    0.516339] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 11 18:30:21 node-2 kernel: [    0.516341] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 11 18:30:21 node-2 kernel: [    0.516346] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 11 18:30:21 node-2 kernel: [    0.516348] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516362] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516391] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 11 18:30:21 node-2 kernel: [    0.516406] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516434] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 11 18:30:21 node-2 kernel: [    0.516449] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 11 18:30:21 node-2 kernel: [    0.516477] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 11 18:30:21 node-2 kernel: [    0.516492] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 11 18:30:21 node-2 kernel: [    0.516521] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 11 18:30:21 node-2 kernel: [    0.516523] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516540] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516569] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 11 18:30:21 node-2 kernel: [    0.516571] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516586] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516614] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 11 18:30:21 node-2 kernel: [    0.516616] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516619] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516623] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 11 18:30:21 node-2 kernel: [    0.516624] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516627] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516630] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 11 18:30:21 node-2 kernel: [    0.516635] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 11 18:30:21 node-2 kernel: [    0.516643] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 11 18:30:21 node-2 kernel: [    0.516647] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 11 18:30:21 node-2 kernel: [    0.516653] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 11 18:30:21 node-2 kernel: [    0.516654] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 11 18:30:21 node-2 kernel: [    0.516655] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 11 18:30:21 node-2 kernel: [    0.516656] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 11 18:30:21 node-2 kernel: [    0.516656] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 11 18:30:21 node-2 kernel: [    0.516657] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 11 18:30:21 node-2 kernel: [    0.516658] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 11 18:30:21 node-2 kernel: [    0.516659] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 11 18:30:21 node-2 kernel: [    0.516660] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516661] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516662] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516663] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516663] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516664] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516665] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516666] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516667] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 11 18:30:21 node-2 kernel: [    0.516668] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516669] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 11 18:30:21 node-2 kernel: [    0.516670] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 11 18:30:21 node-2 kernel: [    0.516671] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 11 18:30:21 node-2 kernel: [    0.516672] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 11 18:30:21 node-2 kernel: [    0.516674] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 11 18:30:21 node-2 kernel: [    0.516675] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 11 18:30:21 node-2 kernel: [    0.516711] NET: Registered protocol family 2
Sep 11 18:30:21 node-2 kernel: [    0.516967] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.517301] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.517444] TCP: Hash tables configured (established 262144 bind 65536)
Sep 11 18:30:21 node-2 kernel: [    0.517480] TCP: reno registered
Sep 11 18:30:21 node-2 kernel: [    0.517510] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.517604] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.517751] NET: Registered protocol family 1
Sep 11 18:30:21 node-2 kernel: [    0.553278] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 11 18:30:21 node-2 kernel: [    0.553294] PCI: CLS 64 bytes, default 64
Sep 11 18:30:21 node-2 kernel: [    0.553370] Trying to unpack rootfs image as initramfs...
Sep 11 18:30:21 node-2 kernel: [    0.773715] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Sep 11 18:30:21 node-2 kernel: [    0.773760] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 11 18:30:21 node-2 kernel: [    0.773764] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 11 18:30:21 node-2 kernel: [    0.774189] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774195] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774200] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774206] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774215] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774226] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774235] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774244] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774252] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774261] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774267] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774274] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774280] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774288] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774296] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774303] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 11 18:30:21 node-2 kernel: [    0.774345] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 11 18:30:21 node-2 kernel: [    0.774348] Scanning for low memory corruption every 60 seconds
Sep 11 18:30:21 node-2 kernel: [    0.774654] Initialise system trusted keyring
Sep 11 18:30:21 node-2 kernel: [    0.774699] audit: initializing netlink socket (disabled)
Sep 11 18:30:21 node-2 kernel: [    0.774709] type=2000 audit(1473618584.728:1): initialized
Sep 11 18:30:21 node-2 kernel: [    0.792515] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 11 18:30:21 node-2 kernel: [    0.794017] zbud: loaded
Sep 11 18:30:21 node-2 kernel: [    0.794134] VFS: Disk quotas dquot_6.5.2
Sep 11 18:30:21 node-2 kernel: [    0.794174] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 11 18:30:21 node-2 kernel: [    0.794544] fuse init (API version 7.22)
Sep 11 18:30:21 node-2 kernel: [    0.794600] msgmni has been set to 32768
Sep 11 18:30:21 node-2 kernel: [    0.794645] Key type big_key registered
Sep 11 18:30:21 node-2 kernel: [    0.795157] Key type asymmetric registered
Sep 11 18:30:21 node-2 kernel: [    0.795158] Asymmetric key parser 'x509' registered
Sep 11 18:30:21 node-2 kernel: [    0.795180] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 11 18:30:21 node-2 kernel: [    0.795251] io scheduler noop registered
Sep 11 18:30:21 node-2 kernel: [    0.795253] io scheduler deadline registered (default)
Sep 11 18:30:21 node-2 kernel: [    0.795268] io scheduler cfq registered
Sep 11 18:30:21 node-2 kernel: [    0.795583] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    0.795674] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    0.795762] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    0.795849] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    0.795945] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    0.796012] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    0.796277] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 11 18:30:21 node-2 kernel: [    0.796295] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 11 18:30:21 node-2 kernel: [    0.796308] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 11 18:30:21 node-2 kernel: [    0.796318] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796320] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796323] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 11 18:30:21 node-2 kernel: [    0.796326] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796328] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796329] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796330] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796332] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796333] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796334] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796336] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796337] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796339] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796340] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796342] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796344] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 11 18:30:21 node-2 kernel: [    0.796348] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796350] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 11 18:30:21 node-2 kernel: [    0.796358] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796361] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 11 18:30:21 node-2 kernel: [    0.796371] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796372] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 11 18:30:21 node-2 kernel: [    0.796375] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 11 18:30:21 node-2 kernel: [    0.796388] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 11 18:30:21 node-2 kernel: [    0.796476] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 11 18:30:21 node-2 kernel: [    0.796480] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 11 18:30:21 node-2 kernel: [    0.796489] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 11 18:30:21 node-2 kernel: [    0.796525] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 11 18:30:21 node-2 kernel: [    0.796526] vesafb: scrolling: redraw
Sep 11 18:30:21 node-2 kernel: [    0.796528] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 11 18:30:21 node-2 kernel: [    0.817147] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 11 18:30:21 node-2 kernel: [    0.825661] Console: switching to colour frame buffer device 80x30
Sep 11 18:30:21 node-2 kernel: [    0.834353] fb0: VESA VGA frame buffer device
Sep 11 18:30:21 node-2 kernel: [    0.834550] intel_idle: MWAIT substates: 0x2120
Sep 11 18:30:21 node-2 kernel: [    0.834551] intel_idle: v0.4 model 0x3F
Sep 11 18:30:21 node-2 kernel: [    0.834552] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 11 18:30:21 node-2 kernel: [    0.834787] ipmi message handler version 39.2
Sep 11 18:30:21 node-2 kernel: [    0.835050] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 11 18:30:21 node-2 kernel: [    0.835487] ACPI: AC Adapter [P111] (on-line)
Sep 11 18:30:21 node-2 kernel: [    0.840708] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 11 18:30:21 node-2 kernel: [    0.851708] ACPI: Power Button [PWRB]
Sep 11 18:30:21 node-2 kernel: [    0.857504] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 11 18:30:21 node-2 kernel: [    0.869217] ACPI: Power Button [PWRF]
Sep 11 18:30:21 node-2 kernel: [    0.894862] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 11 18:30:21 node-2 kernel: [    0.906522] pstore: Registered erst as persistent store backend
Sep 11 18:30:21 node-2 kernel: [    0.912721] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 11 18:30:21 node-2 kernel: [    0.924671] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 11 18:30:21 node-2 kernel: [    0.951433] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 11 18:30:21 node-2 kernel: [    0.984729] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 11 18:30:21 node-2 kernel: [    0.998822] Linux agpgart interface v0.103
Sep 11 18:30:21 node-2 kernel: [    1.006474] brd: module loaded
Sep 11 18:30:21 node-2 kernel: [    1.013548] loop: module loaded
Sep 11 18:30:21 node-2 kernel: [    1.020290] libphy: Fixed MDIO Bus: probed
Sep 11 18:30:21 node-2 kernel: [    1.026751] tun: Universal TUN/TAP device driver, 1.6
Sep 11 18:30:21 node-2 kernel: [    1.033247] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 11 18:30:21 node-2 kernel: [    1.039772] PPP generic driver version 2.4.2
Sep 11 18:30:21 node-2 kernel: [    1.046151] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 11 18:30:21 node-2 kernel: [    1.052586] ehci-pci: EHCI PCI platform driver
Sep 11 18:30:21 node-2 kernel: [    1.059173] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 11 18:30:21 node-2 kernel: [    1.065588] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 11 18:30:21 node-2 kernel: [    1.078120] ehci-pci 0000:00:1a.0: debug port 2
Sep 11 18:30:21 node-2 kernel: [    1.088319] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 11 18:30:21 node-2 kernel: [    1.088336] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 11 18:30:21 node-2 kernel: [    1.104670] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 11 18:30:21 node-2 kernel: [    1.110747] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 11 18:30:21 node-2 kernel: [    1.116923] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 11 18:30:21 node-2 kernel: [    1.128892] usb usb1: Product: EHCI Host Controller
Sep 11 18:30:21 node-2 kernel: [    1.134930] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 11 18:30:21 node-2 kernel: [    1.140993] usb usb1: SerialNumber: 0000:00:1a.0
Sep 11 18:30:21 node-2 kernel: [    1.146949] hub 1-0:1.0: USB hub found
Sep 11 18:30:21 node-2 kernel: [    1.152730] hub 1-0:1.0: 2 ports detected
Sep 11 18:30:21 node-2 kernel: [    1.158531] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 11 18:30:21 node-2 kernel: [    1.164119] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 11 18:30:21 node-2 kernel: [    1.175042] ehci-pci 0000:00:1d.0: debug port 2
Sep 11 18:30:21 node-2 kernel: [    1.184366] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 11 18:30:21 node-2 kernel: [    1.184369] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 11 18:30:21 node-2 kernel: [    1.200588] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 11 18:30:21 node-2 kernel: [    1.205814] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 11 18:30:21 node-2 kernel: [    1.211128] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 11 18:30:21 node-2 kernel: [    1.221726] usb usb2: Product: EHCI Host Controller
Sep 11 18:30:21 node-2 kernel: [    1.227208] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 11 18:30:21 node-2 kernel: [    1.232829] usb usb2: SerialNumber: 0000:00:1d.0
Sep 11 18:30:21 node-2 kernel: [    1.238442] hub 2-0:1.0: USB hub found
Sep 11 18:30:21 node-2 kernel: [    1.243855] hub 2-0:1.0: 2 ports detected
Sep 11 18:30:21 node-2 kernel: [    1.249160] ehci-platform: EHCI generic platform driver
Sep 11 18:30:21 node-2 kernel: [    1.254400] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 11 18:30:21 node-2 kernel: [    1.259716] ohci-pci: OHCI PCI platform driver
Sep 11 18:30:21 node-2 kernel: [    1.265026] ohci-platform: OHCI generic platform driver
Sep 11 18:30:21 node-2 kernel: [    1.270209] uhci_hcd: USB Universal Host Controller Interface driver
Sep 11 18:30:21 node-2 kernel: [    1.275551] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 11 18:30:21 node-2 kernel: [    1.468368] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 11 18:30:21 node-2 kernel: [    1.632612] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 11 18:30:21 node-2 kernel: [    1.638121] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 11 18:30:21 node-2 kernel: [    1.643875] hub 1-1:1.0: USB hub found
Sep 11 18:30:21 node-2 kernel: [    1.649347] hub 1-1:1.0: 6 ports detected
Sep 11 18:30:21 node-2 kernel: [    1.764109] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 11 18:30:21 node-2 kernel: [    1.772127] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 11 18:30:21 node-2 kernel: [    2.032271] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 11 18:30:21 node-2 kernel: [    2.037825] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 11 18:30:21 node-2 kernel: [    2.043664] hub 2-1:1.0: USB hub found
Sep 11 18:30:21 node-2 kernel: [    2.049383] hub 2-1:1.0: 8 ports detected
Sep 11 18:30:21 node-2 kernel: [    2.316970] i8042: No controller found
Sep 11 18:30:21 node-2 kernel: [    2.322369] mousedev: PS/2 mouse device common for all mice
Sep 11 18:30:21 node-2 kernel: [    2.327753] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 11 18:30:21 node-2 kernel: [    2.333476] rtc_cmos 00:02: RTC can wake from S4
Sep 11 18:30:21 node-2 kernel: [    2.339221] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 11 18:30:21 node-2 kernel: [    2.344835] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 11 18:30:21 node-2 kernel: [    2.355936] device-mapper: uevent: version 1.0.3
Sep 11 18:30:21 node-2 kernel: [    2.361569] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 11 18:30:21 node-2 kernel: [    2.372804] ledtrig-cpu: registered to indicate activity on CPUs
Sep 11 18:30:21 node-2 kernel: [    2.378830] TCP: cubic registered
Sep 11 18:30:21 node-2 kernel: [    2.384733] NET: Registered protocol family 10
Sep 11 18:30:21 node-2 kernel: [    2.390708] NET: Registered protocol family 17
Sep 11 18:30:21 node-2 kernel: [    2.396386] Key type dns_resolver registered
Sep 11 18:30:21 node-2 kernel: [    2.402342] Loading compiled-in X.509 certificates
Sep 11 18:30:21 node-2 kernel: [    2.408526] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 11 18:30:21 node-2 kernel: [    2.419940] registered taskstats version 1
Sep 11 18:30:21 node-2 kernel: [    2.427902] Key type trusted registered
Sep 11 18:30:21 node-2 kernel: [    2.435439] Key type encrypted registered
Sep 11 18:30:21 node-2 kernel: [    2.440906] AppArmor: AppArmor sha1 policy hashing enabled
Sep 11 18:30:21 node-2 kernel: [    2.446388] IMA: No TPM chip found, activating TPM-bypass!
Sep 11 18:30:21 node-2 kernel: [    2.452547] regulator-dummy: disabling
Sep 11 18:30:21 node-2 kernel: [    2.458130]   Magic number: 0:680:493
Sep 11 18:30:21 node-2 kernel: [    2.463784] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 11 18:30:21 node-2 kernel: [    2.469336] rtc_cmos 00:02: setting system clock to 2016-09-11 18:29:46 UTC (1473618586)
Sep 11 18:30:21 node-2 kernel: [    2.469338] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 11 18:30:21 node-2 kernel: [    2.469339] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 11 18:30:21 node-2 kernel: [    2.469340] usb 2-1.4: Manufacturer: Avocent
Sep 11 18:30:21 node-2 kernel: [    2.469341] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 11 18:30:21 node-2 kernel: [    2.510947] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 11 18:30:21 node-2 kernel: [    2.516773] EDD information not available.
Sep 11 18:30:21 node-2 kernel: [    2.522569] PM: Hibernation image not present or could not be loaded.
Sep 11 18:30:21 node-2 kernel: [    2.523427] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 11 18:30:21 node-2 kernel: [    2.535006] Write protecting the kernel read-only data: 12288k
Sep 11 18:30:21 node-2 kernel: [    2.541393] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 11 18:30:21 node-2 kernel: [    2.554135] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 11 18:30:21 node-2 kernel: [    2.587413] device-mapper: multipath: version 1.6.0 loaded
Sep 11 18:30:21 node-2 kernel: [    2.595686] systemd-udevd[216]: starting version 204
Sep 11 18:30:21 node-2 kernel: [    2.619153] md: linear personality registered for level -1
Sep 11 18:30:21 node-2 kernel: [    2.634410] md: multipath personality registered for level -4
Sep 11 18:30:21 node-2 kernel: [    2.642706] md: raid0 personality registered for level 0
Sep 11 18:30:21 node-2 kernel: [    2.651702] md: raid1 personality registered for level 1
Sep 11 18:30:21 node-2 kernel: [    2.660652] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 11 18:30:21 node-2 kernel: [    2.667207] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 11 18:30:21 node-2 kernel: [    2.668237] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 11 18:30:21 node-2 kernel: [    2.673243] megasas: FW now in Ready state
Sep 11 18:30:21 node-2 kernel: [    2.673675] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.673868] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.673988] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674126] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674244] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674374] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674521] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674648] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674779] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674884] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.674973] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.675072] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.675173] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.675306] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.675594] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.675682] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.676356] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 11 18:30:21 node-2 kernel: [    2.700017] hidraw: raw HID events driver (C) Jiri Kosina
Sep 11 18:30:21 node-2 kernel: [    2.709171] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 11 18:30:21 node-2 kernel: [    2.716290] usbcore: registered new interface driver usbhid
Sep 11 18:30:21 node-2 kernel: [    2.716291] usbhid: USB HID core driver
Sep 11 18:30:21 node-2 kernel: [    2.727588] raid6: sse2x1     938 MB/s
Sep 11 18:30:21 node-2 kernel: [    2.741643] 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
Sep 11 18:30:21 node-2 kernel: [    2.754953] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 11 18:30:21 node-2 kernel: [    2.761684] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.761690] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.761695] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.761700] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.761739] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 11 18:30:21 node-2 kernel: [    2.795249] raid6: sse2x2    3589 MB/s
Sep 11 18:30:21 node-2 kernel: [    2.867186] raid6: sse2x4   10138 MB/s
Sep 11 18:30:21 node-2 kernel: [    2.939125] raid6: avx2x1   14945 MB/s
Sep 11 18:30:21 node-2 kernel: [    3.011066] raid6: avx2x2   18853 MB/s
Sep 11 18:30:21 node-2 kernel: [    3.083007] raid6: avx2x4   21428 MB/s
Sep 11 18:30:21 node-2 kernel: [    3.088572] raid6: using algorithm avx2x4 (21428 MB/s)
Sep 11 18:30:21 node-2 kernel: [    3.094124] raid6: using avx2x2 recovery algorithm
Sep 11 18:30:21 node-2 kernel: [    3.099612] Switched to clocksource tsc
Sep 11 18:30:21 node-2 kernel: [    3.105799] xor: automatically using best checksumming function:
Sep 11 18:30:21 node-2 kernel: [    3.112038] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 11 18:30:21 node-2 kernel: [    3.122698] enic 0000:07: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
Sep 11 18:30:21 node-2 kernel: [    3.134177] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 11 18:30:21 node-2 kernel: [    3.140033] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.140037] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.140041] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.140045] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.140093] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.151092]    avx       : 35185.000 MB/sec
Sep 11 18:30:21 node-2 kernel: [    3.157646] async_tx: api initialized (async)
Sep 11 18:30:21 node-2 kernel: [    3.166829] 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
Sep 11 18:30:21 node-2 kernel: [    3.167412] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 11 18:30:21 node-2 kernel: [    3.167424] 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
Sep 11 18:30:21 node-2 kernel: [    3.167427] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 11 18:30:21 node-2 kernel: [    3.167731] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.167854] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.168034] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.168155] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.168358] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.181841] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 11 18:30:21 node-2 kernel: [    3.181849] 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
Sep 11 18:30:21 node-2 kernel: [    3.181868] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 11 18:30:21 node-2 kernel: [    3.182085] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.182167] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.182258] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.182359] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.182559] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 11 18:30:21 node-2 kernel: [    3.260732] 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
Sep 11 18:30:21 node-2 kernel: [    3.260942] md: raid6 personality registered for level 6
Sep 11 18:30:21 node-2 kernel: [    3.260942] md: raid5 personality registered for level 5
Sep 11 18:30:21 node-2 kernel: [    3.260943] md: raid4 personality registered for level 4
Sep 11 18:30:21 node-2 kernel: [    3.295058] 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
Sep 11 18:30:21 node-2 kernel: [    3.308386] 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
Sep 11 18:30:21 node-2 kernel: [    3.321738] 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
Sep 11 18:30:21 node-2 kernel: [    3.335651] md: raid10 personality registered for level 10
Sep 11 18:30:21 node-2 kernel: [    3.336288] 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
Sep 11 18:30:21 node-2 kernel: [    3.408508] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Sep 11 18:30:21 node-2 kernel: [    3.822428] megasas:IOC Init cmd success
Sep 11 18:30:21 node-2 kernel: [    3.874429] megasas: INIT adapter done
Sep 11 18:30:21 node-2 kernel: [    3.950305] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 11 18:30:21 node-2 kernel: [    3.957141] scsi0 : LSI SAS based MegaRAID driver
Sep 11 18:30:21 node-2 kernel: [    3.964771] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 11 18:30:21 node-2 kernel: [    3.984010] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 11 18:30:21 node-2 kernel: [    3.999611] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 11 18:30:21 node-2 kernel: [    4.006300] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 11 18:30:21 node-2 kernel: [    4.019756] sd 0:2:0:0: [sda] Write Protect is off
Sep 11 18:30:21 node-2 kernel: [    4.026698] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 11 18:30:21 node-2 kernel: [    4.026717] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 11 18:30:21 node-2 kernel: [    4.070541]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 11 18:30:21 node-2 kernel: [    4.077822] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 11 18:30:21 node-2 kernel: [    4.222497] random: lvm urandom read with 30 bits of entropy available
Sep 11 18:30:21 node-2 kernel: [    4.359483] bio: create slab <bio-1> at 1
Sep 11 18:30:21 node-2 kernel: [    5.129824] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 11 18:30:21 node-2 kernel: [    5.860780] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 11 18:30:21 node-2 kernel: [    5.918491] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 11 18:30:21 node-2 kernel: [    6.050337] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 11 18:30:21 node-2 kernel: [    6.080301] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 11 18:30:21 node-2 kernel: [    6.132481] random: nonblocking pool is initialized
Sep 11 18:30:21 node-2 kernel: [    6.240172] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 11 18:30:21 node-2 kernel: [    6.370349] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 11 18:30:21 node-2 kernel: [    6.401645] XFS (dm-0): Mounting Filesystem
Sep 11 18:30:21 node-2 kernel: [    6.601921] XFS (dm-0): Ending clean mount
Sep 11 18:30:21 node-2 kernel: [    6.639484] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 11 18:30:21 node-2 kernel: [    6.691848] XFS (dm-1): Mounting Filesystem
Sep 11 18:30:21 node-2 kernel: [    6.810176] XFS (dm-1): Ending clean mount
Sep 11 18:30:21 node-2 kernel: [    8.829145] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 11 18:30:21 node-2 kernel: [    8.857580] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 11 18:30:21 node-2 kernel: [    9.001424] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 11 18:30:21 node-2 kernel: [    9.001457] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 11 18:30:21 node-2 kernel: [    9.001462] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 11 18:30:21 node-2 kernel: [    9.001466] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 11 18:30:21 node-2 kernel: [    9.051410] systemd-udevd[776]: starting version 204
Sep 11 18:30:21 node-2 kernel: [    9.291350] power_meter ACPI000D:00: Found ACPI power meter.
Sep 11 18:30:21 node-2 kernel: [    9.291393] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 11 18:30:21 node-2 kernel: [    9.312666] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 11 18:30:21 node-2 kernel: [    9.312671] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 11 18:30:21 node-2 kernel: [    9.312674] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 11 18:30:21 node-2 kernel: [    9.312676] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 11 18:30:21 node-2 kernel: [    9.312702] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 11 18:30:21 node-2 kernel: [    9.332266] wmi: Mapper loaded
Sep 11 18:30:21 node-2 kernel: [    9.344785] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 11 18:30:21 node-2 kernel: [    9.352547] IPMI System Interface driver.
Sep 11 18:30:21 node-2 kernel: [    9.352581] ipmi_si: probing via ACPI
Sep 11 18:30:21 node-2 kernel: [    9.352598] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 11 18:30:21 node-2 kernel: [    9.352599] ipmi_si: Adding ACPI-specified kcs state machine
Sep 11 18:30:21 node-2 kernel: [    9.352606] ipmi_si: probing via SMBIOS
Sep 11 18:30:21 node-2 kernel: [    9.352607] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 11 18:30:21 node-2 kernel: [    9.352608] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 11 18:30:21 node-2 kernel: [    9.352609] ipmi_si: probing via SPMI
Sep 11 18:30:21 node-2 kernel: [    9.352610] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 11 18:30:21 node-2 kernel: [    9.352610] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 11 18:30:21 node-2 kernel: [    9.352612] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 11 18:30:21 node-2 kernel: [    9.402124] systemd-udevd[798]: renamed network interface eth2 to enp8s0
Sep 11 18:30:21 node-2 kernel: [    9.426549] systemd-udevd[794]: renamed network interface eth0 to enp6s0
Sep 11 18:30:21 node-2 kernel: [    9.456303] systemd-udevd[804]: renamed network interface eth1 to enp7s0
Sep 11 18:30:21 node-2 kernel: [    9.490021] systemd-udevd[795]: renamed network interface eth3 to enp9s0
Sep 11 18:30:21 node-2 kernel: [    9.541584] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 11 18:30:21 node-2 kernel: [    9.541589] ipmi_si 00:09: IPMI kcs interface initialized
Sep 11 18:30:21 node-2 kernel: [    9.793104] type=1400 audit(1473618593.829:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.793259] type=1400 audit(1473618593.829:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.793390] type=1400 audit(1473618593.833:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.804626] type=1400 audit(1473618593.841:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1058 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.804862] type=1400 audit(1473618593.841:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1058 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.805073] type=1400 audit(1473618593.841:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1058 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.808490] type=1400 audit(1473618593.845:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.808633] type=1400 audit(1473618593.845:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.808759] type=1400 audit(1473618593.845:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [    9.816373] type=1400 audit(1473618593.853:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Sep 11 18:30:21 node-2 kernel: [   10.314283] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 11 18:30:21 node-2 kernel: [   10.315732] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 11 18:30:21 node-2 kernel: [   10.528002] enic 0000:06:00.0 enp6s0: Link UP
Sep 11 18:30:21 node-2 kernel: [   10.529187] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 11 18:30:21 node-2 kernel: [   10.529191] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 11 18:30:21 node-2 kernel: [   19.771165] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 11 18:30:21 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 11 18:30:22 node-2 failsafe: Failsafe of 120 seconds reached.
Sep 11 18:30:22 node-2 kernel: [   38.648988] init: failsafe main process (8418) killed by TERM signal
Sep 11 18:30:23 node-2 dbus[8449]: [system] AppArmor D-Bus mediation is enabled
Sep 11 18:30:23 node-2 kernel: [   38.943031] audit_printk_skb: 30 callbacks suppressed
Sep 11 18:30:23 node-2 kernel: [   38.943033] type=1400 audit(1473618623.215:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8544 comm="apparmor_parser"
Sep 11 18:30:23 node-2 kernel: [   38.943297] type=1400 audit(1473618623.215:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8543 comm="apparmor_parser"
Sep 11 18:30:23 node-2 kernel: [   38.943301] type=1400 audit(1473618623.215:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Sep 11 18:30:23 node-2 kernel: [   38.943303] type=1400 audit(1473618623.215:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Sep 11 18:30:23 node-2 kernel: [   38.943537] type=1400 audit(1473618623.215:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Sep 11 18:30:23 node-2 kernel: [   38.943538] type=1400 audit(1473618623.215:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Sep 11 18:30:23 node-2 kernel: [   38.943650] type=1400 audit(1473618623.215:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Sep 11 18:30:23 node-2 kernel: [   39.037257] type=1400 audit(1473618623.307:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8546 comm="apparmor_parser"
Sep 11 18:30:23 node-2 cron[8577]: (CRON) INFO (pidfile fd = 3)
Sep 11 18:30:23 node-2 anacron[8595]: Anacron 2.3 started on 2016-09-11
Sep 11 18:30:23 node-2 cron[8600]: (CRON) STARTUP (fork ok)
Sep 11 18:30:23 node-2 anacron[8595]: Will run job `cron.daily' in 5 min.
Sep 11 18:30:23 node-2 anacron[8595]: Will run job `cron.weekly' in 10 min.
Sep 11 18:30:23 node-2 anacron[8595]: Will run job `cron.monthly' in 15 min.
Sep 11 18:30:23 node-2 anacron[8595]: Jobs will be executed sequentially
Sep 11 18:30:23 node-2 multipathd: path checkers start up
Sep 11 18:30:23 node-2 cron[8600]: (CRON) INFO (Running @reboot jobs)
Sep 11 18:30:23 node-2 postfix/master[8755]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 11 18:30:26 node-2 puppet-agent[8941]: Reopening log files
Sep 11 18:30:27 node-2 puppet-agent[8941]: Could not request certificate: Connection refused - connect(2)
Sep 11 18:30:42 node-2 puppet-user[9149]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 11 18:30:42 node-2 puppet-user[9149]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 11 18:30:43 node-2 puppet-user[9149]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 11 18:30:43 node-2 puppet-user[9149]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 11 18:30:43 node-2 puppet-user[9149]: Finished catalog run in 0.68 seconds
Sep 11 18:30:44 node-2 multipathd: uevent trigger error
Sep 11 18:30:44 node-2 puppet-user[9574]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 11 18:30:44 node-2 puppet-user[9574]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep 11 18:30:44 node-2 puppet-user[9574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 11 18:30:44 node-2 puppet-user[9574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 11 18:30:44 node-2 puppet-user[9574]: (/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"]'
Sep 11 18:30:44 node-2 puppet-user[9574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 11 18:30:44 node-2 puppet-user[9574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 11 18:30:44 node-2 puppet-user[9574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 11 18:30:44 node-2 puppet-user[9574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 11 18:30:44 node-2 puppet-user[9574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 11 18:30:45 node-2 puppet-user[9574]: Finished catalog run in 0.06 seconds
Sep 11 18:30:46 node-2 puppet-user[10031]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 11 18:30:46 node-2 puppet-user[10031]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep 11 18:30:46 node-2 puppet-user[10031]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 11 18:30:46 node-2 puppet-user[10031]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 11 18:30:46 node-2 puppet-user[10031]: Finished catalog run in 0.03 seconds
Sep 11 18:30:48 node-2 puppet-user[10489]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 11 18:30:48 node-2 puppet-user[10489]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 11 18:30:48 node-2 puppet-user[10489]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 11 18:30:48 node-2 puppet-user[10489]: Finished catalog run in 0.03 seconds
Sep 11 18:30:49 node-2 puppet-user[10936]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 11 18:30:49 node-2 puppet-user[10936]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Sep 11 18:30:49 node-2 puppet-user[10936]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 11 18:30:50 node-2 puppet-user[10936]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 11 18:30:50 node-2 puppet-user[10936]: Finished catalog run in 0.42 seconds
Sep 11 18:30:51 node-2 puppet-user[11590]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 11 18:30:51 node-2 puppet-user[11590]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Sep 11 18:30:51 node-2 puppet-user[11590]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 11 18:30:51 node-2 puppet-user[11590]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 11 18:30:51 node-2 puppet-user[11590]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 11 18:30:51 node-2 puppet-user[11590]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 11 18:30:52 node-2 puppet-user[11590]: Finished catalog run in 0.25 seconds
Sep 11 18:30:53 node-2 puppet-user[12063]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 11 18:30:53 node-2 puppet-user[12063]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Sep 11 18:30:53 node-2 puppet-user[12063]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 11 18:30:53 node-2 kernel: [   69.449728] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 11 18:30:53 node-2 kernel: [   69.449778] 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.
Sep 11 18:30:53 node-2 puppet-user[12063]: (/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'
Sep 11 18:30:53 node-2 puppet-user[12063]: Finished catalog run in 0.05 seconds
Sep 11 18:30:55 node-2 puppet-user[12520]: (Scope(Class[main])) MODULAR: sync_time
Sep 11 18:30:55 node-2 puppet-user[12520]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 11 18:30:55 node-2 ntpdate[12936]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 11 18:31:01 node-2 CRON[13073]: (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")
Sep 11 18:31:01 node-2 ntpdate[12936]: adjust time server 10.20.0.2 offset 0.006073 sec
Sep 11 18:31:01 node-2 puppet-user[12520]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 11 18:31:01 node-2 puppet-user[12520]: Finished catalog run in 6.16 seconds
Sep 11 18:31:02 node-2 kernel: [   77.855499] init: plymouth-upstart-bridge main process ended, respawning
Sep 11 18:31:02 node-2 puppet-agent[8941]: Could not run: SIGTERM
Sep 11 18:31:02 node-2 kernel: [   78.143603] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 11 18:31:02 node-2 ec2: 
Sep 11 18:31:02 node-2 ec2: #############################################################
Sep 11 18:31:02 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 11 18:31:02 node-2 ec2: 1024 b7:2d:70:8b:b3:ed:68:08:c3:52:b1:cf:ef:54:7e:d4  root@node-2.domain.tld (DSA)
Sep 11 18:31:02 node-2 ec2: 256 c7:4e:6a:95:0a:24:69:56:91:5e:2d:2c:9e:34:4d:da  root@node-2.domain.tld (ECDSA)
Sep 11 18:31:02 node-2 ec2: 256 d4:5e:aa:37:38:2b:f2:2a:43:77:a1:db:83:4a:43:62  root@node-2.domain.tld (ED25519)
Sep 11 18:31:02 node-2 ec2: 2048 77:d6:74:83:b2:80:98:67:8f:a7:ca:ae:a4:ad:b8:09  root@node-2.domain.tld (RSA)
Sep 11 18:31:02 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 11 18:31:02 node-2 ec2: #############################################################
Sep 11 18:31:07 node-2 puppet-user[13320]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 11 18:31:07 node-2 puppet-user[13320]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Sep 11 18:31:07 node-2 puppet-user[13320]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 11 18:31:07 node-2 puppet-user[13320]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Sep 11 18:31:07 node-2 puppet-user[13320]: Finished catalog run in 0.06 seconds
Sep 11 18:31:09 node-2 puppet-user[13778]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 11 18:31:10 node-2 puppet-user[13778]: Compiled catalog for node-2.domain.tld in environment production in 0.97 seconds
Sep 11 18:31:10 node-2 puppet-user[13778]: (/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
Sep 11 18:31:10 node-2 puppet-user[13778]: (/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
Sep 11 18:31:10 node-2 puppet-user[13778]: (/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
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/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
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/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
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Sep 11 18:31:10 node-2 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 11 18:31:13 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 11 18:31:13 node-2 nailgun-agent: D, [2016-09-11T18:31:01.696709 #13076] DEBUG -- : Sleep for 12 seconds before sending request
Sep 11 18:31:13 node-2 nailgun-agent: I, [2016-09-11T18:31:13.718981 #13076]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 11 18:31:14 node-2 nailgun-agent: D, [2016-09-11T18:31:14.106713 #13076] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.348431 #13076] DEBUG -- : Trying to find block devices
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.348742 #13076] DEBUG -- : Found block device: sda
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.348844 #13076] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.348902 #13076] DEBUG -- : Trying to get list of physical devices
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.349322 #13076] DEBUG -- : Getting udev properties for device: sda
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.352200 #13076] 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"=>"0x618e72837274ff201cc788
Sep 11 18:31:26 node-2 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35533", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.352275 #13076] DEBUG -- : Trying to find out if device sda is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.352394 #13076] DEBUG -- : Device sda removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.352440 #13076] DEBUG -- : Device sda seems to be appropriate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.353520 #13076] DEBUG -- : Getting udev properties for device: dm-0
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.356392 #13076] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-DZssbo4VsfebppgiuBS2Qa6D1tfo6Qe5mrbQRCBNkY5ooZrQTt2caCNqw8yNevhz /dev/disk/by-uuid/a395c14f-2960-40e0-ad8b-71a189994c0d /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-DZssbo4VsfebppgiuBS2Qa6D1tfo6Qe5mrbQRCBNkY5ooZrQTt2caCNqw8yNevhz", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a395c14f-2960-40e0-ad8b-71a189994c0d", "ID_FS_UUID_ENC"=>"a395c14f-2960-40e0-ad8b-71a189994c0d", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17533", "nomdmonddf"=>"1", "nom
Sep 11 18:31:26 node-2 nailgun-agent: dmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.356466 #13076] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.356598 #13076] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.356661 #13076] DEBUG -- : Device dm-0 seems to be appropriate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.356703 #13076] DEBUG -- : Getting udev properties for device: dm-1
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.359219 #13076] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-LDTJ3GScPmMMJOHiyJG6j82kzkau5hiYPKtnGYLCJlOY0JY2Ew85TYO7XzicIpEv /dev/disk/by-uuid/bf824669-cb61-43cc-9744-77bc09c05b29 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-LDTJ3GScPmMMJOHiyJG6j82kzkau5hiYPKtnGYLCJlOY0JY2Ew85TYO7XzicIpEv", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"bf824669-cb61-43cc-9744-77bc09c05b29", "ID_FS_UUID_ENC"=>"bf824669-cb61-43cc-9744-77bc09c05b29", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6
Sep 11 18:31:26 node-2 nailgun-agent: 6203", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.359280 #13076] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.359386 #13076] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.359418 #13076] DEBUG -- : Device dm-1 seems to be appropriate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.359448 #13076] DEBUG -- : Getting udev properties for device: dm-2
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.362749 #13076] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-2Tp2fNnOZyOQIVoIg7jGzmYCHYAK9r8KtNmYEfroV8sWPDPVz4Zg2dLqNv6cochr /dev/disk/by-uuid/9b8069c1-7271-45bf-bebb-ceb89917530c /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-2Tp2fNnOZyOQIVoIg7jGzmYCHYAK9r8KtNmYEfroV8sWPDPVz4Zg2dLqNv6cochr", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9b8069c1-7271-45bf-bebb-ceb89917530c", "ID_FS_UUID_ENC"=>"9b8069c1-7271-45bf-bebb-ceb89917530c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69460", "nomdmon
Sep 11 18:31:26 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.362809 #13076] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.362874 #13076] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.362935 #13076] DEBUG -- : Device dm-2 seems to be appropriate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.362965 #13076] DEBUG -- : Getting udev properties for device: dm-3
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.366182 #13076] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Vm3MBhIpWhunCjMJB0iVnsjl4zWnzUwYu41VTqi6YVLZughwdPo6uzOKRIUBWZX8 /dev/disk/by-uuid/0db3d74b-9832-45b8-a554-9550715aa834 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-Vm3MBhIpWhunCjMJB0iVnsjl4zWnzUwYu41VTqi6YVLZughwdPo6uzOKRIUBWZX8", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0db3d74b-9832-45b8-a554-9550715aa834", "ID_FS_UUID_ENC"=>"0db3d74b-9832-45b8-a554-9550715aa834", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73576", "nomdmonddf"=>"1",
Sep 11 18:31:26 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.366241 #13076] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.366309 #13076] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.366338 #13076] DEBUG -- : Device dm-3 seems to be appropriate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.366369 #13076] DEBUG -- : Getting udev properties for device: dm-4
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.369644 #13076] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-JfH5iYPwUIZh7Cc4fIBRETM6CtYD01tYflttLibxAlk3AXXhHdAiXVIt4LUbzYR0 /dev/disk/by-uuid/4ae3f936-c6bd-4661-b29f-0fa5a7d189a1 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-JfH5iYPwUIZh7Cc4fIBRETM6CtYD01tYflttLibxAlk3AXXhHdAiXVIt4LUbzYR0", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4ae3f936-c6bd-4661-b29f-0fa5a7d189a1", "ID_FS_UUID_ENC"=>"4ae3f936-c6bd-4661-b29f-0fa5a7d189a1", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75420", "nomdmonddf"=>"1", "nom
Sep 11 18:31:26 node-2 nailgun-agent: dmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.369703 #13076] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.369808 #13076] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.369840 #13076] DEBUG -- : Device dm-4 seems to be appropriate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.369890 #13076] DEBUG -- : Getting udev properties for device: dm-5
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.372829 #13076] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-JfH5iYPwUIZh7Cc4fIBRETM6CtYD01tYHD0v07VlKjcXwYFHafLI0VLDsEB44c1W /dev/disk/by-uuid/5890a6f9-18e4-4462-8303-5e45c007aa50 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-JfH5iYPwUIZh7Cc4fIBRETM6CtYD01tYHD0v07VlKjcXwYFHafLI0VLDsEB44c1W", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"5890a6f9-18e4-4462-8303-5e45c007aa50", "ID_FS_UUID_ENC"=>"5890a6f9-18e4-4462-8303-5e45c007aa50", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75850", "nomdmonddf"=>"1", "nomdmonisw
Sep 11 18:31:26 node-2 nailgun-agent: "=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.372865 #13076] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.372908 #13076] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.372965 #13076] DEBUG -- : Device dm-5 seems to be appropriate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.372986 #13076] DEBUG -- : Getting udev properties for device: ram0
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.375642 #13076] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7056", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.375701 #13076] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.375762 #13076] DEBUG -- : Device ram0 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.375789 #13076] DEBUG -- : Getting udev properties for device: ram1
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.378502 #13076] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7227", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.378563 #13076] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.378618 #13076] DEBUG -- : Device ram1 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.378645 #13076] DEBUG -- : Getting udev properties for device: ram2
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.381635 #13076] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14402", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.381707 #13076] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.381805 #13076] DEBUG -- : Device ram2 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.381927 #13076] DEBUG -- : Getting udev properties for device: ram3
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.385108 #13076] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14410", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.385180 #13076] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.385287 #13076] DEBUG -- : Device ram3 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.385344 #13076] DEBUG -- : Getting udev properties for device: ram4
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.388322 #13076] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14418", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.388370 #13076] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.388419 #13076] DEBUG -- : Device ram4 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.388449 #13076] DEBUG -- : Getting udev properties for device: ram5
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.391449 #13076] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14427", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.391586 #13076] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.391689 #13076] DEBUG -- : Device ram5 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.391747 #13076] DEBUG -- : Getting udev properties for device: ram6
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.394948 #13076] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14435", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.395043 #13076] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.395164 #13076] DEBUG -- : Device ram6 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.395246 #13076] DEBUG -- : Getting udev properties for device: ram7
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.398433 #13076] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14443", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.398539 #13076] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.398637 #13076] DEBUG -- : Device ram7 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.398693 #13076] DEBUG -- : Getting udev properties for device: ram8
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.404779 #13076] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14452", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.404832 #13076] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.404922 #13076] DEBUG -- : Device ram8 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.404960 #13076] DEBUG -- : Getting udev properties for device: ram9
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.408879 #13076] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14463", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.408946 #13076] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.409050 #13076] DEBUG -- : Device ram9 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.409130 #13076] DEBUG -- : Getting udev properties for device: loop0
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.413491 #13076] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6050", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.413583 #13076] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.413710 #13076] DEBUG -- : Device loop0 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.413770 #13076] DEBUG -- : Getting udev properties for device: loop1
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.417262 #13076] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6219", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.417334 #13076] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.417473 #13076] DEBUG -- : Device loop1 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.417531 #13076] DEBUG -- : Getting udev properties for device: loop2
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.421652 #13076] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6276", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.421706 #13076] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.421762 #13076] DEBUG -- : Device loop2 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.421831 #13076] DEBUG -- : Getting udev properties for device: loop3
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.426074 #13076] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6428", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.426183 #13076] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.426289 #13076] DEBUG -- : Device loop3 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.426344 #13076] DEBUG -- : Getting udev properties for device: loop4
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.429984 #13076] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6574", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.430035 #13076] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.430153 #13076] DEBUG -- : Device loop4 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.430194 #13076] DEBUG -- : Getting udev properties for device: loop5
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.433281 #13076] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6765", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.433332 #13076] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.433425 #13076] DEBUG -- : Device loop5 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.433464 #13076] DEBUG -- : Getting udev properties for device: loop6
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.436440 #13076] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6841", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.436490 #13076] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.436589 #13076] DEBUG -- : Device loop6 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.436647 #13076] DEBUG -- : Getting udev properties for device: loop7
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.446557 #13076] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6947", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.446612 #13076] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.446692 #13076] DEBUG -- : Device loop7 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.446733 #13076] DEBUG -- : Getting udev properties for device: ram10
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.450574 #13076] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7359", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.450645 #13076] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.450760 #13076] DEBUG -- : Device ram10 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.450815 #13076] DEBUG -- : Getting udev properties for device: ram11
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.454331 #13076] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7511", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.454386 #13076] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.454465 #13076] DEBUG -- : Device ram11 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.454506 #13076] DEBUG -- : Getting udev properties for device: ram12
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.458187 #13076] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7705", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.458337 #13076] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.458449 #13076] DEBUG -- : Device ram12 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.458503 #13076] DEBUG -- : Getting udev properties for device: ram13
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.462107 #13076] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11928", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.462186 #13076] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.462414 #13076] DEBUG -- : Device ram13 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.462472 #13076] DEBUG -- : Getting udev properties for device: ram14
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.465757 #13076] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14373", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.465830 #13076] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.465922 #13076] DEBUG -- : Device ram14 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.466045 #13076] DEBUG -- : Getting udev properties for device: ram15
Sep 11 18:31:26 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469037 #13076] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14394", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469111 #13076] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469204 #13076] DEBUG -- : Device ram15 removable parameter: "0"
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469302 #13076] 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"}]
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469342 #13076] DEBUG -- : Block device seems to be physical data storage: sda
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469512 #13076] DEBUG -- : Found block device: dm-0
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469553 #13076] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469588 #13076] DEBUG -- : Found block device: dm-1
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469621 #13076] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469647 #13076] DEBUG -- : Found block device: dm-2
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469679 #13076] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469703 #13076] DEBUG -- : Found block device: dm-3
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469731 #13076] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469755 #13076] DEBUG -- : Found block device: dm-4
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469783 #13076] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469868 #13076] DEBUG -- : Found block device: dm-5
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469898 #13076] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469923 #13076] DEBUG -- : Found block device: ram0
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469950 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.469974 #13076] DEBUG -- : Found block device: ram1
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470000 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470025 #13076] DEBUG -- : Found block device: ram2
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470053 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470075 #13076] DEBUG -- : Found block device: ram3
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470102 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470186 #13076] DEBUG -- : Found block device: ram4
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470216 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470240 #13076] DEBUG -- : Found block device: ram5
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470266 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470290 #13076] DEBUG -- : Found block device: ram6
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470317 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470339 #13076] DEBUG -- : Found block device: ram7
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470371 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470396 #13076] DEBUG -- : Found block device: ram8
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470422 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470510 #13076] DEBUG -- : Found block device: ram9
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470537 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470559 #13076] DEBUG -- : Found block device: loop0
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470586 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470608 #13076] DEBUG -- : Found block device: loop1
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470634 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470658 #13076] DEBUG -- : Found block device: loop2
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470683 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470705 #13076] DEBUG -- : Found block device: loop3
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470730 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470754 #13076] DEBUG -- : Found block device: loop4
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470881 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470904 #13076] DEBUG -- : Found block device: loop5
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470928 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470952 #13076] DEBUG -- : Found block device: loop6
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.470982 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471005 #13076] DEBUG -- : Found block device: loop7
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471034 #13076] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471060 #13076] DEBUG -- : Found block device: ram10
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471085 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471216 #13076] DEBUG -- : Found block device: ram11
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471243 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471266 #13076] DEBUG -- : Found block device: ram12
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471291 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471315 #13076] DEBUG -- : Found block device: ram13
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471342 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471364 #13076] DEBUG -- : Found block device: ram14
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471391 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471415 #13076] DEBUG -- : Found block device: ram15
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471552 #13076] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.471631 #13076] 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}]
Sep 11 18:31:26 node-2 nailgun-agent: D, [2016-09-11T18:31:26.690102 #13076] DEBUG -- : Response: status: 200 body: {"id": 2}
Sep 11 18:31:26 node-2 nailgun-agent: I, [2016-09-11T18:31:26.690464 #13076]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep 11 18:31:28 node-2 puppet-user[13778]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep 11 18:31:28 node-2 puppet-user[13778]: Finished catalog run in 18.74 seconds
Sep 11 18:31:30 node-2 puppet-user[15138]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 11 18:31:31 node-2 puppet-user[15138]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Sep 11 18:31:35 node-2 puppet-user[15138]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 11 18:32:01 node-2 CRON[17376]: (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")
Sep 11 18:32:05 node-2 puppet-user[15138]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 11 18:32:05 node-2 puppet-user[15138]: Finished catalog run in 34.29 seconds
Sep 11 18:32:07 node-2 puppet-user[17594]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 11 18:32:07 node-2 puppet-user[17594]: Compiled catalog for node-2.domain.tld in environment production in 0.57 seconds
Sep 11 18:32:08 node-2 puppet-user[17594]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 11 18:32:08 node-2 puppet-user[17594]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 11 18:32:08 node-2 puppet-user[17594]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 11 18:32:08 node-2 puppet-user[17594]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 11 18:32:08 node-2 puppet-user[17594]: Finished catalog run in 0.09 seconds
Sep 11 18:32:09 node-2 puppet-user[18056]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 11 18:32:10 node-2 puppet-user[18056]: Compiled catalog for node-2.domain.tld in environment production in 0.93 seconds
Sep 11 18:32:11 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 11 18:32:11 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 11 18:32:11 node-2 crontab[18483]: (root) LIST (root)
Sep 11 18:32:11 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 11 18:32:11 node-2 crontab[18484]: (root) REPLACE (root)
Sep 11 18:32:13 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 11 18:32:14 node-2 puppet-user[18056]: (/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
Sep 11 18:32:14 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/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
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 11 18:32:15 node-2 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 11 18:32:15 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 11 18:32:15 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 11 18:32:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:32:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:33:41 node-2 ntpdate[30691]: no servers can be used, exiting
<27>Sep 11 18:33:41 node-2 ntpdate[30933]: no servers can be used, exiting
<27>Sep 11 18:34:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:16 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:16 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:16 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:16 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:16 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:27 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:27 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:27 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:27 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:34:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:30 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:35:41 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 11 18:35:41 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 11 18:35:47 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 11 18:35:47 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 11 18:35:53 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 11 18:35:59 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 11 18:35:59 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 11 18:36:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:19 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:19 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:19 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:19 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:52 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:52 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:52 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:52 node-2 multipathd: uevent trigger error
<27>Sep 11 18:36:52 node-2 multipathd: uevent trigger error
<129>Sep 11 18:36:54 node-2 haproxy[25533]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 11 18:36:54 node-2 haproxy[25533]: proxy odl-neutron-endpoint has no server available!
<129>Sep 11 18:36:55 node-2 haproxy[25551]: Server odl-jetty/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 56ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 11 18:36:55 node-2 haproxy[25551]: proxy odl-jetty has no server available!
<27>Sep 11 18:37:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:18 node-2 multipathd: uevent trigger error
<129>Sep 11 18:37:20 node-2 haproxy[27901]: 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>Sep 11 18:37:21 node-2 haproxy[27905]: 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>Sep 11 18:37:21 node-2 haproxy[27905]: 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>Sep 11 18:37:21 node-2 haproxy[27905]: proxy mysqld has no server available!
<27>Sep 11 18:37:24 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:24 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:24 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:24 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:24 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:27 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:27 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:27 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:27 node-2 multipathd: uevent trigger error
<129>Sep 11 18:37:30 node-2 haproxy[30614]: 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>Sep 11 18:37:30 node-2 haproxy[30614]: 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>Sep 11 18:37:30 node-2 haproxy[30614]: 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>Sep 11 18:37:30 node-2 haproxy[30614]: proxy mysqld has no server available!
<129>Sep 11 18:37:30 node-2 haproxy[30614]: 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>Sep 11 18:37:31 node-2 haproxy[30618]: 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>Sep 11 18:37:31 node-2 haproxy[30618]: 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>Sep 11 18:37:31 node-2 haproxy[30618]: proxy object-storage has no server available!
<27>Sep 11 18:37:33 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:33 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:33 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:33 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:33 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:33 node-2 multipathd: uevent trigger error
<129>Sep 11 18:37:35 node-2 haproxy[31942]: 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>Sep 11 18:37:35 node-2 haproxy[31942]: 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>Sep 11 18:37:35 node-2 haproxy[31942]: 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>Sep 11 18:37:35 node-2 haproxy[31942]: proxy neutron has no server available!
<129>Sep 11 18:37:35 node-2 haproxy[31942]: 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>Sep 11 18:37:35 node-2 haproxy[31942]: 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>Sep 11 18:37:36 node-2 haproxy[31946]: 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>Sep 11 18:37:36 node-2 haproxy[31946]: proxy mysqld has no server available!
<129>Sep 11 18:37:36 node-2 haproxy[31946]: 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>Sep 11 18:37:36 node-2 haproxy[31946]: 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>Sep 11 18:37:36 node-2 haproxy[31946]: 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>Sep 11 18:37:36 node-2 haproxy[31946]: proxy object-storage has no server available!
<27>Sep 11 18:37:38 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:38 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:38 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:38 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:38 node-2 multipathd: uevent trigger error
<129>Sep 11 18:37:40 node-2 haproxy[1022]: 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>Sep 11 18:37:40 node-2 haproxy[1022]: 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>Sep 11 18:37:40 node-2 haproxy[1022]: 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>Sep 11 18:37:40 node-2 haproxy[1022]: proxy keystone-1 has no server available!
<129>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:41 node-2 haproxy[1047]: proxy keystone-2 has no server available!
<129>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:41 node-2 haproxy[1047]: proxy neutron has no server available!
<129>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:41 node-2 haproxy[1047]: 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>Sep 11 18:37:42 node-2 haproxy[1047]: 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>Sep 11 18:37:42 node-2 haproxy[1047]: proxy mysqld has no server available!
<129>Sep 11 18:37:42 node-2 haproxy[1047]: 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>Sep 11 18:37:42 node-2 haproxy[1047]: 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>Sep 11 18:37:42 node-2 haproxy[1047]: 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>Sep 11 18:37:42 node-2 haproxy[1047]: proxy object-storage has no server available!
<27>Sep 11 18:37:43 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:43 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:43 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:43 node-2 multipathd: uevent trigger error
<129>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: proxy keystone-1 has no server available!
<129>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: proxy keystone-2 has no server available!
<129>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: 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>Sep 11 18:37:46 node-2 haproxy[2411]: proxy neutron has no server available!
<129>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: proxy mysqld has no server available!
<129>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: proxy object-storage has no server available!
<129>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: 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>Sep 11 18:37:47 node-2 haproxy[2415]: proxy aodh has no server available!
<27>Sep 11 18:37:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:49 node-2 multipathd: uevent trigger error
<129>Sep 11 18:37:51 node-2 haproxy[3764]: 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>Sep 11 18:37:51 node-2 haproxy[3764]: 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>Sep 11 18:37:51 node-2 haproxy[3764]: 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>Sep 11 18:37:51 node-2 haproxy[3764]: proxy keystone-1 has no server available!
<129>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: proxy keystone-2 has no server available!
<129>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: proxy neutron has no server available!
<129>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: proxy mysqld has no server available!
<129>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: 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>Sep 11 18:37:52 node-2 haproxy[3771]: proxy object-storage has no server available!
<129>Sep 11 18:37:53 node-2 haproxy[3771]: 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>Sep 11 18:37:53 node-2 haproxy[3771]: 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>Sep 11 18:37:53 node-2 haproxy[3771]: 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>Sep 11 18:37:53 node-2 haproxy[3771]: proxy aodh has no server available!
<129>Sep 11 18:37:53 node-2 haproxy[3771]: 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>Sep 11 18:37:53 node-2 haproxy[3771]: 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>Sep 11 18:37:53 node-2 haproxy[3771]: 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>Sep 11 18:37:53 node-2 haproxy[3771]: proxy ceilometer has no server available!
<27>Sep 11 18:37:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:37:54 node-2 multipathd: uevent trigger error
<129>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: proxy keystone-1 has no server available!
<129>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: proxy keystone-2 has no server available!
<129>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:57 node-2 haproxy[5103]: proxy neutron has no server available!
<129>Sep 11 18:37:57 node-2 haproxy[5103]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: proxy mysqld has no server available!
<129>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: proxy object-storage has no server available!
<129>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: proxy aodh has no server available!
<129>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: 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>Sep 11 18:37:58 node-2 haproxy[5107]: proxy ceilometer has no server available!
<27>Sep 11 18:38:00 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:00 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:00 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:00 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:00 node-2 multipathd: uevent trigger error
<129>Sep 11 18:38:02 node-2 haproxy[6469]: 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>Sep 11 18:38:02 node-2 haproxy[6469]: 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>Sep 11 18:38:02 node-2 haproxy[6469]: 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>Sep 11 18:38:02 node-2 haproxy[6469]: 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>Sep 11 18:38:02 node-2 haproxy[6469]: proxy keystone-1 has no server available!
<129>Sep 11 18:38:02 node-2 haproxy[6469]: 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>Sep 11 18:38:02 node-2 haproxy[6469]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: proxy keystone-2 has no server available!
<129>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: proxy neutron has no server available!
<129>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: proxy mysqld has no server available!
<129>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: proxy object-storage has no server available!
<129>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: 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>Sep 11 18:38:03 node-2 haproxy[6473]: proxy aodh has no server available!
<129>Sep 11 18:38:04 node-2 haproxy[6473]: 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>Sep 11 18:38:04 node-2 haproxy[6473]: 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>Sep 11 18:38:04 node-2 haproxy[6473]: 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>Sep 11 18:38:04 node-2 haproxy[6473]: proxy ceilometer has no server available!
<27>Sep 11 18:38:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:05 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:05 node-2 multipathd: uevent trigger error
<129>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: proxy keystone-1 has no server available!
<129>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: proxy keystone-2 has no server available!
<129>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: proxy glance-api has no server available!
<129>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: proxy glance-glare has no server available!
<129>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:08 node-2 haproxy[7872]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: proxy neutron has no server available!
<129>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: proxy glance-registry has no server available!
<129>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: proxy mysqld has no server available!
<129>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: proxy object-storage has no server available!
<129>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: proxy aodh has no server available!
<129>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: 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>Sep 11 18:38:09 node-2 haproxy[7879]: proxy ceilometer has no server available!
<27>Sep 11 18:38:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:11 node-2 multipathd: uevent trigger error
<129>Sep 11 18:38:13 node-2 haproxy[9505]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: proxy keystone-1 has no server available!
<129>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: proxy keystone-2 has no server available!
<129>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: proxy nova-api has no server available!
<129>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: proxy nova-metadata-api has no server available!
<129>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: proxy glance-api has no server available!
<27>Sep 11 18:38:14 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: proxy glance-glare has no server available!
<129>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:14 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: proxy neutron has no server available!
<129>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: proxy glance-registry has no server available!
<129>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: proxy mysqld has no server available!
<129>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: proxy object-storage has no server available!
<129>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: proxy aodh has no server available!
<129>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: proxy ceilometer has no server available!
<129>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: 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>Sep 11 18:38:15 node-2 haproxy[9509]: proxy nova-novncproxy has no server available!
<27>Sep 11 18:38:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:17 node-2 multipathd: uevent trigger error
<129>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: proxy keystone-1 has no server available!
<129>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: proxy keystone-2 has no server available!
<129>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: proxy nova-api has no server available!
<129>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: proxy nova-metadata-api has no server available!
<129>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:19 node-2 haproxy[10823]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy cinder-api has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy glance-api has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy glance-glare has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy neutron has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy glance-registry has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy mysqld has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy object-storage has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:20 node-2 haproxy[10827]: proxy aodh has no server available!
<129>Sep 11 18:38:20 node-2 haproxy[10827]: 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>Sep 11 18:38:21 node-2 haproxy[10827]: 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>Sep 11 18:38:21 node-2 haproxy[10827]: 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>Sep 11 18:38:21 node-2 haproxy[10827]: proxy ceilometer has no server available!
<129>Sep 11 18:38:21 node-2 haproxy[10827]: 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>Sep 11 18:38:21 node-2 haproxy[10827]: 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>Sep 11 18:38:21 node-2 haproxy[10827]: 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>Sep 11 18:38:21 node-2 haproxy[10827]: proxy nova-novncproxy has no server available!
<27>Sep 11 18:38:21 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 11 18:38:22 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:22 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:22 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:22 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:22 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:22 node-2 multipathd: uevent trigger error
<129>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: proxy keystone-1 has no server available!
<129>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: proxy keystone-2 has no server available!
<129>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: proxy nova-api has no server available!
<129>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: proxy nova-metadata-api has no server available!
<129>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: 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>Sep 11 18:38:25 node-2 haproxy[12588]: proxy cinder-api has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy glance-api has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy glance-glare has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy neutron has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy glance-registry has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy mysqld has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy object-storage has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy aodh has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy ceilometer has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:26 node-2 haproxy[12594]: proxy heat-api has no server available!
<129>Sep 11 18:38:26 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: proxy heat-api-cfn has no server available!
<129>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: proxy heat-api-cloudwatch has no server available!
<129>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: 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>Sep 11 18:38:27 node-2 haproxy[12594]: proxy nova-novncproxy has no server available!
<27>Sep 11 18:38:28 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:28 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:28 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:28 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:28 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:38:42 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 11 18:39:07 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>Sep 11 18:39:09 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 11 18:39:56 node-2 multipathd: uevent trigger error
<27>Sep 11 18:39:56 node-2 multipathd: uevent trigger error
<27>Sep 11 18:39:56 node-2 multipathd: uevent trigger error
<27>Sep 11 18:39:56 node-2 multipathd: uevent trigger error
<27>Sep 11 18:39:56 node-2 multipathd: uevent trigger error
<27>Sep 11 18:39:56 node-2 multipathd: uevent trigger error
<27>Sep 11 18:41:32 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 11 18:42:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:18 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:18 node-2 multipathd: uevent trigger error
<43>Sep 11 18:42:36 node-2 apache2_error [Sun Sep 11 18:42:30.920633 2016] [mpm_event:notice] [pid 22874:tid 139699830241152] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 11 18:42:36 node-2 apache2_error [Sun Sep 11 18:42:30.920785 2016] [core:notice] [pid 22874:tid 139699830241152] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 11 18:42:36 node-2 apache2_error [Sun Sep 11 18:42:34.278294 2016] [mpm_event:notice] [pid 22874:tid 139699830241152] AH00491: caught SIGTERM, shutting down
<43>Sep 11 18:42:36 node-2 apache2_error [Sun Sep 11 18:42:35.365833 2016] [mpm_worker:notice] [pid 23888:tid 140027437811584] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 11 18:42:36 node-2 apache2_error [Sun Sep 11 18:42:35.365895 2016] [core:notice] [pid 23888:tid 140027437811584] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 11 18:42:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:44 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:44 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:44 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:44 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:44 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:48 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:48 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:48 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:48 node-2 multipathd: uevent trigger error
<27>Sep 11 18:42:48 node-2 multipathd: uevent trigger error
<43>Sep 11 18:43:56 node-2 apache2_error [Sun Sep 11 18:43:56.440583 2016] [mpm_worker:notice] [pid 23888:tid 140027437811584] AH00295: caught SIGTERM, shutting down
<43>Sep 11 18:44:06 node-2 apache2_error [Sun Sep 11 18:43:57.200037 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 11 18:44:06 node-2 apache2_error [Sun Sep 11 18:43:57.200068 2016] [core:notice] [pid 5119:tid 140003838633856] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 11 18:44:33 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 11 18:44:46 node-2 apache2_error [Sun Sep 11 18:44:41.134712 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 11 18:44:46 node-2 apache2_error [Sun Sep 11 18:44:41.327853 2016] [mpm_worker:warn] [pid 5119:tid 140003838633856] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 11 18:44:46 node-2 apache2_error [Sun Sep 11 18:44:41.330963 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 11 18:44:46 node-2 apache2_error [Sun Sep 11 18:44:41.330987 2016] [core:notice] [pid 5119:tid 140003838633856] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 11 18:45:26 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:26 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:26 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:26 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:26 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:31 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:47 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:47 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:47 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:47 node-2 multipathd: uevent trigger error
<27>Sep 11 18:45:47 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:12 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:46:35 node-2 multipathd: uevent trigger error
<27>Sep 11 18:47:34 node-2 multipathd: uevent trigger error
<27>Sep 11 18:47:34 node-2 multipathd: uevent trigger error
<27>Sep 11 18:47:34 node-2 multipathd: uevent trigger error
<27>Sep 11 18:47:34 node-2 multipathd: uevent trigger error
<27>Sep 11 18:47:34 node-2 multipathd: uevent trigger error
<27>Sep 11 18:47:40 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 11 18:48:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:48:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:48:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:48:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:48:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:49:45 node-2 multipathd: uevent trigger error
<27>Sep 11 18:49:45 node-2 multipathd: uevent trigger error
<27>Sep 11 18:49:45 node-2 multipathd: uevent trigger error
<27>Sep 11 18:49:45 node-2 multipathd: uevent trigger error
<27>Sep 11 18:49:45 node-2 multipathd: uevent trigger error
<27>Sep 11 18:49:45 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:11 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:17 node-2 multipathd: uevent trigger error
<27>Sep 11 18:50:42 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 11 18:52:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:52:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:52:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:52:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:52:46 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:02 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:02 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:02 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:02 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:02 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:02 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:07 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:07 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:07 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:07 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:07 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:13 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:13 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:13 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:13 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:13 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:39 node-2 multipathd: uevent trigger error
<27>Sep 11 18:53:44 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 11 18:54:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:54:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:54:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:54:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:54:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:08 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:08 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:08 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:08 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:23 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:55:41 node-2 multipathd: uevent trigger error
<27>Sep 11 18:56:46 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 11 18:58:06 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:06 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:06 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:06 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:06 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:06 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:49 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:58:54 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:47 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 11 18:59:55 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:55 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:55 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:55 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:59 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:59 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:59 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:59 node-2 multipathd: uevent trigger error
<27>Sep 11 18:59:59 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:03 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:03 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:04 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:04 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:04 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:16 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:16 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:16 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:16 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:22 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:55 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:55 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:55 node-2 multipathd: uevent trigger error
<27>Sep 11 19:00:55 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:04 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:04 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:04 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:04 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:22 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:22 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:22 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:22 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:22 node-2 multipathd: uevent trigger error
<27>Sep 11 19:02:22 node-2 multipathd: uevent trigger error
<11>Sep 11 19:02:35 node-2 liberasurecode[26080]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:35 node-2 liberasurecode[26080]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:35 node-2 liberasurecode[26080]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:35 node-2 liberasurecode[26080]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:35 node-2 liberasurecode[26246]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:35 node-2 liberasurecode[26246]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:35 node-2 liberasurecode[26246]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:35 node-2 liberasurecode[26246]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:37 node-2 liberasurecode[27176]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:37 node-2 liberasurecode[27176]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:37 node-2 liberasurecode[27176]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:37 node-2 liberasurecode[27176]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27793]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27793]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27793]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27793]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27834]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27834]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27899]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27899]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27899]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:43 node-2 liberasurecode[27899]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27967]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27967]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27986]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27986]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27986]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27986]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27999]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27999]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27999]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[27999]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[28011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[28011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[28011]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:02:44 node-2 liberasurecode[28011]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 11 19:02:48 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Sep 11 19:03:01 node-2 liberasurecode[28760]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:03:01 node-2 liberasurecode[28760]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:03:01 node-2 liberasurecode[28760]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:03:01 node-2 liberasurecode[28760]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 11 19:03:09 node-2 multipathd: uevent trigger error
<27>Sep 11 19:03:09 node-2 multipathd: uevent trigger error
<27>Sep 11 19:03:09 node-2 multipathd: uevent trigger error
<27>Sep 11 19:03:09 node-2 multipathd: uevent trigger error
<27>Sep 11 19:03:09 node-2 multipathd: uevent trigger error
<43>Sep 11 19:03:58 node-2 apache2_error [Sun Sep 11 19:03:57.000770 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 11 19:03:58 node-2 apache2_error [Sun Sep 11 19:03:57.386927 2016] [mpm_worker:warn] [pid 5119:tid 140003838633856] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 11 19:03:58 node-2 apache2_error [Sun Sep 11 19:03:57.391247 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 11 19:03:58 node-2 apache2_error [Sun Sep 11 19:03:57.391272 2016] [core:notice] [pid 5119:tid 140003838633856] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 11 19:04:38 node-2 apache2_error [Sun Sep 11 19:04:34.563552 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 11 19:04:38 node-2 apache2_error [Sun Sep 11 19:04:34.760724 2016] [mpm_worker:warn] [pid 5119:tid 140003838633856] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 11 19:04:38 node-2 apache2_error [Sun Sep 11 19:04:34.771412 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 11 19:04:38 node-2 apache2_error [Sun Sep 11 19:04:34.771448 2016] [core:notice] [pid 5119:tid 140003838633856] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 11 19:04:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:45 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:45 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:45 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:45 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:04:51 node-2 multipathd: uevent trigger error
<11>Sep 11 19:05:01 node-2 liberasurecode[16565]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:05:01 node-2 liberasurecode[16565]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:05:01 node-2 liberasurecode[16565]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:05:01 node-2 liberasurecode[16565]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Sep 11 19:05:28 node-2 apache2_error [Sun Sep 11 19:05:26.397631 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 11 19:05:28 node-2 apache2_error [Sun Sep 11 19:05:26.597496 2016] [mpm_worker:warn] [pid 5119:tid 140003838633856] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 11 19:05:28 node-2 apache2_error [Sun Sep 11 19:05:26.609712 2016] [mpm_worker:notice] [pid 5119:tid 140003838633856] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 11 19:05:28 node-2 apache2_error [Sun Sep 11 19:05:26.609744 2016] [core:notice] [pid 5119:tid 140003838633856] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 11 19:05:30 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:30 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:30 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:30 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:30 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:30 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:37 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:37 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:37 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:37 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:05:51 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 11 19:06:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:22 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:37 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 11 19:06:46 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:46 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:46 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:46 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:46 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:51 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:06:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:10 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:10 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:10 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:10 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:13 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 11 19:07:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:23 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:39 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:39 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:39 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:39 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:44 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:44 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:44 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:44 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:44 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:07:57 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:02 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:14 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:14 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:14 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:14 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:14 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:29 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:33 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:33 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:33 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:33 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:33 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:38 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:43 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:48 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:48 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:48 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:48 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:52 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:52 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:52 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:53 node-2 multipathd: uevent trigger error
<27>Sep 11 19:08:53 node-2 multipathd: uevent trigger error
<11>Sep 11 19:10:01 node-2 liberasurecode[24988]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:10:01 node-2 liberasurecode[24988]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:10:01 node-2 liberasurecode[24988]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 11 19:10:01 node-2 liberasurecode[24988]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
