Jul 27 20:54:39 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8403" x-info="http://www.rsyslog.com"] start
Jul 27 20:54:39 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 27 20:54:39 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 27 20:54:39 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 27 20:54:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 27 20:54:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 27 20:54:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 27 20:54:39 node-2 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 27 20:54:39 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=2feef717-9fda-4d7b-a349-a4e9eeea9420 nomdmonddf nomdmonisw
Jul 27 20:54:39 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 27 20:54:39 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 27 20:54:39 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 27 20:54:39 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 27 20:54:39 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 27 20:54:39 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 27 20:54:39 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 27 20:54:39 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
Jul 27 20:54:39 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 27 20:54:39 node-2 kernel: [    0.000000] No AGP bridge found
Jul 27 20:54:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 27 20:54:39 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 27 20:54:39 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 27 20:54:39 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 27 20:54:39 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 27 20:54:39 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 27 20:54:39 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 27 20:54:39 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 27 20:54:39 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 27 20:54:39 node-2 kernel: [    0.000000]   2 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000]   3 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000]   4 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000]   5 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000]   6 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000]   7 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000]   8 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000]   9 disabled
Jul 27 20:54:39 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 27 20:54:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 27 20:54:39 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 27 20:54:39 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 27 20:54:39 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 27 20:54:39 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 27 20:54:39 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 27 20:54:39 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 27 20:54:39 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 27 20:54:39 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 27 20:54:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 27 20:54:39 node-2 kernel: [    0.000000] RAMDISK: [mem 0x3581a000-0x36c04fff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 27 20:54:39 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 27 20:54:39 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 27 20:54:39 node-2 kernel: [    0.000000] Zone ranges:
Jul 27 20:54:39 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 27 20:54:39 node-2 kernel: [    0.000000] Early memory node ranges
Jul 27 20:54:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 27 20:54:39 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 27 20:54:39 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 27 20:54:39 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 27 20:54:39 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 27 20:54:39 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 27 20:54:39 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 27 20:54:39 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 27 20:54:39 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 27 20:54:39 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 27 20:54:39 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 27 20:54:39 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 27 20:54:39 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 27 20:54:39 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 27 20:54:39 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 27 20:54:39 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 27 20:54:39 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 27 20:54:39 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 27 20:54:39 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 27 20:54:39 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 27 20:54:39 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 27 20:54:39 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 27 20:54:39 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 27 20:54:39 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 
Jul 27 20:54:39 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 27 20:54:39 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 27 20:54:39 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=2feef717-9fda-4d7b-a349-a4e9eeea9420 nomdmonddf nomdmonisw
Jul 27 20:54:39 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 27 20:54:39 node-2 kernel: [    0.000000] Checking aperture...
Jul 27 20:54:39 node-2 kernel: [    0.000000] No AGP bridge found
Jul 27 20:54:39 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 27 20:54:39 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 27 20:54:39 node-2 kernel: [    0.000000] Memory: 32653300K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627196K reserved)
Jul 27 20:54:39 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 27 20:54:39 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 27 20:54:39 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 27 20:54:39 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 27 20:54:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 27 20:54:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 27 20:54:39 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 27 20:54:39 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 27 20:54:39 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 27 20:54:39 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 27 20:54:39 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 27 20:54:39 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 27 20:54:39 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 27 20:54:39 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 27 20:54:39 node-2 kernel: [    0.004000] tsc: Detected 3491.756 MHz processor
Jul 27 20:54:39 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.51 BogoMIPS (lpj=13967024)
Jul 27 20:54:39 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 27 20:54:39 node-2 kernel: [    0.000043] Security Framework initialized
Jul 27 20:54:39 node-2 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 27 20:54:39 node-2 kernel: [    0.000062] Yama: becoming mindful.
Jul 27 20:54:39 node-2 kernel: [    0.001450] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.006351] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.008278] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.008306] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.008599] Initializing cgroup subsys memory
Jul 27 20:54:39 node-2 kernel: [    0.008607] Initializing cgroup subsys devices
Jul 27 20:54:39 node-2 kernel: [    0.008609] Initializing cgroup subsys freezer
Jul 27 20:54:39 node-2 kernel: [    0.008611] Initializing cgroup subsys blkio
Jul 27 20:54:39 node-2 kernel: [    0.008612] Initializing cgroup subsys perf_event
Jul 27 20:54:39 node-2 kernel: [    0.008614] Initializing cgroup subsys hugetlb
Jul 27 20:54:39 node-2 kernel: [    0.008633] CPU: Physical Processor ID: 0
Jul 27 20:54:39 node-2 kernel: [    0.008635] CPU: Processor Core ID: 0
Jul 27 20:54:39 node-2 kernel: [    0.008639] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 27 20:54:39 node-2 kernel: [    0.008639] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 27 20:54:39 node-2 kernel: [    0.009332] mce: CPU supports 22 MCE banks
Jul 27 20:54:39 node-2 kernel: [    0.009360] CPU0: Thermal monitoring enabled (TM1)
Jul 27 20:54:39 node-2 kernel: [    0.009380] process: using mwait in idle threads
Jul 27 20:54:39 node-2 kernel: [    0.009384] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 27 20:54:39 node-2 kernel: [    0.009384] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 27 20:54:39 node-2 kernel: [    0.009384] tlb_flushall_shift: 6
Jul 27 20:54:39 node-2 kernel: [    0.009473] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 27 20:54:39 node-2 kernel: [    0.010197] ACPI: Core revision 20131115
Jul 27 20:54:39 node-2 kernel: [    0.022869] ACPI: All ACPI Tables successfully acquired
Jul 27 20:54:39 node-2 kernel: [    0.023042] ftrace: allocating 28617 entries in 112 pages
Jul 27 20:54:39 node-2 kernel: [    0.031860] dmar: Host address width 46
Jul 27 20:54:39 node-2 kernel: [    0.031862] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 27 20:54:39 node-2 kernel: [    0.031869] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 20:54:39 node-2 kernel: [    0.031870] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 27 20:54:39 node-2 kernel: [    0.031875] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 20:54:39 node-2 kernel: [    0.031876] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 27 20:54:39 node-2 kernel: [    0.031878] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 27 20:54:39 node-2 kernel: [    0.031879] dmar: ATSR flags: 0x0
Jul 27 20:54:39 node-2 kernel: [    0.031880] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 27 20:54:39 node-2 kernel: [    0.031881] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 27 20:54:39 node-2 kernel: [    0.031997] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 27 20:54:39 node-2 kernel: [    0.031998] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 20:54:39 node-2 kernel: [    0.031999] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 20:54:39 node-2 kernel: [    0.032000] HPET id 0 under DRHD base 0xc7ffc000
Jul 27 20:54:39 node-2 kernel: [    0.032001] Your BIOS is broken and requested that x2apic be disabled.
Jul 27 20:54:39 node-2 kernel: [    0.032001] This will slightly decrease performance.
Jul 27 20:54:39 node-2 kernel: [    0.032001] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 27 20:54:39 node-2 kernel: [    0.032432] Enabled IRQ remapping in xapic mode
Jul 27 20:54:39 node-2 kernel: [    0.032433] x2apic not enabled, IRQ remapping is in xapic mode
Jul 27 20:54:39 node-2 kernel: [    0.032437] Switched APIC routing to physical flat.
Jul 27 20:54:39 node-2 kernel: [    0.033063] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 27 20:54:39 node-2 kernel: [    0.072711] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 27 20:54:39 node-2 kernel: [    0.072717] TSC deadline timer enabled
Jul 27 20:54:39 node-2 kernel: [    0.072724] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 27 20:54:39 node-2 kernel: [    0.072730] ... version:                3
Jul 27 20:54:39 node-2 kernel: [    0.072731] ... bit width:              48
Jul 27 20:54:39 node-2 kernel: [    0.072732] ... generic registers:      4
Jul 27 20:54:39 node-2 kernel: [    0.072733] ... value mask:             0000ffffffffffff
Jul 27 20:54:39 node-2 kernel: [    0.072734] ... max period:             0000ffffffffffff
Jul 27 20:54:39 node-2 kernel: [    0.072735] ... fixed-purpose events:   3
Jul 27 20:54:39 node-2 kernel: [    0.072736] ... event mask:             000000070000000f
Jul 27 20:54:39 node-2 kernel: [    0.074188] x86: Booting SMP configuration:
Jul 27 20:54:39 node-2 kernel: [    0.088315] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 27 20:54:39 node-2 kernel: [    0.074190] .... node  #0, CPUs:        #1  #2  #3
Jul 27 20:54:39 node-2 kernel: [    0.116230] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 27 20:54:39 node-2 kernel: [    0.270369] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 27 20:54:39 node-2 kernel: [    0.325879] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 27 20:54:39 node-2 kernel: [    0.382733] x86: Booted up 2 nodes, 16 CPUs
Jul 27 20:54:39 node-2 kernel: [    0.382737] smpboot: Total of 16 processors activated (111748.18 BogoMIPS)
Jul 27 20:54:39 node-2 kernel: [    0.406350] devtmpfs: initialized
Jul 27 20:54:39 node-2 kernel: [    0.409424] EVM: security.selinux
Jul 27 20:54:39 node-2 kernel: [    0.409426] EVM: security.SMACK64
Jul 27 20:54:39 node-2 kernel: [    0.409427] EVM: security.ima
Jul 27 20:54:39 node-2 kernel: [    0.409428] EVM: security.capability
Jul 27 20:54:39 node-2 kernel: [    0.409478] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.410159] pinctrl core: initialized pinctrl subsystem
Jul 27 20:54:39 node-2 kernel: [    0.410222] regulator-dummy: no parameters
Jul 27 20:54:39 node-2 kernel: [    0.410254] RTC time: 20:54:01, date: 07/27/16
Jul 27 20:54:39 node-2 kernel: [    0.410289] NET: Registered protocol family 16
Jul 27 20:54:39 node-2 kernel: [    0.410375] cpuidle: using governor ladder
Jul 27 20:54:39 node-2 kernel: [    0.410376] cpuidle: using governor menu
Jul 27 20:54:39 node-2 kernel: [    0.410410] ACPI: bus type PCI registered
Jul 27 20:54:39 node-2 kernel: [    0.410412] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 27 20:54:39 node-2 kernel: [    0.410459] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 27 20:54:39 node-2 kernel: [    0.410462] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 27 20:54:39 node-2 kernel: [    0.424194] PCI: Using configuration type 1 for base access
Jul 27 20:54:39 node-2 kernel: [    0.425198] bio: create slab <bio-0> at 0
Jul 27 20:54:39 node-2 kernel: [    0.425480] ACPI: Added _OSI(Module Device)
Jul 27 20:54:39 node-2 kernel: [    0.425482] ACPI: Added _OSI(Processor Device)
Jul 27 20:54:39 node-2 kernel: [    0.425483] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 27 20:54:39 node-2 kernel: [    0.425484] ACPI: Added _OSI(Processor Aggregator Device)
Jul 27 20:54:39 node-2 kernel: [    0.438128] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 27 20:54:39 node-2 kernel: [    0.448641] ACPI: Interpreter enabled
Jul 27 20:54:39 node-2 kernel: [    0.448647] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 27 20:54:39 node-2 kernel: [    0.448651] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 27 20:54:39 node-2 kernel: [    0.448653] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 27 20:54:39 node-2 kernel: [    0.448660] ACPI: (supports S0 S4 S5)
Jul 27 20:54:39 node-2 kernel: [    0.448662] ACPI: Using IOAPIC for interrupt routing
Jul 27 20:54:39 node-2 kernel: [    0.448706] HEST: Table parsing has been initialized.
Jul 27 20:54:39 node-2 kernel: [    0.448709] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 27 20:54:39 node-2 kernel: [    0.449263] ACPI: No dock devices found.
Jul 27 20:54:39 node-2 kernel: [    0.460910] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 27 20:54:39 node-2 kernel: [    0.460914] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 20:54:39 node-2 kernel: [    0.460918] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 20:54:39 node-2 kernel: [    0.460944] PCI host bridge to bus 0000:ff
Jul 27 20:54:39 node-2 kernel: [    0.460946] pci_bus 0000:ff: root bus resource [bus ff]
Jul 27 20:54:39 node-2 kernel: [    0.460954] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.460992] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.461023] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461057] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461085] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.461114] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.461144] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461173] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461202] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461230] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461256] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461283] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461310] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461336] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461362] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461389] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461416] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461443] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461469] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.461497] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461522] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.461548] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461573] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461603] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.461637] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461668] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461697] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461728] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461758] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461790] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461822] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461853] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461883] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461916] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461947] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.461978] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462010] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462038] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462066] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462097] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462129] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462167] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462202] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462235] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462264] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462295] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462325] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462355] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462387] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462419] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462451] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462481] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462509] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462539] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462568] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462599] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462630] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462686] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 27 20:54:39 node-2 kernel: [    0.462689] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 20:54:39 node-2 kernel: [    0.462691] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 20:54:39 node-2 kernel: [    0.462709] PCI host bridge to bus 0000:7f
Jul 27 20:54:39 node-2 kernel: [    0.462710] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 27 20:54:39 node-2 kernel: [    0.462715] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462742] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.462770] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462798] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462820] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.462844] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.462870] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462895] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462921] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462945] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462969] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.462993] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463018] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463040] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463063] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463089] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463111] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463134] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463156] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.463182] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463207] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.463231] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463256] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463284] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 20:54:39 node-2 kernel: [    0.463318] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463344] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463371] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463399] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463424] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463451] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463476] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463504] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463529] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463557] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463585] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463614] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463643] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463669] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463694] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463722] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463747] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463776] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463805] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463833] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463859] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463883] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463909] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463936] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463962] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.463990] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.464019] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.464044] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.464067] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.464092] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.464117] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.464145] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.464171] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.465412] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 27 20:54:39 node-2 kernel: [    0.465416] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 20:54:39 node-2 kernel: [    0.466533] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 20:54:39 node-2 kernel: [    0.467048] PCI host bridge to bus 0000:00
Jul 27 20:54:39 node-2 kernel: [    0.467050] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 27 20:54:39 node-2 kernel: [    0.467052] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 27 20:54:39 node-2 kernel: [    0.467053] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 27 20:54:39 node-2 kernel: [    0.467055] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 27 20:54:39 node-2 kernel: [    0.467056] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 27 20:54:39 node-2 kernel: [    0.467058] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 27 20:54:39 node-2 kernel: [    0.467059] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 27 20:54:39 node-2 kernel: [    0.467065] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 27 20:54:39 node-2 kernel: [    0.467147] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.467178] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.467222] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 27 20:54:39 node-2 kernel: [    0.467241] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.467270] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.467310] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 27 20:54:39 node-2 kernel: [    0.467328] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.467358] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.467397] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 27 20:54:39 node-2 kernel: [    0.467414] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.467484] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.467559] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.467637] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 20:54:39 node-2 kernel: [    0.467642] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 27 20:54:39 node-2 kernel: [    0.467727] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 27 20:54:39 node-2 kernel: [    0.467874] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 27 20:54:39 node-2 kernel: [    0.467892] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 27 20:54:39 node-2 kernel: [    0.467970] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.468025] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 27 20:54:39 node-2 kernel: [    0.468047] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.468103] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.468146] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 27 20:54:39 node-2 kernel: [    0.468174] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.468230] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.468273] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 27 20:54:39 node-2 kernel: [    0.468297] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 27 20:54:39 node-2 kernel: [    0.468315] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 27 20:54:39 node-2 kernel: [    0.468393] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.468442] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 27 20:54:39 node-2 kernel: [    0.468470] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 27 20:54:39 node-2 kernel: [    0.468720] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 27 20:54:39 node-2 kernel: [    0.468726] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 27 20:54:39 node-2 kernel: [    0.468732] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.468738] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.468745] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 27 20:54:39 node-2 kernel: [    0.468775] pci 0000:01:00.0: supports D1 D2
Jul 27 20:54:39 node-2 kernel: [    0.474944] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 20:54:39 node-2 kernel: [    0.474951] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 20:54:39 node-2 kernel: [    0.474955] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 20:54:39 node-2 kernel: [    0.475117] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.475150] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 27 20:54:39 node-2 kernel: [    0.482941] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 20:54:39 node-2 kernel: [    0.482947] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.482951] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 20:54:39 node-2 kernel: [    0.483036] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.483108] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.483197] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.483243] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 20:54:39 node-2 kernel: [    0.483246] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.483248] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 20:54:39 node-2 kernel: [    0.483304] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.483431] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.483485] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 20:54:39 node-2 kernel: [    0.483488] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.483490] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.483539] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.483657] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.483698] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.483816] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.483854] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.483973] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.484010] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 27 20:54:39 node-2 kernel: [    0.484129] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 27 20:54:39 node-2 kernel: [    0.484169] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 20:54:39 node-2 kernel: [    0.484172] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.484174] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.484233] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 27 20:54:39 node-2 kernel: [    0.484311] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.484362] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.484402] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 27 20:54:39 node-2 kernel: [    0.484482] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 27 20:54:39 node-2 kernel: [    0.484588] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 20:54:39 node-2 kernel: [    0.484591] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.484593] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.484649] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 27 20:54:39 node-2 kernel: [    0.484703] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.484751] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.484966] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 20:54:39 node-2 kernel: [    0.484969] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 20:54:39 node-2 kernel: [    0.485031] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 27 20:54:39 node-2 kernel: [    0.485083] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.485132] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.485367] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 20:54:39 node-2 kernel: [    0.485370] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 20:54:39 node-2 kernel: [    0.485431] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 27 20:54:39 node-2 kernel: [    0.485492] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.485544] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 27 20:54:39 node-2 kernel: [    0.485763] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 20:54:39 node-2 kernel: [    0.485767] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 20:54:39 node-2 kernel: [    0.485943] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 20:54:39 node-2 kernel: [    0.485981] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 20:54:39 node-2 kernel: [    0.486055] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 27 20:54:39 node-2 kernel: [    0.486073] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 27 20:54:39 node-2 kernel: [    0.486086] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 27 20:54:39 node-2 kernel: [    0.486100] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 27 20:54:39 node-2 kernel: [    0.486150] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 27 20:54:39 node-2 kernel: [    0.490947] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 20:54:39 node-2 kernel: [    0.490956] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 20:54:39 node-2 kernel: [    0.491009] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 27 20:54:39 node-2 kernel: [    0.491618] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 27 20:54:39 node-2 kernel: [    0.491621] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 20:54:39 node-2 kernel: [    0.491745] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 20:54:39 node-2 kernel: [    0.491849] PCI host bridge to bus 0000:80
Jul 27 20:54:39 node-2 kernel: [    0.491852] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 27 20:54:39 node-2 kernel: [    0.491853] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 27 20:54:39 node-2 kernel: [    0.491854] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 27 20:54:39 node-2 kernel: [    0.491862] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.491925] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.491992] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 20:54:39 node-2 kernel: [    0.492053] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 20:54:39 node-2 kernel: [    0.492059] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 27 20:54:39 node-2 kernel: [    0.492129] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 27 20:54:39 node-2 kernel: [    0.492426] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 27 20:54:39 node-2 kernel: [    0.492458] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 27 20:54:39 node-2 kernel: [    0.492487] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 27 20:54:39 node-2 kernel: [    0.492516] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 27 20:54:39 node-2 kernel: [    0.492545] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 20:54:39 node-2 kernel: [    0.492575] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 20:54:39 node-2 kernel: [    0.492605] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 20:54:39 node-2 kernel: [    0.492635] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 20:54:39 node-2 kernel: [    0.492719] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 27 20:54:39 node-2 kernel: [    0.492723] ACPI: \_SB_.UNC1: notify handler is installed
Jul 27 20:54:39 node-2 kernel: [    0.492724] ACPI: \_SB_.UNC0: notify handler is installed
Jul 27 20:54:39 node-2 kernel: [    0.492739] ACPI: \_SB_.PCI0: notify handler is installed
Jul 27 20:54:39 node-2 kernel: [    0.492792] ACPI: \_SB_.PCI1: notify handler is installed
Jul 27 20:54:39 node-2 kernel: [    0.492871] Found 4 acpi root devices
Jul 27 20:54:39 node-2 kernel: [    0.492976] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 27 20:54:39 node-2 kernel: [    0.492978] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 27 20:54:39 node-2 kernel: [    0.492979] vgaarb: loaded
Jul 27 20:54:39 node-2 kernel: [    0.492980] vgaarb: bridge control possible 0000:0c:00.0
Jul 27 20:54:39 node-2 kernel: [    0.493094] SCSI subsystem initialized
Jul 27 20:54:39 node-2 kernel: [    0.493158] libata version 3.00 loaded.
Jul 27 20:54:39 node-2 kernel: [    0.493172] ACPI: bus type USB registered
Jul 27 20:54:39 node-2 kernel: [    0.493183] usbcore: registered new interface driver usbfs
Jul 27 20:54:39 node-2 kernel: [    0.493187] usbcore: registered new interface driver hub
Jul 27 20:54:39 node-2 kernel: [    0.493211] usbcore: registered new device driver usb
Jul 27 20:54:39 node-2 kernel: [    0.493375] PCI: Using ACPI for IRQ routing
Jul 27 20:54:39 node-2 kernel: [    0.496991] PCI: pci_cache_line_size set to 64 bytes
Jul 27 20:54:39 node-2 kernel: [    0.497198] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 27 20:54:39 node-2 kernel: [    0.497199] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 27 20:54:39 node-2 kernel: [    0.497200] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 27 20:54:39 node-2 kernel: [    0.497264] NetLabel: Initializing
Jul 27 20:54:39 node-2 kernel: [    0.497266] NetLabel:  domain hash size = 128
Jul 27 20:54:39 node-2 kernel: [    0.497266] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 27 20:54:39 node-2 kernel: [    0.497276] NetLabel:  unlabeled traffic allowed by default
Jul 27 20:54:39 node-2 kernel: [    0.497332] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 27 20:54:39 node-2 kernel: [    0.497336] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 27 20:54:39 node-2 kernel: [    0.499393] Switched to clocksource hpet
Jul 27 20:54:39 node-2 kernel: [    0.503222] AppArmor: AppArmor Filesystem Enabled
Jul 27 20:54:39 node-2 kernel: [    0.503235] pnp: PnP ACPI init
Jul 27 20:54:39 node-2 kernel: [    0.503242] ACPI: bus type PNP registered
Jul 27 20:54:39 node-2 kernel: [    0.503358] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503367] pnp 00:01: [dma 4]
Jul 27 20:54:39 node-2 kernel: [    0.503378] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503409] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503429] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503446] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503480] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503530] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503532] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 27 20:54:39 node-2 kernel: [    0.503534] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503535] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503537] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503541] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503543] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 27 20:54:39 node-2 kernel: [    0.503545] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503546] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503548] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503549] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503551] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503552] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 27 20:54:39 node-2 kernel: [    0.503555] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503638] pnp 00:07: [dma 0 disabled]
Jul 27 20:54:39 node-2 kernel: [    0.503666] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503740] pnp 00:08: [dma 0 disabled]
Jul 27 20:54:39 node-2 kernel: [    0.503771] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 20:54:39 node-2 kernel: [    0.503821] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 27 20:54:39 node-2 kernel: [    0.504169] pnp: PnP ACPI: found 10 devices
Jul 27 20:54:39 node-2 kernel: [    0.504171] ACPI: bus type PNP unregistered
Jul 27 20:54:39 node-2 kernel: [    0.510443] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 20:54:39 node-2 kernel: [    0.510446] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 20:54:39 node-2 kernel: [    0.510449] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 20:54:39 node-2 kernel: [    0.510453] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 20:54:39 node-2 kernel: [    0.510455] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510470] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510503] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 20:54:39 node-2 kernel: [    0.510517] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510546] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 20:54:39 node-2 kernel: [    0.510560] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 20:54:39 node-2 kernel: [    0.510589] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 20:54:39 node-2 kernel: [    0.510604] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 20:54:39 node-2 kernel: [    0.510633] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 20:54:39 node-2 kernel: [    0.510634] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510649] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510678] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 20:54:39 node-2 kernel: [    0.510680] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510694] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510723] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 20:54:39 node-2 kernel: [    0.510725] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510728] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510732] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 20:54:39 node-2 kernel: [    0.510734] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510736] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510740] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 20:54:39 node-2 kernel: [    0.510744] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 20:54:39 node-2 kernel: [    0.510752] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 20:54:39 node-2 kernel: [    0.510756] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 20:54:39 node-2 kernel: [    0.510762] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 27 20:54:39 node-2 kernel: [    0.510763] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 27 20:54:39 node-2 kernel: [    0.510764] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 27 20:54:39 node-2 kernel: [    0.510764] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 27 20:54:39 node-2 kernel: [    0.510765] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 27 20:54:39 node-2 kernel: [    0.510766] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 27 20:54:39 node-2 kernel: [    0.510767] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 27 20:54:39 node-2 kernel: [    0.510768] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 27 20:54:39 node-2 kernel: [    0.510769] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510770] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510771] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510772] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510773] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510773] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510774] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510775] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510776] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 27 20:54:39 node-2 kernel: [    0.510777] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510778] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 27 20:54:39 node-2 kernel: [    0.510779] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 27 20:54:39 node-2 kernel: [    0.510780] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 27 20:54:39 node-2 kernel: [    0.510781] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 27 20:54:39 node-2 kernel: [    0.510783] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 27 20:54:39 node-2 kernel: [    0.510784] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 27 20:54:39 node-2 kernel: [    0.510824] NET: Registered protocol family 2
Jul 27 20:54:39 node-2 kernel: [    0.511082] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.511420] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.511564] TCP: Hash tables configured (established 262144 bind 65536)
Jul 27 20:54:39 node-2 kernel: [    0.511607] TCP: reno registered
Jul 27 20:54:39 node-2 kernel: [    0.511636] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.511731] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.511882] NET: Registered protocol family 1
Jul 27 20:54:39 node-2 kernel: [    0.547492] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 27 20:54:39 node-2 kernel: [    0.547506] PCI: CLS 64 bytes, default 64
Jul 27 20:54:39 node-2 kernel: [    0.547580] Trying to unpack rootfs image as initramfs...
Jul 27 20:54:39 node-2 kernel: [    0.766871] Freeing initrd memory: 20396K (ffff88003581a000 - ffff880036c05000)
Jul 27 20:54:39 node-2 kernel: [    0.766913] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 27 20:54:39 node-2 kernel: [    0.766916] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 27 20:54:39 node-2 kernel: [    0.767354] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767360] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767365] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767371] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767380] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767391] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767400] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767409] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767417] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767427] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767433] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767440] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767446] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767454] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767462] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767469] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 20:54:39 node-2 kernel: [    0.767547] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 27 20:54:39 node-2 kernel: [    0.767550] Scanning for low memory corruption every 60 seconds
Jul 27 20:54:39 node-2 kernel: [    0.767921] Initialise system trusted keyring
Jul 27 20:54:39 node-2 kernel: [    0.767973] audit: initializing netlink socket (disabled)
Jul 27 20:54:39 node-2 kernel: [    0.767989] type=2000 audit(1469652841.724:1): initialized
Jul 27 20:54:39 node-2 kernel: [    0.785886] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 27 20:54:39 node-2 kernel: [    0.787402] zbud: loaded
Jul 27 20:54:39 node-2 kernel: [    0.787527] VFS: Disk quotas dquot_6.5.2
Jul 27 20:54:39 node-2 kernel: [    0.787564] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 27 20:54:39 node-2 kernel: [    0.787952] fuse init (API version 7.22)
Jul 27 20:54:39 node-2 kernel: [    0.788011] msgmni has been set to 32768
Jul 27 20:54:39 node-2 kernel: [    0.788058] Key type big_key registered
Jul 27 20:54:39 node-2 kernel: [    0.788577] Key type asymmetric registered
Jul 27 20:54:39 node-2 kernel: [    0.788579] Asymmetric key parser 'x509' registered
Jul 27 20:54:39 node-2 kernel: [    0.788609] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 27 20:54:39 node-2 kernel: [    0.788680] io scheduler noop registered
Jul 27 20:54:39 node-2 kernel: [    0.788682] io scheduler deadline registered (default)
Jul 27 20:54:39 node-2 kernel: [    0.788700] io scheduler cfq registered
Jul 27 20:54:39 node-2 kernel: [    0.789176] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    0.789294] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    0.789412] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    0.789522] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    0.789636] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    0.789734] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    0.790135] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 27 20:54:39 node-2 kernel: [    0.790182] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 27 20:54:39 node-2 kernel: [    0.790209] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 27 20:54:39 node-2 kernel: [    0.790227] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790232] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790238] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 27 20:54:39 node-2 kernel: [    0.790248] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790252] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790256] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790260] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790264] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790268] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790271] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790275] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790279] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790282] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790286] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790289] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790295] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 27 20:54:39 node-2 kernel: [    0.790305] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790311] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 27 20:54:39 node-2 kernel: [    0.790335] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790341] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 27 20:54:39 node-2 kernel: [    0.790360] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790364] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 27 20:54:39 node-2 kernel: [    0.790371] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 27 20:54:39 node-2 kernel: [    0.790429] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 27 20:54:39 node-2 kernel: [    0.790441] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 27 20:54:39 node-2 kernel: [    0.790451] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 27 20:54:39 node-2 kernel: [    0.790473] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 27 20:54:39 node-2 kernel: [    0.790561] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 27 20:54:39 node-2 kernel: [    0.790578] vesafb: scrolling: redraw
Jul 27 20:54:39 node-2 kernel: [    0.790580] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 27 20:54:39 node-2 kernel: [    0.811290] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 27 20:54:39 node-2 kernel: [    0.819809] Console: switching to colour frame buffer device 80x30
Jul 27 20:54:39 node-2 kernel: [    0.828477] fb0: VESA VGA frame buffer device
Jul 27 20:54:39 node-2 kernel: [    0.828674] intel_idle: MWAIT substates: 0x2120
Jul 27 20:54:39 node-2 kernel: [    0.828675] intel_idle: v0.4 model 0x3F
Jul 27 20:54:39 node-2 kernel: [    0.828675] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 27 20:54:39 node-2 kernel: [    0.828913] ipmi message handler version 39.2
Jul 27 20:54:39 node-2 kernel: [    0.829180] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 27 20:54:39 node-2 kernel: [    0.829611] ACPI: AC Adapter [P111] (on-line)
Jul 27 20:54:39 node-2 kernel: [    0.834853] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 27 20:54:39 node-2 kernel: [    0.845888] ACPI: Power Button [PWRB]
Jul 27 20:54:39 node-2 kernel: [    0.851654] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 27 20:54:39 node-2 kernel: [    0.863366] ACPI: Power Button [PWRF]
Jul 27 20:54:39 node-2 kernel: [    0.888938] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 27 20:54:39 node-2 kernel: [    0.900622] pstore: Registered erst as persistent store backend
Jul 27 20:54:39 node-2 kernel: [    0.906825] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 27 20:54:39 node-2 kernel: [    0.918782] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 27 20:54:39 node-2 kernel: [    0.945530] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 27 20:54:39 node-2 kernel: [    0.978813] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 27 20:54:39 node-2 kernel: [    0.992900] Linux agpgart interface v0.103
Jul 27 20:54:39 node-2 kernel: [    1.000568] brd: module loaded
Jul 27 20:54:39 node-2 kernel: [    1.007608] loop: module loaded
Jul 27 20:54:39 node-2 kernel: [    1.014330] libphy: Fixed MDIO Bus: probed
Jul 27 20:54:39 node-2 kernel: [    1.020803] tun: Universal TUN/TAP device driver, 1.6
Jul 27 20:54:39 node-2 kernel: [    1.027265] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 27 20:54:39 node-2 kernel: [    1.033789] PPP generic driver version 2.4.2
Jul 27 20:54:39 node-2 kernel: [    1.040181] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 27 20:54:39 node-2 kernel: [    1.046666] ehci-pci: EHCI PCI platform driver
Jul 27 20:54:39 node-2 kernel: [    1.053273] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 27 20:54:39 node-2 kernel: [    1.059761] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 27 20:54:39 node-2 kernel: [    1.072288] ehci-pci 0000:00:1a.0: debug port 2
Jul 27 20:54:39 node-2 kernel: [    1.082483] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 27 20:54:39 node-2 kernel: [    1.082500] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 27 20:54:39 node-2 kernel: [    1.098889] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 27 20:54:39 node-2 kernel: [    1.104952] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 20:54:39 node-2 kernel: [    1.111126] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 20:54:39 node-2 kernel: [    1.123037] usb usb1: Product: EHCI Host Controller
Jul 27 20:54:39 node-2 kernel: [    1.129060] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 20:54:39 node-2 kernel: [    1.135101] usb usb1: SerialNumber: 0000:00:1a.0
Jul 27 20:54:39 node-2 kernel: [    1.141053] hub 1-0:1.0: USB hub found
Jul 27 20:54:39 node-2 kernel: [    1.146823] hub 1-0:1.0: 2 ports detected
Jul 27 20:54:39 node-2 kernel: [    1.152642] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 27 20:54:39 node-2 kernel: [    1.158227] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 27 20:54:39 node-2 kernel: [    1.169126] ehci-pci 0000:00:1d.0: debug port 2
Jul 27 20:54:39 node-2 kernel: [    1.178434] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 27 20:54:39 node-2 kernel: [    1.178437] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 27 20:54:39 node-2 kernel: [    1.194807] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 27 20:54:39 node-2 kernel: [    1.200009] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 20:54:39 node-2 kernel: [    1.205318] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 20:54:39 node-2 kernel: [    1.215896] usb usb2: Product: EHCI Host Controller
Jul 27 20:54:39 node-2 kernel: [    1.221365] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 20:54:39 node-2 kernel: [    1.226921] usb usb2: SerialNumber: 0000:00:1d.0
Jul 27 20:54:39 node-2 kernel: [    1.232436] hub 2-0:1.0: USB hub found
Jul 27 20:54:39 node-2 kernel: [    1.237796] hub 2-0:1.0: 2 ports detected
Jul 27 20:54:39 node-2 kernel: [    1.243090] ehci-platform: EHCI generic platform driver
Jul 27 20:54:39 node-2 kernel: [    1.248322] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 27 20:54:39 node-2 kernel: [    1.253639] ohci-pci: OHCI PCI platform driver
Jul 27 20:54:39 node-2 kernel: [    1.258932] ohci-platform: OHCI generic platform driver
Jul 27 20:54:39 node-2 kernel: [    1.264135] uhci_hcd: USB Universal Host Controller Interface driver
Jul 27 20:54:39 node-2 kernel: [    1.269470] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 27 20:54:39 node-2 kernel: [    1.470570] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 27 20:54:39 node-2 kernel: [    1.762335] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 27 20:54:39 node-2 kernel: [    1.778647] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 27 20:54:39 node-2 kernel: [    1.784274] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 20:54:39 node-2 kernel: [    1.790040] hub 1-1:1.0: USB hub found
Jul 27 20:54:39 node-2 kernel: [    1.795634] hub 1-1:1.0: 6 ports detected
Jul 27 20:54:39 node-2 kernel: [    1.914218] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 27 20:54:39 node-2 kernel: [    2.308161] i8042: No controller found
Jul 27 20:54:39 node-2 kernel: [    2.313767] mousedev: PS/2 mouse device common for all mice
Jul 27 20:54:39 node-2 kernel: [    2.319489] rtc_cmos 00:02: RTC can wake from S4
Jul 27 20:54:39 node-2 kernel: [    2.325204] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 27 20:54:39 node-2 kernel: [    2.326622] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 27 20:54:39 node-2 kernel: [    2.326623] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 20:54:39 node-2 kernel: [    2.327387] hub 2-1:1.0: USB hub found
Jul 27 20:54:39 node-2 kernel: [    2.327621] hub 2-1:1.0: 8 ports detected
Jul 27 20:54:39 node-2 kernel: [    2.353296] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 27 20:54:39 node-2 kernel: [    2.364591] device-mapper: uevent: version 1.0.3
Jul 27 20:54:39 node-2 kernel: [    2.370293] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 27 20:54:39 node-2 kernel: [    2.381648] ledtrig-cpu: registered to indicate activity on CPUs
Jul 27 20:54:39 node-2 kernel: [    2.387613] TCP: cubic registered
Jul 27 20:54:39 node-2 kernel: [    2.393455] NET: Registered protocol family 10
Jul 27 20:54:39 node-2 kernel: [    2.399512] NET: Registered protocol family 17
Jul 27 20:54:39 node-2 kernel: [    2.405270] Key type dns_resolver registered
Jul 27 20:54:39 node-2 kernel: [    2.411296] Loading compiled-in X.509 certificates
Jul 27 20:54:39 node-2 kernel: [    2.417496] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 27 20:54:39 node-2 kernel: [    2.429077] registered taskstats version 1
Jul 27 20:54:39 node-2 kernel: [    2.437092] Key type trusted registered
Jul 27 20:54:39 node-2 kernel: [    2.444678] Key type encrypted registered
Jul 27 20:54:39 node-2 kernel: [    2.450173] AppArmor: AppArmor sha1 policy hashing enabled
Jul 27 20:54:39 node-2 kernel: [    2.455655] IMA: No TPM chip found, activating TPM-bypass!
Jul 27 20:54:39 node-2 kernel: [    2.461747] regulator-dummy: disabling
Jul 27 20:54:39 node-2 kernel: [    2.467228]   Magic number: 8:50:954
Jul 27 20:54:39 node-2 kernel: [    2.472835] processor cpu9: hash matches
Jul 27 20:54:39 node-2 kernel: [    2.478239] memory memory7: hash matches
Jul 27 20:54:39 node-2 kernel: [    2.483527] rtc_cmos 00:02: setting system clock to 2016-07-27 20:54:04 UTC (1469652844)
Jul 27 20:54:39 node-2 kernel: [    2.495573] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 27 20:54:39 node-2 kernel: [    2.501095] EDD information not available.
Jul 27 20:54:39 node-2 kernel: [    2.506562] PM: Hibernation image not present or could not be loaded.
Jul 27 20:54:39 node-2 kernel: [    2.507417] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 27 20:54:39 node-2 kernel: [    2.518488] Write protecting the kernel read-only data: 12288k
Jul 27 20:54:39 node-2 kernel: [    2.524800] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 27 20:54:39 node-2 kernel: [    2.537412] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 27 20:54:39 node-2 kernel: [    2.569265] device-mapper: multipath: version 1.6.0 loaded
Jul 27 20:54:39 node-2 kernel: [    2.576974] systemd-udevd[215]: starting version 204
Jul 27 20:54:39 node-2 kernel: [    2.595742] md: linear personality registered for level -1
Jul 27 20:54:39 node-2 kernel: [    2.605790] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 27 20:54:39 node-2 kernel: [    2.616401] md: multipath personality registered for level -4
Jul 27 20:54:39 node-2 kernel: [    2.624680] md: raid0 personality registered for level 0
Jul 27 20:54:39 node-2 kernel: [    2.633171] md: raid1 personality registered for level 1
Jul 27 20:54:39 node-2 kernel: [    2.641190] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 27 20:54:39 node-2 kernel: [    2.647407] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 27 20:54:39 node-2 kernel: [    2.647632] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 27 20:54:39 node-2 kernel: [    2.649148] megasas: FW now in Ready state
Jul 27 20:54:39 node-2 kernel: [    2.649883] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.649993] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.650103] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.650205] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.650350] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.650511] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.650631] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.650785] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.650898] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.651058] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.651226] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.651327] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.651394] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.651511] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.651585] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.651712] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.652399] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 27 20:54:39 node-2 kernel: [    2.687285] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 27 20:54:39 node-2 kernel: [    2.700635] 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
Jul 27 20:54:39 node-2 kernel: [    2.705588] raid6: sse2x1   10373 MB/s
Jul 27 20:54:39 node-2 kernel: [    2.721361] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 20:54:39 node-2 kernel: [    2.728369] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.728374] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.728377] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.728381] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.728418] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 20:54:39 node-2 kernel: [    2.741830] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 27 20:54:39 node-2 kernel: [    2.748731] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 27 20:54:39 node-2 kernel: [    2.760466] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 27 20:54:39 node-2 kernel: [    2.760494] 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
Jul 27 20:54:39 node-2 kernel: [    2.760506] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 20:54:39 node-2 kernel: [    2.773725] raid6: sse2x2   10923 MB/s
Jul 27 20:54:39 node-2 kernel: [    2.803030] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 27 20:54:39 node-2 kernel: [    2.809993] usb 2-1.4: Manufacturer: Avocent
Jul 27 20:54:39 node-2 kernel: [    2.816775] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 27 20:54:39 node-2 kernel: [    2.841426] raid6: sse2x4    9737 MB/s
Jul 27 20:54:39 node-2 kernel: [    2.913361] raid6: avx2x1   14938 MB/s
Jul 27 20:54:39 node-2 kernel: [    2.985297] raid6: avx2x2   18871 MB/s
Jul 27 20:54:39 node-2 kernel: [    3.057237] raid6: avx2x4   21293 MB/s
Jul 27 20:54:39 node-2 kernel: [    3.063433] raid6: using algorithm avx2x4 (21293 MB/s)
Jul 27 20:54:39 node-2 kernel: [    3.069613] raid6: using avx2x2 recovery algorithm
Jul 27 20:54:39 node-2 kernel: [    3.075685] megasas:IOC Init cmd success
Jul 27 20:54:39 node-2 kernel: [    3.075687] Switched to clocksource tsc
Jul 27 20:54:39 node-2 kernel: [    3.076315] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.079202] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.079246] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.079285] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.079381] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.100037] xor: automatically using best checksumming function:
Jul 27 20:54:39 node-2 kernel: [    3.106036] hidraw: raw HID events driver (C) Jiri Kosina
Jul 27 20:54:39 node-2 kernel: [    3.106743] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 27 20:54:39 node-2 kernel: [    3.106745] 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
Jul 27 20:54:39 node-2 kernel: [    3.106746] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 20:54:39 node-2 kernel: [    3.107025] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.107165] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.107278] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.107384] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.107582] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.121230] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 27 20:54:39 node-2 kernel: [    3.121262] 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
Jul 27 20:54:39 node-2 kernel: [    3.121263] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 20:54:39 node-2 kernel: [    3.121488] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.121565] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.121684] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.121821] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.121994] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 20:54:39 node-2 kernel: [    3.125883] megasas: INIT adapter done
Jul 27 20:54:39 node-2 kernel: [    3.145157]    avx       : 35648.000 MB/sec
Jul 27 20:54:39 node-2 kernel: [    3.197833] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 27 20:54:39 node-2 kernel: [    3.199578] scsi0 : LSI SAS based MegaRAID driver
Jul 27 20:54:39 node-2 kernel: [    3.207437] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 20:54:39 node-2 kernel: [    3.229642] async_tx: api initialized (async)
Jul 27 20:54:39 node-2 kernel: [    3.236660] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 20:54:39 node-2 kernel: [    3.250094] usbcore: registered new interface driver usbhid
Jul 27 20:54:39 node-2 kernel: [    3.256522] usbhid: USB HID core driver
Jul 27 20:54:39 node-2 kernel: [    3.263874] 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
Jul 27 20:54:39 node-2 kernel: [    3.277012] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 27 20:54:39 node-2 kernel: [    3.277062] 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
Jul 27 20:54:39 node-2 kernel: [    3.277176] 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
Jul 27 20:54:39 node-2 kernel: [    3.277234] 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
Jul 27 20:54:39 node-2 kernel: [    3.277287] 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
Jul 27 20:54:39 node-2 kernel: [    3.277328] 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
Jul 27 20:54:39 node-2 kernel: [    3.351130] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 27 20:54:39 node-2 kernel: [    3.351450] md: raid6 personality registered for level 6
Jul 27 20:54:39 node-2 kernel: [    3.351450] md: raid5 personality registered for level 5
Jul 27 20:54:39 node-2 kernel: [    3.351450] md: raid4 personality registered for level 4
Jul 27 20:54:39 node-2 kernel: [    3.385614] sd 0:2:0:0: [sda] Write Protect is off
Jul 27 20:54:39 node-2 kernel: [    3.392252] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 27 20:54:39 node-2 kernel: [    3.392271] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 27 20:54:39 node-2 kernel: [    3.407241] md: raid10 personality registered for level 10
Jul 27 20:54:39 node-2 kernel: [    3.429877]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 27 20:54:39 node-2 kernel: [    3.435543] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 27 20:54:39 node-2 kernel: [    3.477686] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Jul 27 20:54:39 node-2 kernel: [    3.561879] random: lvm urandom read with 30 bits of entropy available
Jul 27 20:54:39 node-2 kernel: [    3.704013] bio: create slab <bio-1> at 1
Jul 27 20:54:39 node-2 kernel: [    4.497783] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 20:54:39 node-2 kernel: [    5.192401] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 27 20:54:39 node-2 kernel: [    5.229196] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 27 20:54:39 node-2 kernel: [    5.362212] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 27 20:54:39 node-2 kernel: [    5.392173] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 27 20:54:39 node-2 kernel: [    5.449826] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 20:54:39 node-2 kernel: [    5.453599] random: nonblocking pool is initialized
Jul 27 20:54:39 node-2 kernel: [    5.670324] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 27 20:54:39 node-2 kernel: [    5.706000] XFS (dm-1): Mounting Filesystem
Jul 27 20:54:39 node-2 kernel: [    5.924318] XFS (dm-1): Ending clean mount
Jul 27 20:54:39 node-2 kernel: [    5.983057] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 20:54:39 node-2 kernel: [    6.009555] XFS (dm-2): Mounting Filesystem
Jul 27 20:54:39 node-2 kernel: [    6.147482] XFS (dm-2): Ending clean mount
Jul 27 20:54:39 node-2 kernel: [    6.231655] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 20:54:39 node-2 kernel: [    8.170898] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 20:54:39 node-2 kernel: [    8.185713] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 20:54:39 node-2 kernel: [    8.356951] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 27 20:54:39 node-2 kernel: [    8.356955] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 27 20:54:39 node-2 kernel: [    8.356959] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 27 20:54:39 node-2 kernel: [    8.356963] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 27 20:54:39 node-2 kernel: [    8.389215] systemd-udevd[799]: starting version 204
Jul 27 20:54:39 node-2 kernel: [    8.670163] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 27 20:54:39 node-2 kernel: [    8.670168] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 20:54:39 node-2 kernel: [    8.670171] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 27 20:54:39 node-2 kernel: [    8.670172] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 20:54:39 node-2 kernel: [    8.670185] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 27 20:54:39 node-2 kernel: [    8.670607] power_meter ACPI000D:00: Found ACPI power meter.
Jul 27 20:54:39 node-2 kernel: [    8.670614] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 27 20:54:39 node-2 kernel: [    8.702767] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 27 20:54:39 node-2 kernel: [    8.719488] IPMI System Interface driver.
Jul 27 20:54:39 node-2 kernel: [    8.719551] ipmi_si: probing via ACPI
Jul 27 20:54:39 node-2 kernel: [    8.719577] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 27 20:54:39 node-2 kernel: [    8.719578] ipmi_si: Adding ACPI-specified kcs state machine
Jul 27 20:54:39 node-2 kernel: [    8.719598] ipmi_si: probing via SMBIOS
Jul 27 20:54:39 node-2 kernel: [    8.719600] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 20:54:39 node-2 kernel: [    8.719600] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 27 20:54:39 node-2 kernel: [    8.719602] ipmi_si: probing via SPMI
Jul 27 20:54:39 node-2 kernel: [    8.719603] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 20:54:39 node-2 kernel: [    8.719604] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 27 20:54:39 node-2 kernel: [    8.719606] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 27 20:54:39 node-2 kernel: [    8.723193] wmi: Mapper loaded
Jul 27 20:54:39 node-2 kernel: [    8.785737] systemd-udevd[837]: renamed network interface eth0 to enp6s0
Jul 27 20:54:39 node-2 kernel: [    8.820747] systemd-udevd[844]: renamed network interface eth3 to enp9s0
Jul 27 20:54:39 node-2 kernel: [    8.844762] systemd-udevd[838]: renamed network interface eth1 to enp7s0
Jul 27 20:54:39 node-2 kernel: [    8.858285] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 27 20:54:39 node-2 kernel: [    8.858291] ipmi_si 00:09: IPMI kcs interface initialized
Jul 27 20:54:39 node-2 kernel: [    8.875018] systemd-udevd[836]: renamed network interface eth2 to enp8s0
Jul 27 20:54:39 node-2 kernel: [    9.136570] type=1400 audit(1469652851.157:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1071 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.136731] type=1400 audit(1469652851.157:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1071 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.136877] type=1400 audit(1469652851.157:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1071 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.136982] type=1400 audit(1469652851.157:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1083 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.137127] type=1400 audit(1469652851.157:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1083 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.137253] type=1400 audit(1469652851.157:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1083 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.153855] type=1400 audit(1469652851.173:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.154091] type=1400 audit(1469652851.173:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.154292] type=1400 audit(1469652851.173:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.169204] type=1400 audit(1469652851.189:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Jul 27 20:54:39 node-2 kernel: [    9.744650] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 20:54:39 node-2 kernel: [    9.745580] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 20:54:39 node-2 kernel: [    9.978721] enic 0000:06:00.0 enp6s0: Link UP
Jul 27 20:54:39 node-2 kernel: [    9.979552] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 27 20:54:39 node-2 kernel: [    9.979563] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 27 20:54:39 node-2 kernel: [   20.390230] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 27 20:54:39 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 27 20:54:40 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 27 20:54:41 node-2 kernel: [   39.797562] init: failsafe main process (8430) killed by TERM signal
Jul 27 20:54:41 node-2 dbus[8462]: [system] AppArmor D-Bus mediation is enabled
Jul 27 20:54:41 node-2 kernel: [   40.028733] audit_printk_skb: 30 callbacks suppressed
Jul 27 20:54:41 node-2 kernel: [   40.028735] type=1400 audit(1469652881.251:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8558 comm="apparmor_parser"
Jul 27 20:54:41 node-2 kernel: [   40.028928] type=1400 audit(1469652881.251:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8557 comm="apparmor_parser"
Jul 27 20:54:41 node-2 kernel: [   40.028933] type=1400 audit(1469652881.251:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8557 comm="apparmor_parser"
Jul 27 20:54:41 node-2 kernel: [   40.028935] type=1400 audit(1469652881.251:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8557 comm="apparmor_parser"
Jul 27 20:54:41 node-2 kernel: [   40.029158] type=1400 audit(1469652881.251:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8557 comm="apparmor_parser"
Jul 27 20:54:41 node-2 kernel: [   40.029161] type=1400 audit(1469652881.251:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8557 comm="apparmor_parser"
Jul 27 20:54:41 node-2 kernel: [   40.029274] type=1400 audit(1469652881.251:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8557 comm="apparmor_parser"
Jul 27 20:54:41 node-2 kernel: [   40.098740] type=1400 audit(1469652881.323:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8560 comm="apparmor_parser"
Jul 27 20:54:41 node-2 anacron[8622]: Anacron 2.3 started on 2016-07-27
Jul 27 20:54:41 node-2 cron[8588]: (CRON) INFO (pidfile fd = 3)
Jul 27 20:54:41 node-2 cron[8627]: (CRON) STARTUP (fork ok)
Jul 27 20:54:41 node-2 anacron[8622]: Will run job `cron.daily' in 5 min.
Jul 27 20:54:41 node-2 anacron[8622]: Will run job `cron.weekly' in 10 min.
Jul 27 20:54:41 node-2 anacron[8622]: Will run job `cron.monthly' in 15 min.
Jul 27 20:54:41 node-2 anacron[8622]: Jobs will be executed sequentially
Jul 27 20:54:41 node-2 multipathd: path checkers start up
Jul 27 20:54:41 node-2 cron[8627]: (CRON) INFO (Running @reboot jobs)
Jul 27 20:54:41 node-2 postfix/master[8767]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 27 20:54:45 node-2 puppet-agent[8951]: Reopening log files
Jul 27 20:54:45 node-2 puppet-agent[8951]: Could not request certificate: Connection refused - connect(2)
Jul 27 20:54:57 node-2 puppet-user[9030]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 27 20:54:57 node-2 puppet-user[9030]: Compiled catalog for node-2.domain.tld in environment production in 0.01 seconds
Jul 27 20:54:58 node-2 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 27 20:54:58 node-2 puppet-user[9030]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 27 20:54:58 node-2 puppet-user[9030]: Finished catalog run in 0.74 seconds
Jul 27 20:54:59 node-2 multipathd: uevent trigger error
Jul 27 20:54:59 node-2 puppet-user[9455]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 20:54:59 node-2 puppet-user[9455]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 27 20:54:59 node-2 puppet-user[9455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 27 20:55:00 node-2 puppet-user[9455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 27 20:55:00 node-2 puppet-user[9455]: (/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"]'
Jul 27 20:55:00 node-2 puppet-user[9455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 27 20:55:00 node-2 puppet-user[9455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 27 20:55:00 node-2 puppet-user[9455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 27 20:55:00 node-2 puppet-user[9455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 27 20:55:00 node-2 puppet-user[9455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 27 20:55:00 node-2 puppet-user[9455]: Finished catalog run in 0.08 seconds
Jul 27 20:55:01 node-2 puppet-user[9923]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 27 20:55:01 node-2 puppet-user[9923]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 27 20:55:01 node-2 puppet-user[9923]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 27 20:55:01 node-2 puppet-user[9923]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 27 20:55:01 node-2 puppet-user[9923]: Finished catalog run in 0.03 seconds
Jul 27 20:55:02 node-2 CRON[10347]: (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")
Jul 27 20:55:03 node-2 puppet-user[10399]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 27 20:55:03 node-2 puppet-user[10399]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 27 20:55:03 node-2 puppet-user[10399]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 27 20:55:03 node-2 puppet-user[10399]: Finished catalog run in 0.03 seconds
Jul 27 20:55:05 node-2 puppet-user[10866]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 27 20:55:05 node-2 puppet-user[10866]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Jul 27 20:55:05 node-2 puppet-user[10866]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 27 20:55:05 node-2 kernel: [   64.322452] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 27 20:55:05 node-2 kernel: [   64.322503] 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.
Jul 27 20:55:05 node-2 puppet-user[10866]: (/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'
Jul 27 20:55:06 node-2 puppet-user[10866]: Finished catalog run in 0.06 seconds
Jul 27 20:55:07 node-2 puppet-user[11394]: (Scope(Class[main])) MODULAR: sync_time
Jul 27 20:55:07 node-2 puppet-user[11394]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 27 20:55:07 node-2 ntpdate[11865]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 27 20:55:13 node-2 ntpdate[11865]: adjust time server 10.20.0.2 offset 0.000047 sec
Jul 27 20:55:13 node-2 puppet-user[11394]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 27 20:55:13 node-2 puppet-user[11394]: Finished catalog run in 6.19 seconds
Jul 27 20:55:19 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 20:55:19 node-2 nailgun-agent: D, [2016-07-27T20:55:02.131740 #10350] DEBUG -- : Sleep for 17 seconds before sending request
Jul 27 20:55:19 node-2 nailgun-agent: I, [2016-07-27T20:55:19.146478 #10350]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 20:55:19 node-2 nailgun-agent: D, [2016-07-27T20:55:19.542586 #10350] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 27 20:55:20 node-2 puppet-user[12067]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 20:55:20 node-2 puppet-user[12067]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 27 20:55:20 node-2 puppet-user[12067]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 27 20:55:20 node-2 puppet-user[12067]: Finished catalog run in 0.07 seconds
Jul 27 20:55:21 node-2 puppet-user[12837]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 27 20:55:22 node-2 puppet-user[12837]: Compiled catalog for node-2.domain.tld in environment production in 0.95 seconds
Jul 27 20:55:22 node-2 puppet-user[12837]: (/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
Jul 27 20:55:22 node-2 puppet-user[12837]: (/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
Jul 27 20:55:22 node-2 puppet-user[12837]: (/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
Jul 27 20:55:22 node-2 puppet-user[12837]: (/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
Jul 27 20:55:22 node-2 puppet-user[12837]: (/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
Jul 27 20:55:22 node-2 puppet-user[12837]: (/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
Jul 27 20:55:23 node-2 puppet-user[12837]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 27 20:55:23 node-2 puppet-user[12837]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 27 20:55:23 node-2 puppet-user[12837]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 27 20:55:23 node-2 puppet-user[12837]: (/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
Jul 27 20:55:23 node-2 puppet-user[12837]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 27 20:55:23 node-2 puppet-user[12837]: (/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
Jul 27 20:55:23 node-2 puppet-user[12837]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 27 20:55:23 node-2 puppet-user[12837]: (/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
Jul 27 20:55:23 node-2 puppet-user[12837]: (/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
Jul 27 20:55:23 node-2 puppet-user[12837]: (/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
Jul 27 20:55:23 node-2 puppet-user[12837]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 27 20:55:23 node-2 puppet-user[12837]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.419223 #10350] DEBUG -- : Trying to find block devices
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.419295 #10350] DEBUG -- : Found block device: sda
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.419337 #10350] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.419385 #10350] DEBUG -- : Trying to get list of physical devices
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.419560 #10350] DEBUG -- : Getting udev properties for device: sda
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.421694 #10350] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Jul 27 20:55:31 node-2 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"92693", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.421722 #10350] DEBUG -- : Trying to find out if device sda is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.421767 #10350] DEBUG -- : Device sda removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.421784 #10350] DEBUG -- : Device sda seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.422289 #10350] DEBUG -- : Getting udev properties for device: dm-0
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.423924 #10350] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-0Sm8o1domLBfLjNt2XkKal7xIQnwYeO1eLQbN8bu3sdZZ0mBvhhR2Oal16Y6LDnb /dev/disk/by-uuid/e5e58e42-f64e-488a-be69-d7741c41bf90 /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-0Sm8o1domLBfLjNt2XkKal7xIQnwYeO1eLQbN8bu3sdZZ0mBvhhR2Oal16Y6LDnb", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e5e58e42-f64e-488a-be69-d7741c41bf90", "ID_FS_UUID_ENC"=>"e5e58e42-f64e-488a-be69-d7741c41bf90", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6
Jul 27 20:55:31 node-2 nailgun-agent: 3364", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.423952 #10350] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.423982 #10350] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.423996 #10350] DEBUG -- : Device dm-0 seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.424011 #10350] DEBUG -- : Getting udev properties for device: dm-1
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.426091 #10350] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-aIzLBT4rfIDBjKtyy46bCtj5NzHD0EAyvjacq6GIilMKNurh1eTstBBgEu53P3BN /dev/disk/by-uuid/7f4929d6-e4e9-4721-ba21-888ddfe7a73b /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-aIzLBT4rfIDBjKtyy46bCtj5NzHD0EAyvjacq6GIilMKNurh1eTstBBgEu53P3BN", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"7f4929d6-e4e9-4721-ba21-888ddfe7a73b", "ID_FS_UUID_ENC"=>"7f4929d6-e4e9-4721-ba21-888ddfe7a73b", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88436", "nomdmonddf"=>"1", "nom
Jul 27 20:55:31 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.426118 #10350] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.426151 #10350] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.426166 #10350] DEBUG -- : Device dm-1 seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.426226 #10350] DEBUG -- : Getting udev properties for device: dm-2
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.428092 #10350] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-N39cRPJ35qTgZurkcRIjP3fkPmfjxzwEfN46xlQflzpwFem1YOLXMS4WReUDWRd0 /dev/disk/by-uuid/0339cbea-e66e-4c1e-8893-5d2ef8afef42 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-N39cRPJ35qTgZurkcRIjP3fkPmfjxzwEfN46xlQflzpwFem1YOLXMS4WReUDWRd0", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0339cbea-e66e-4c1e-8893-5d2ef8afef42", "ID_FS_UUID_ENC"=>"0339cbea-e66e-4c1e-8893-5d2ef8afef42", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7
Jul 27 20:55:31 node-2 nailgun-agent: 014", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.428120 #10350] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.428154 #10350] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.428206 #10350] DEBUG -- : Device dm-2 seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.428221 #10350] DEBUG -- : Getting udev properties for device: dm-3
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.429829 #10350] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-1FLHNCK7E8fsz7KgsysZ9iV4iwkmE6ZM7iDuxXaA5Ff2L0RX9AZmyOrtVaTxB88x /dev/disk/by-uuid/b2fb9c47-6596-4241-8fb9-3f763f4f3b5d /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-1FLHNCK7E8fsz7KgsysZ9iV4iwkmE6ZM7iDuxXaA5Ff2L0RX9AZmyOrtVaTxB88x", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b2fb9c47-6596-4241-8fb9-3f763f4f3b5d", "ID_FS_UUID_ENC"=>"b2fb9c47-6596-4241-8fb9-3f763f4f3b5d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17982", "nomdmon
Jul 27 20:55:31 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.429855 #10350] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.429895 #10350] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.429908 #10350] DEBUG -- : Device dm-3 seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.429923 #10350] DEBUG -- : Getting udev properties for device: dm-4
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.431735 #10350] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Szpqv7u2aYtrb4DtLZlYtg8qtNBXS7z4HNOKCSItfT63o1lKdVoF7LnTmkbuf9LX /dev/disk/by-uuid/55b158ad-21fc-4f30-bdea-0eb7b9ee6ffe /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-Szpqv7u2aYtrb4DtLZlYtg8qtNBXS7z4HNOKCSItfT63o1lKdVoF7LnTmkbuf9LX", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"55b158ad-21fc-4f30-bdea-0eb7b9ee6ffe", "ID_FS_UUID_ENC"=>"55b158ad-21fc-4f30-bdea-0eb7b9ee6ffe", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21232", "nomdmonddf"=>"1",
Jul 27 20:55:31 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.431773 #10350] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.431806 #10350] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.431843 #10350] DEBUG -- : Device dm-4 seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.431858 #10350] DEBUG -- : Getting udev properties for device: dm-5
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.433720 #10350] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-fLdROcSISgK23yi2MarRB8FIeHXMlR6Hp8902165sia6B3z7c0UJNFJ3xpH9JvVS /dev/disk/by-uuid/2feef717-9fda-4d7b-a349-a4e9eeea9420 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-fLdROcSISgK23yi2MarRB8FIeHXMlR6Hp8902165sia6B3z7c0UJNFJ3xpH9JvVS", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2feef717-9fda-4d7b-a349-a4e9eeea9420", "ID_FS_UUID_ENC"=>"2feef717-9fda-4d7b-a349-a4e9eeea9420", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23931", "nomdmonddf"=>"1", "nom
Jul 27 20:55:31 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.433750 #10350] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.433791 #10350] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.433805 #10350] DEBUG -- : Device dm-5 seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.433820 #10350] DEBUG -- : Getting udev properties for device: dm-6
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.435457 #10350] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-fLdROcSISgK23yi2MarRB8FIeHXMlR6H0BOtNct0s1OhUnnSpDIBMQHf0PsWjxNr /dev/disk/by-uuid/62251523-13bd-4dab-b46d-36c2c917116d /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-fLdROcSISgK23yi2MarRB8FIeHXMlR6H0BOtNct0s1OhUnnSpDIBMQHf0PsWjxNr", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"62251523-13bd-4dab-b46d-36c2c917116d", "ID_FS_UUID_ENC"=>"62251523-13bd-4dab-b46d-36c2c917116d", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24373", "nomdmonddf"=>"1", "nomdmonisw
Jul 27 20:55:31 node-2 nailgun-agent: "=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.435485 #10350] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.435531 #10350] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.435547 #10350] DEBUG -- : Device dm-6 seems to be appropriate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.435574 #10350] DEBUG -- : Getting udev properties for device: ram0
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.437147 #10350] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95202", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.437191 #10350] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.437235 #10350] DEBUG -- : Device ram0 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.437256 #10350] DEBUG -- : Getting udev properties for device: ram1
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.438817 #10350] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95672", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.438845 #10350] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.438880 #10350] DEBUG -- : Device ram1 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.438900 #10350] DEBUG -- : Getting udev properties for device: ram2
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.440417 #10350] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98645", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.440442 #10350] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.440476 #10350] DEBUG -- : Device ram2 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.440496 #10350] DEBUG -- : Getting udev properties for device: ram3
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.442007 #10350] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99241", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.442029 #10350] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.442064 #10350] DEBUG -- : Device ram3 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.442081 #10350] DEBUG -- : Getting udev properties for device: ram4
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.443723 #10350] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99598", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.443763 #10350] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.443801 #10350] DEBUG -- : Device ram4 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.443841 #10350] DEBUG -- : Getting udev properties for device: ram5
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.445333 #10350] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99846", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.445358 #10350] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.445391 #10350] DEBUG -- : Device ram5 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.445410 #10350] DEBUG -- : Getting udev properties for device: ram6
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.446841 #10350] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"998", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.446866 #10350] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.446899 #10350] DEBUG -- : Device ram6 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.446951 #10350] DEBUG -- : Getting udev properties for device: ram7
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.448343 #10350] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1079", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.448369 #10350] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.448411 #10350] DEBUG -- : Device ram7 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.448431 #10350] DEBUG -- : Getting udev properties for device: ram8
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.449880 #10350] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1134", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.449906 #10350] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.449959 #10350] DEBUG -- : Device ram8 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.449978 #10350] DEBUG -- : Getting udev properties for device: ram9
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.451364 #10350] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1182", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.451399 #10350] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.451433 #10350] DEBUG -- : Device ram9 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.451463 #10350] DEBUG -- : Getting udev properties for device: loop0
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.452867 #10350] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93373", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.452904 #10350] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.452954 #10350] DEBUG -- : Device loop0 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.452973 #10350] DEBUG -- : Getting udev properties for device: loop1
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.454402 #10350] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93718", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.454444 #10350] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.454479 #10350] DEBUG -- : Device loop1 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.454498 #10350] DEBUG -- : Getting udev properties for device: loop2
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.458756 #10350] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93875", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.458782 #10350] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.458827 #10350] DEBUG -- : Device loop2 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.458847 #10350] DEBUG -- : Getting udev properties for device: loop3
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.460411 #10350] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94109", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.460437 #10350] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.460489 #10350] DEBUG -- : Device loop3 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.460508 #10350] DEBUG -- : Getting udev properties for device: loop4
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.462045 #10350] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94365", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.462072 #10350] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.462114 #10350] DEBUG -- : Device loop4 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.462146 #10350] DEBUG -- : Getting udev properties for device: loop5
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.463559 #10350] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94603", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.463604 #10350] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.463640 #10350] DEBUG -- : Device loop5 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.463659 #10350] DEBUG -- : Getting udev properties for device: loop6
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.465091 #10350] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94827", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.465123 #10350] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.465164 #10350] DEBUG -- : Device loop6 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.465195 #10350] DEBUG -- : Getting udev properties for device: loop7
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.471452 #10350] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95049", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.471481 #10350] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.471526 #10350] DEBUG -- : Device loop7 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.471546 #10350] DEBUG -- : Getting udev properties for device: ram10
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.473159 #10350] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96364", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.473184 #10350] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.473255 #10350] DEBUG -- : Device ram10 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.473274 #10350] DEBUG -- : Getting udev properties for device: ram11
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.475151 #10350] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96854", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.475177 #10350] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.475209 #10350] DEBUG -- : Device ram11 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.475259 #10350] DEBUG -- : Getting udev properties for device: ram12
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.476901 #10350] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97131", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.476929 #10350] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.476960 #10350] DEBUG -- : Device ram12 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.476980 #10350] DEBUG -- : Getting udev properties for device: ram13
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.478595 #10350] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97572", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.478620 #10350] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.478655 #10350] DEBUG -- : Device ram13 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.478673 #10350] DEBUG -- : Getting udev properties for device: ram14
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.480165 #10350] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97834", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.480191 #10350] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.480227 #10350] DEBUG -- : Device ram14 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.480245 #10350] DEBUG -- : Getting udev properties for device: ram15
Jul 27 20:55:31 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482109 #10350] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98214", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482134 #10350] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482178 #10350] DEBUG -- : Device ram15 removable parameter: "0"
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482212 #10350] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482227 #10350] DEBUG -- : Block device seems to be physical data storage: sda
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482276 #10350] DEBUG -- : Found block device: dm-0
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482291 #10350] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482304 #10350] DEBUG -- : Found block device: dm-1
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482314 #10350] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482368 #10350] DEBUG -- : Found block device: dm-2
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482379 #10350] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482387 #10350] DEBUG -- : Found block device: dm-3
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482399 #10350] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482408 #10350] DEBUG -- : Found block device: dm-4
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482418 #10350] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482427 #10350] DEBUG -- : Found block device: dm-5
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482436 #10350] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482445 #10350] DEBUG -- : Found block device: dm-6
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482455 #10350] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482510 #10350] DEBUG -- : Found block device: ram0
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482520 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482529 #10350] DEBUG -- : Found block device: ram1
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482539 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482547 #10350] DEBUG -- : Found block device: ram2
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482556 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482564 #10350] DEBUG -- : Found block device: ram3
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482574 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482631 #10350] DEBUG -- : Found block device: ram4
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482643 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482652 #10350] DEBUG -- : Found block device: ram5
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482662 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482670 #10350] DEBUG -- : Found block device: ram6
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482679 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482687 #10350] DEBUG -- : Found block device: ram7
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482697 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482706 #10350] DEBUG -- : Found block device: ram8
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482761 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482771 #10350] DEBUG -- : Found block device: ram9
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482780 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482789 #10350] DEBUG -- : Found block device: loop0
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482799 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482807 #10350] DEBUG -- : Found block device: loop1
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482817 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482825 #10350] DEBUG -- : Found block device: loop2
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482834 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482885 #10350] DEBUG -- : Found block device: loop3
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482895 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482904 #10350] DEBUG -- : Found block device: loop4
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482913 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482920 #10350] DEBUG -- : Found block device: loop5
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482930 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482938 #10350] DEBUG -- : Found block device: loop6
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482947 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.482955 #10350] DEBUG -- : Found block device: loop7
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483006 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483015 #10350] DEBUG -- : Found block device: ram10
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483024 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483032 #10350] DEBUG -- : Found block device: ram11
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483042 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483050 #10350] DEBUG -- : Found block device: ram12
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483059 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483067 #10350] DEBUG -- : Found block device: ram13
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483078 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483127 #10350] DEBUG -- : Found block device: ram14
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483137 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483146 #10350] DEBUG -- : Found block device: ram15
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483155 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.483182 #10350] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.572383 #10350] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 27 20:55:31 node-2 nailgun-agent: D, [2016-07-27T20:55:31.572446 #10350] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 27 20:55:31 node-2 kernel: [   89.922494] init: plymouth-upstart-bridge main process ended, respawning
Jul 27 20:55:31 node-2 puppet-agent[8951]: Could not run: SIGTERM
Jul 27 20:55:31 node-2 kernel: [   90.161720] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 27 20:55:31 node-2 ec2: 
Jul 27 20:55:31 node-2 ec2: #############################################################
Jul 27 20:55:31 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 27 20:55:31 node-2 ec2: 1024 1f:50:cd:13:d7:2b:0f:f7:32:03:d5:ea:12:96:32:aa  root@node-2.domain.tld (DSA)
Jul 27 20:55:31 node-2 ec2: 256 72:ef:dd:14:ff:f6:32:52:51:98:82:a3:d5:48:cb:b8  root@node-2.domain.tld (ECDSA)
Jul 27 20:55:31 node-2 ec2: 256 2b:c4:0f:27:ab:22:ce:1d:b0:ea:37:78:59:c8:8e:12  root@node-2.domain.tld (ED25519)
Jul 27 20:55:31 node-2 ec2: 2048 5b:9b:b6:fa:43:f4:45:8a:86:08:79:d2:7a:43:46:56  root@node-2.domain.tld (RSA)
Jul 27 20:55:31 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 27 20:55:31 node-2 ec2: #############################################################
Jul 27 20:55:41 node-2 puppet-user[12837]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 27 20:55:42 node-2 puppet-user[12837]: Finished catalog run in 19.20 seconds
Jul 27 20:55:43 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.737866 #10350] DEBUG -- : Trying to find block devices
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738107 #10350] DEBUG -- : Found block device: sda
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738178 #10350] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738226 #10350] DEBUG -- : Block device seems to be physical data storage: sda
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738314 #10350] DEBUG -- : Found block device: dm-0
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738366 #10350] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738398 #10350] DEBUG -- : Found block device: dm-1
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738426 #10350] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738453 #10350] DEBUG -- : Found block device: dm-2
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738480 #10350] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738504 #10350] DEBUG -- : Found block device: dm-3
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738597 #10350] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738624 #10350] DEBUG -- : Found block device: dm-4
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738652 #10350] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738676 #10350] DEBUG -- : Found block device: dm-5
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738703 #10350] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738727 #10350] DEBUG -- : Found block device: dm-6
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738753 #10350] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738776 #10350] DEBUG -- : Found block device: ram0
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738801 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738872 #10350] DEBUG -- : Found block device: ram1
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738899 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738923 #10350] DEBUG -- : Found block device: ram2
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738948 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738972 #10350] DEBUG -- : Found block device: ram3
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.738997 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739020 #10350] DEBUG -- : Found block device: ram4
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739045 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739068 #10350] DEBUG -- : Found block device: ram5
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739159 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739184 #10350] DEBUG -- : Found block device: ram6
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739210 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739233 #10350] DEBUG -- : Found block device: ram7
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739259 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739281 #10350] DEBUG -- : Found block device: ram8
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739306 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739329 #10350] DEBUG -- : Found block device: ram9
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739354 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739377 #10350] DEBUG -- : Found block device: loop0
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739467 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739493 #10350] DEBUG -- : Found block device: loop1
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739518 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739541 #10350] DEBUG -- : Found block device: loop2
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739567 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739590 #10350] DEBUG -- : Found block device: loop3
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739617 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739641 #10350] DEBUG -- : Found block device: loop4
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739665 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739688 #10350] DEBUG -- : Found block device: loop5
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739778 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739803 #10350] DEBUG -- : Found block device: loop6
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739829 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739854 #10350] DEBUG -- : Found block device: loop7
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739880 #10350] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739903 #10350] DEBUG -- : Found block device: ram10
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739928 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739953 #10350] DEBUG -- : Found block device: ram11
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.739978 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740046 #10350] DEBUG -- : Found block device: ram12
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740073 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740096 #10350] DEBUG -- : Found block device: ram13
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740122 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740144 #10350] DEBUG -- : Found block device: ram14
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740170 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740193 #10350] DEBUG -- : Found block device: ram15
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740218 #10350] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.740289 #10350] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 27 20:55:43 node-2 nailgun-agent: D, [2016-07-27T20:55:43.966199 #10350] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 27 20:55:43 node-2 nailgun-agent: I, [2016-07-27T20:55:43.966681 #10350]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 27 20:55:44 node-2 puppet-user[14274]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 27 20:55:44 node-2 puppet-user[14274]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Jul 27 20:55:49 node-2 puppet-user[14274]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 27 20:56:01 node-2 CRON[15939]: (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")
Jul 27 20:56:13 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 20:56:13 node-2 nailgun-agent: I, [2016-07-27T20:56:13.148695 #15943]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 20:56:21 node-2 puppet-user[14274]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 27 20:56:21 node-2 puppet-user[14274]: Finished catalog run in 37.57 seconds
Jul 27 20:56:23 node-2 puppet-user[17049]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 27 20:56:24 node-2 puppet-user[17049]: Compiled catalog for node-2.domain.tld in environment production in 0.53 seconds
Jul 27 20:56:24 node-2 puppet-user[17049]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 27 20:56:24 node-2 puppet-user[17049]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 27 20:56:24 node-2 puppet-user[17049]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 27 20:56:24 node-2 puppet-user[17049]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 27 20:56:24 node-2 puppet-user[17049]: Finished catalog run in 0.08 seconds
Jul 27 20:56:26 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 20:56:26 node-2 puppet-user[17504]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 27 20:56:26 node-2 nailgun-agent: I, [2016-07-27T20:56:26.196410 #15943]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 27 20:56:26 node-2 puppet-user[17504]: Compiled catalog for node-2.domain.tld in environment production in 0.83 seconds
Jul 27 20:56:27 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 27 20:56:27 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 27 20:56:27 node-2 crontab[18113]: (root) LIST (root)
Jul 27 20:56:27 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 27 20:56:27 node-2 crontab[18114]: (root) REPLACE (root)
Jul 27 20:56:29 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:31 node-2 puppet-user[17504]: (/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
Jul 27 20:56:32 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 27 20:56:32 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 27 20:56:32 node-2 puppet-user[17504]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 27 20:56:32 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8403" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 20:56:32 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 27 20:56:34 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:34 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:34 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:34 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:34 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:54 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:54 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:54 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:54 node-2 multipathd: uevent trigger error
<27>Jul 27 20:56:54 node-2 multipathd: uevent trigger error
<27>Jul 27 20:57:55 node-2 ntpdate[29284]: no servers can be used, exiting
<27>Jul 27 20:58:27 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:27 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:27 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:27 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:27 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:32 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:32 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:32 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:32 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:32 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:43 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:43 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:43 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:43 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:43 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:46 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:46 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:46 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:46 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:46 node-2 multipathd: uevent trigger error
<27>Jul 27 20:58:46 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:48 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:48 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:48 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:48 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:48 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:57 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:57 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:57 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:57 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:57 node-2 multipathd: uevent trigger error
<27>Jul 27 20:59:59 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 20:59:59 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 21:00:05 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 21:00:05 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 21:00:11 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 21:00:16 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 21:00:16 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 21:00:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:37 node-2 multipathd: uevent trigger error
<129>Jul 27 21:00:39 node-2 haproxy[17747]: 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>Jul 27 21:00:40 node-2 haproxy[17751]: 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>Jul 27 21:00:40 node-2 haproxy[17751]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:00:40 node-2 haproxy[17751]: proxy mysqld has no server available!
<27>Jul 27 21:00:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:46 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:46 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:46 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:46 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:46 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:46 node-2 multipathd: uevent trigger error
<129>Jul 27 21:00:48 node-2 haproxy[20435]: 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>Jul 27 21:00:48 node-2 haproxy[20435]: 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>Jul 27 21:00:49 node-2 haproxy[20441]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:00:49 node-2 haproxy[20441]: proxy mysqld has no server available!
<129>Jul 27 21:00:49 node-2 haproxy[20441]: 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>Jul 27 21:00:49 node-2 haproxy[20441]: 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>Jul 27 21:00:50 node-2 haproxy[20441]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:00:50 node-2 haproxy[20441]: proxy object-storage has no server available!
<27>Jul 27 21:00:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:51 node-2 multipathd: uevent trigger error
<129>Jul 27 21:00:53 node-2 haproxy[21828]: 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>Jul 27 21:00:54 node-2 haproxy[21838]: 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>Jul 27 21:00:54 node-2 haproxy[21838]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:00:54 node-2 haproxy[21838]: proxy neutron has no server available!
<129>Jul 27 21:00:54 node-2 haproxy[21838]: 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>Jul 27 21:00:54 node-2 haproxy[21838]: 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>Jul 27 21:00:55 node-2 haproxy[21838]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:00:55 node-2 haproxy[21838]: proxy mysqld has no server available!
<129>Jul 27 21:00:55 node-2 haproxy[21838]: 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>Jul 27 21:00:55 node-2 haproxy[21838]: 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>Jul 27 21:00:55 node-2 haproxy[21838]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:00:55 node-2 haproxy[21838]: proxy object-storage has no server available!
<27>Jul 27 21:00:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:00:57 node-2 multipathd: uevent trigger error
<129>Jul 27 21:00:59 node-2 haproxy[23319]: 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>Jul 27 21:00:59 node-2 haproxy[23319]: 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>Jul 27 21:01:00 node-2 haproxy[23323]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:00 node-2 haproxy[23323]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:00 node-2 haproxy[23323]: 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>Jul 27 21:01:00 node-2 haproxy[23323]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 21:01:00 node-2 haproxy[23323]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:00 node-2 haproxy[23323]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:00 node-2 haproxy[23323]: 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>Jul 27 21:01:00 node-2 haproxy[23323]: 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>Jul 27 21:01:00 node-2 haproxy[23323]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:00 node-2 haproxy[23323]: proxy neutron has no server available!
<129>Jul 27 21:01:00 node-2 haproxy[23323]: 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>Jul 27 21:01:01 node-2 haproxy[23323]: 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>Jul 27 21:01:01 node-2 haproxy[23323]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:01 node-2 haproxy[23323]: proxy mysqld has no server available!
<129>Jul 27 21:01:01 node-2 haproxy[23323]: 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>Jul 27 21:01:01 node-2 haproxy[23323]: 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>Jul 27 21:01:01 node-2 haproxy[23323]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:01 node-2 haproxy[23323]: proxy object-storage has no server available!
<27>Jul 27 21:01:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:02 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:04 node-2 haproxy[24700]: 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>Jul 27 21:01:05 node-2 haproxy[24704]: 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>Jul 27 21:01:05 node-2 haproxy[24704]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:05 node-2 haproxy[24704]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:05 node-2 haproxy[24704]: 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>Jul 27 21:01:05 node-2 haproxy[24704]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 21:01:05 node-2 haproxy[24704]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:05 node-2 haproxy[24704]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:05 node-2 haproxy[24704]: 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>Jul 27 21:01:05 node-2 haproxy[24704]: 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>Jul 27 21:01:05 node-2 haproxy[24704]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:05 node-2 haproxy[24704]: proxy neutron has no server available!
<129>Jul 27 21:01:05 node-2 haproxy[24704]: 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>Jul 27 21:01:06 node-2 haproxy[24704]: 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>Jul 27 21:01:06 node-2 haproxy[24704]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:06 node-2 haproxy[24704]: proxy mysqld has no server available!
<129>Jul 27 21:01:06 node-2 haproxy[24704]: 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>Jul 27 21:01:06 node-2 haproxy[24704]: 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>Jul 27 21:01:06 node-2 haproxy[24704]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:06 node-2 haproxy[24704]: proxy object-storage has no server available!
<129>Jul 27 21:01:06 node-2 haproxy[24704]: 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>Jul 27 21:01:06 node-2 haproxy[24704]: 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>Jul 27 21:01:06 node-2 haproxy[24704]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:06 node-2 haproxy[24704]: proxy aodh has no server available!
<27>Jul 27 21:01:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:08 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:10 node-2 haproxy[26060]: 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>Jul 27 21:01:10 node-2 haproxy[26060]: 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>Jul 27 21:01:10 node-2 haproxy[26060]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:10 node-2 haproxy[26060]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:10 node-2 haproxy[26060]: 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>Jul 27 21:01:11 node-2 haproxy[26064]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 21:01:11 node-2 haproxy[26064]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:11 node-2 haproxy[26064]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:11 node-2 haproxy[26064]: 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>Jul 27 21:01:11 node-2 haproxy[26064]: 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>Jul 27 21:01:11 node-2 haproxy[26064]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:11 node-2 haproxy[26064]: proxy neutron has no server available!
<129>Jul 27 21:01:11 node-2 haproxy[26064]: 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>Jul 27 21:01:11 node-2 haproxy[26064]: 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>Jul 27 21:01:11 node-2 haproxy[26064]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:11 node-2 haproxy[26064]: proxy mysqld has no server available!
<129>Jul 27 21:01:11 node-2 haproxy[26064]: 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>Jul 27 21:01:11 node-2 haproxy[26064]: 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>Jul 27 21:01:12 node-2 haproxy[26064]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:12 node-2 haproxy[26064]: proxy object-storage has no server available!
<129>Jul 27 21:01:12 node-2 haproxy[26064]: 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>Jul 27 21:01:12 node-2 haproxy[26064]: 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>Jul 27 21:01:12 node-2 haproxy[26064]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:12 node-2 haproxy[26064]: proxy aodh has no server available!
<129>Jul 27 21:01:12 node-2 haproxy[26064]: 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>Jul 27 21:01:12 node-2 haproxy[26064]: 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>Jul 27 21:01:12 node-2 haproxy[26064]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:12 node-2 haproxy[26064]: proxy ceilometer has no server available!
<27>Jul 27 21:01:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:14 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:16 node-2 haproxy[27394]: 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>Jul 27 21:01:16 node-2 haproxy[27394]: 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>Jul 27 21:01:16 node-2 haproxy[27394]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:16 node-2 haproxy[27394]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:16 node-2 haproxy[27394]: 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>Jul 27 21:01:16 node-2 haproxy[27394]: 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>Jul 27 21:01:16 node-2 haproxy[27394]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:16 node-2 haproxy[27394]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:16 node-2 haproxy[27394]: 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>Jul 27 21:01:16 node-2 haproxy[27394]: 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>Jul 27 21:01:16 node-2 haproxy[27394]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:16 node-2 haproxy[27394]: proxy neutron has no server available!
<129>Jul 27 21:01:16 node-2 haproxy[27394]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:17 node-2 haproxy[27411]: proxy mysqld has no server available!
<129>Jul 27 21:01:17 node-2 haproxy[27411]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:17 node-2 haproxy[27411]: proxy object-storage has no server available!
<129>Jul 27 21:01:17 node-2 haproxy[27411]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:17 node-2 haproxy[27411]: proxy aodh has no server available!
<129>Jul 27 21:01:17 node-2 haproxy[27411]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: 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>Jul 27 21:01:17 node-2 haproxy[27411]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:17 node-2 haproxy[27411]: proxy ceilometer has no server available!
<27>Jul 27 21:01:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:19 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:21 node-2 haproxy[28755]: 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>Jul 27 21:01:21 node-2 haproxy[28755]: 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>Jul 27 21:01:21 node-2 haproxy[28755]: 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>Jul 27 21:01:21 node-2 haproxy[28755]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:21 node-2 haproxy[28755]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:21 node-2 haproxy[28755]: 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>Jul 27 21:01:21 node-2 haproxy[28755]: 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>Jul 27 21:01:21 node-2 haproxy[28755]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:21 node-2 haproxy[28755]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:22 node-2 haproxy[28764]: proxy neutron has no server available!
<129>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:22 node-2 haproxy[28764]: proxy mysqld has no server available!
<129>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:22 node-2 haproxy[28764]: proxy object-storage has no server available!
<129>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: 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>Jul 27 21:01:22 node-2 haproxy[28764]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:22 node-2 haproxy[28764]: proxy aodh has no server available!
<129>Jul 27 21:01:23 node-2 haproxy[28764]: 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>Jul 27 21:01:23 node-2 haproxy[28764]: 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>Jul 27 21:01:23 node-2 haproxy[28764]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:23 node-2 haproxy[28764]: proxy ceilometer has no server available!
<27>Jul 27 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:24 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:26 node-2 haproxy[30287]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:27 node-2 haproxy[30291]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:27 node-2 haproxy[30291]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:27 node-2 haproxy[30291]: proxy glance-api has no server available!
<129>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:27 node-2 haproxy[30291]: proxy glance-glare has no server available!
<129>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:27 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:28 node-2 haproxy[30291]: proxy neutron has no server available!
<129>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:28 node-2 haproxy[30291]: proxy glance-registry has no server available!
<129>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:28 node-2 haproxy[30291]: proxy mysqld has no server available!
<129>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:28 node-2 haproxy[30291]: proxy object-storage has no server available!
<129>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:28 node-2 haproxy[30291]: proxy aodh has no server available!
<129>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: 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>Jul 27 21:01:28 node-2 haproxy[30291]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:28 node-2 haproxy[30291]: proxy ceilometer has no server available!
<27>Jul 27 21:01:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:30 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:32 node-2 haproxy[31690]: 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>Jul 27 21:01:32 node-2 haproxy[31690]: 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>Jul 27 21:01:32 node-2 haproxy[31690]: 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>Jul 27 21:01:32 node-2 haproxy[31690]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:32 node-2 haproxy[31690]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:32 node-2 haproxy[31690]: 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>Jul 27 21:01:32 node-2 haproxy[31690]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:33 node-2 haproxy[31699]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:33 node-2 haproxy[31699]: proxy nova-api has no server available!
<129>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:33 node-2 haproxy[31699]: proxy nova-metadata-api has no server available!
<129>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:33 node-2 haproxy[31699]: proxy glance-api has no server available!
<129>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:33 node-2 haproxy[31699]: proxy glance-glare has no server available!
<129>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:33 node-2 haproxy[31699]: proxy neutron has no server available!
<129>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:33 node-2 haproxy[31699]: proxy glance-registry has no server available!
<129>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:33 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:34 node-2 haproxy[31699]: proxy mysqld has no server available!
<129>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:34 node-2 haproxy[31699]: proxy object-storage has no server available!
<129>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:34 node-2 haproxy[31699]: proxy aodh has no server available!
<129>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:34 node-2 haproxy[31699]: proxy ceilometer has no server available!
<129>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: 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>Jul 27 21:01:34 node-2 haproxy[31699]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:34 node-2 haproxy[31699]: proxy nova-novncproxy has no server available!
<27>Jul 27 21:01:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:35 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:37 node-2 haproxy[785]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:38 node-2 haproxy[789]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:38 node-2 haproxy[789]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:38 node-2 haproxy[789]: proxy nova-api has no server available!
<129>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:38 node-2 haproxy[789]: proxy nova-metadata-api has no server available!
<129>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:38 node-2 haproxy[789]: proxy cinder-api has no server available!
<129>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:38 node-2 haproxy[789]: proxy glance-api has no server available!
<129>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:38 node-2 haproxy[789]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:38 node-2 haproxy[789]: proxy glance-glare has no server available!
<129>Jul 27 21:01:38 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:39 node-2 haproxy[789]: proxy neutron has no server available!
<129>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:39 node-2 haproxy[789]: proxy glance-registry has no server available!
<129>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:39 node-2 haproxy[789]: proxy mysqld has no server available!
<129>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:39 node-2 haproxy[789]: proxy object-storage has no server available!
<129>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:39 node-2 haproxy[789]: proxy aodh has no server available!
<129>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:39 node-2 haproxy[789]: proxy ceilometer has no server available!
<129>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: 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>Jul 27 21:01:39 node-2 haproxy[789]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:39 node-2 haproxy[789]: proxy nova-novncproxy has no server available!
<27>Jul 27 21:01:40 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:41 node-2 multipathd: uevent trigger error
<129>Jul 27 21:01:43 node-2 haproxy[2201]: 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>Jul 27 21:01:43 node-2 haproxy[2201]: 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>Jul 27 21:01:43 node-2 haproxy[2201]: 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>Jul 27 21:01:43 node-2 haproxy[2201]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:43 node-2 haproxy[2201]: proxy keystone-1 has no server available!
<129>Jul 27 21:01:43 node-2 haproxy[2201]: 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>Jul 27 21:01:43 node-2 haproxy[2201]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy keystone-2 has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy nova-api has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy nova-metadata-api has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy cinder-api has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy glance-api has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy glance-glare has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy neutron has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy glance-registry has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:44 node-2 haproxy[2205]: proxy mysqld has no server available!
<129>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:44 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:45 node-2 haproxy[2205]: proxy object-storage has no server available!
<129>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:45 node-2 haproxy[2205]: proxy aodh has no server available!
<129>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:45 node-2 haproxy[2205]: proxy ceilometer has no server available!
<129>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:45 node-2 haproxy[2205]: proxy heat-api has no server available!
<129>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:45 node-2 haproxy[2205]: proxy heat-api-cfn has no server available!
<129>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:45 node-2 haproxy[2205]: proxy heat-api-cloudwatch has no server available!
<129>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: 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>Jul 27 21:01:45 node-2 haproxy[2205]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 21:01:45 node-2 haproxy[2205]: proxy nova-novncproxy has no server available!
<27>Jul 27 21:01:47 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:47 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:47 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:47 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:47 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:47 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:01:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:02:02 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 21:02:27 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>Jul 27 21:02:29 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 27 21:02:58 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:03:03 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 27 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 27 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 27 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 27 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:56 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:56 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:56 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:56 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:56 node-2 multipathd: uevent trigger error
<27>Jul 27 21:05:59 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 27 21:06:13 node-2 apache2_error [Wed Jul 27 21:06:11.543806 2016] [mpm_event:notice] [pid 14039:tid 139811807070080] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 21:06:13 node-2 apache2_error [Wed Jul 27 21:06:11.543910 2016] [core:notice] [pid 14039:tid 139811807070080] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:20 node-2 multipathd: uevent trigger error
<43>Jul 27 21:06:23 node-2 apache2_error [Wed Jul 27 21:06:14.604880 2016] [mpm_event:notice] [pid 14039:tid 139811807070080] AH00491: caught SIGTERM, shutting down
<43>Jul 27 21:06:23 node-2 apache2_error [Wed Jul 27 21:06:15.692436 2016] [mpm_worker:notice] [pid 14404:tid 140073970640768] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 21:06:23 node-2 apache2_error [Wed Jul 27 21:06:15.692498 2016] [core:notice] [pid 14404:tid 140073970640768] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 21:06:23 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:23 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:23 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:23 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:23 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:23 node-2 multipathd: uevent trigger error
<27>Jul 27 21:06:23 node-2 multipathd: uevent trigger error
<43>Jul 27 21:07:43 node-2 apache2_error [Wed Jul 27 21:07:37.657260 2016] [mpm_worker:notice] [pid 14404:tid 140073970640768] AH00295: caught SIGTERM, shutting down
<43>Jul 27 21:07:43 node-2 apache2_error [Wed Jul 27 21:07:38.430127 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 21:07:43 node-2 apache2_error [Wed Jul 27 21:07:38.430200 2016] [core:notice] [pid 29220:tid 139952926340992] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 21:08:33 node-2 apache2_error [Wed Jul 27 21:08:23.790223 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 21:08:33 node-2 apache2_error [Wed Jul 27 21:08:23.986613 2016] [mpm_worker:warn] [pid 29220:tid 139952926340992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 21:08:33 node-2 apache2_error [Wed Jul 27 21:08:23.989126 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 21:08:33 node-2 apache2_error [Wed Jul 27 21:08:23.989138 2016] [core:notice] [pid 29220:tid 139952926340992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 21:09:02 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:09:09 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:09 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:09 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:09 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:09 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:14 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:14 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:14 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:14 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:14 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 27 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 27 21:10:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:10:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:10:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:10:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:10:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:10:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:11:57 node-2 multipathd: uevent trigger error
<27>Jul 27 21:12:03 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:13:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:13:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:13:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:13:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:13:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:13 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:19 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:14:44 node-2 multipathd: uevent trigger error
<27>Jul 27 21:15:05 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:17:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:18:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:39 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 27 21:19:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 27 21:19:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 27 21:19:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 27 21:19:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 27 21:19:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:19:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:34 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:34 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:34 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:34 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:34 node-2 multipathd: uevent trigger error
<27>Jul 27 21:20:34 node-2 multipathd: uevent trigger error
<27>Jul 27 21:21:08 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:23:00 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:00 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:00 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:00 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:00 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:00 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:23:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:10 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:24:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:25 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:25 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:25 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:29 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:42 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:24:48 node-2 multipathd: uevent trigger error
<27>Jul 27 21:25:33 node-2 multipathd: uevent trigger error
<27>Jul 27 21:25:33 node-2 multipathd: uevent trigger error
<27>Jul 27 21:25:33 node-2 multipathd: uevent trigger error
<27>Jul 27 21:25:33 node-2 multipathd: uevent trigger error
<27>Jul 27 21:25:33 node-2 multipathd: uevent trigger error
<27>Jul 27 21:26:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:26:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:26:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:26:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:26:43 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:02 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 27 21:27:16 node-2 liberasurecode[31017]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:16 node-2 liberasurecode[31017]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:16 node-2 liberasurecode[31017]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:16 node-2 liberasurecode[31017]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:16 node-2 liberasurecode[31044]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:16 node-2 liberasurecode[31044]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:16 node-2 liberasurecode[31044]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:16 node-2 liberasurecode[31044]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:19 node-2 liberasurecode[31484]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:19 node-2 liberasurecode[31484]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:19 node-2 liberasurecode[31484]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:19 node-2 liberasurecode[31484]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32330]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32330]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32330]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32330]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32366]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32366]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32366]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32366]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32520]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:25 node-2 liberasurecode[32520]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32539]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32539]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32539]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32539]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32553]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32553]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32553]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32553]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32568]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32568]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32568]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:26 node-2 liberasurecode[32568]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:42 node-2 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:42 node-2 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:42 node-2 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:27:42 node-2 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 21:27:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:51 node-2 multipathd: uevent trigger error
<27>Jul 27 21:27:51 node-2 multipathd: uevent trigger error
<43>Jul 27 21:28:44 node-2 apache2_error [Wed Jul 27 21:28:41.227918 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 21:28:44 node-2 apache2_error [Wed Jul 27 21:28:41.613240 2016] [mpm_worker:warn] [pid 29220:tid 139952926340992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 21:28:44 node-2 apache2_error [Wed Jul 27 21:28:41.619202 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 21:28:44 node-2 apache2_error [Wed Jul 27 21:28:41.619232 2016] [core:notice] [pid 29220:tid 139952926340992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 21:29:22 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:22 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:22 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:22 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:22 node-2 multipathd: uevent trigger error
<43>Jul 27 21:29:25 node-2 apache2_error [Wed Jul 27 21:29:18.611806 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 21:29:25 node-2 apache2_error [Wed Jul 27 21:29:18.805587 2016] [mpm_worker:warn] [pid 29220:tid 139952926340992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 21:29:25 node-2 apache2_error [Wed Jul 27 21:29:18.813867 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 21:29:25 node-2 apache2_error [Wed Jul 27 21:29:18.813901 2016] [core:notice] [pid 29220:tid 139952926340992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 21:29:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:29:30 node-2 multipathd: uevent trigger error
<11>Jul 27 21:30:01 node-2 liberasurecode[24801]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:30:01 node-2 liberasurecode[24801]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:30:01 node-2 liberasurecode[24801]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:30:01 node-2 liberasurecode[24801]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Jul 27 21:30:05 node-2 apache2_error [Wed Jul 27 21:30:04.340187 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 21:30:05 node-2 apache2_error [Wed Jul 27 21:30:04.727009 2016] [mpm_worker:warn] [pid 29220:tid 139952926340992] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 21:30:05 node-2 apache2_error [Wed Jul 27 21:30:04.736285 2016] [mpm_worker:notice] [pid 29220:tid 139952926340992] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 21:30:05 node-2 apache2_error [Wed Jul 27 21:30:04.736316 2016] [core:notice] [pid 29220:tid 139952926340992] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 21:30:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 21:30:15 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:15 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:15 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:15 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:15 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:30:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:01 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:08 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:16 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 27 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:26 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:30 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:35 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:41 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:52 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 21:31:53 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:53 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:53 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:53 node-2 multipathd: uevent trigger error
<27>Jul 27 21:31:53 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:20 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:24 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:37 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:45 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:32:50 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:03 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:03 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:03 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:03 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:03 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:03 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:07 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:07 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:07 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:07 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:07 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:11 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:16 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:21 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:25 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:25 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:25 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:26 node-2 multipathd: uevent trigger error
<27>Jul 27 21:33:26 node-2 multipathd: uevent trigger error
<11>Jul 27 21:35:01 node-2 liberasurecode[30279]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:35:01 node-2 liberasurecode[30279]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:35:01 node-2 liberasurecode[30279]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 21:35:01 node-2 liberasurecode[30279]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
