Jul 25 14:21:30 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8415" x-info="http://www.rsyslog.com"] start
Jul 25 14:21:30 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 25 14:21:30 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 25 14:21:30 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 25 14:21:30 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 25 14:21:30 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 25 14:21:30 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 25 14:21:30 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 25 14:21:30 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=7f830f36-5ee4-49df-8419-c0facfc77428 nomdmonddf nomdmonisw
Jul 25 14:21:30 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 25 14:21:30 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 25 14:21:30 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 25 14:21:30 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 25 14:21:30 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 25 14:21:30 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 25 14:21:30 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 25 14:21:30 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 25 14:21:30 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 25 14:21:30 node-2 kernel: [    0.000000] No AGP bridge found
Jul 25 14:21:30 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 25 14:21:30 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 25 14:21:30 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 25 14:21:30 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 25 14:21:30 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 25 14:21:30 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 25 14:21:30 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 25 14:21:30 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 25 14:21:30 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 25 14:21:30 node-2 kernel: [    0.000000]   2 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000]   3 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000]   4 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000]   5 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000]   6 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000]   7 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000]   8 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000]   9 disabled
Jul 25 14:21:30 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 25 14:21:30 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 25 14:21:30 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 25 14:21:30 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 25 14:21:30 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 25 14:21:30 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 25 14:21:30 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 25 14:21:30 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 25 14:21:30 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 25 14:21:30 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 25 14:21:30 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 25 14:21:30 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 25 14:21:30 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 25 14:21:30 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 25 14:21:30 node-2 kernel: [    0.000000] Zone ranges:
Jul 25 14:21:30 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 25 14:21:30 node-2 kernel: [    0.000000] Early memory node ranges
Jul 25 14:21:30 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 25 14:21:30 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 25 14:21:30 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 25 14:21:30 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 25 14:21:30 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 25 14:21:30 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 25 14:21:30 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 25 14:21:30 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 25 14:21:30 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 25 14:21:30 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 25 14:21:30 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 25 14:21:30 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 25 14:21:30 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 25 14:21:30 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 25 14:21:30 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 25 14:21:30 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 25 14:21:30 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 25 14:21:30 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 25 14:21:30 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 25 14:21:30 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 25 14:21:30 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 25 14:21:30 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 25 14:21:30 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 25 14:21:30 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 25 14:21:30 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 25 14:21:30 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 25 14:21:30 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=7f830f36-5ee4-49df-8419-c0facfc77428 nomdmonddf nomdmonisw
Jul 25 14:21:30 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 25 14:21:30 node-2 kernel: [    0.000000] Checking aperture...
Jul 25 14:21:30 node-2 kernel: [    0.000000] No AGP bridge found
Jul 25 14:21:30 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 25 14:21:30 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 25 14:21:30 node-2 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 25 14:21:30 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 25 14:21:30 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 25 14:21:30 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 25 14:21:30 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 25 14:21:30 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 25 14:21:30 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 25 14:21:30 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 25 14:21:30 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 25 14:21:30 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 25 14:21:30 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 25 14:21:30 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 25 14:21:30 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 25 14:21:30 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 25 14:21:30 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 25 14:21:30 node-2 kernel: [    0.004000] tsc: Detected 3492.155 MHz processor
Jul 25 14:21:30 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.31 BogoMIPS (lpj=13968620)
Jul 25 14:21:30 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 25 14:21:30 node-2 kernel: [    0.000042] Security Framework initialized
Jul 25 14:21:30 node-2 kernel: [    0.000060] AppArmor: AppArmor initialized
Jul 25 14:21:30 node-2 kernel: [    0.000061] Yama: becoming mindful.
Jul 25 14:21:30 node-2 kernel: [    0.001449] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.006298] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.008227] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.008255] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.008543] Initializing cgroup subsys memory
Jul 25 14:21:30 node-2 kernel: [    0.008551] Initializing cgroup subsys devices
Jul 25 14:21:30 node-2 kernel: [    0.008553] Initializing cgroup subsys freezer
Jul 25 14:21:30 node-2 kernel: [    0.008555] Initializing cgroup subsys blkio
Jul 25 14:21:30 node-2 kernel: [    0.008556] Initializing cgroup subsys perf_event
Jul 25 14:21:30 node-2 kernel: [    0.008558] Initializing cgroup subsys hugetlb
Jul 25 14:21:30 node-2 kernel: [    0.008578] CPU: Physical Processor ID: 0
Jul 25 14:21:30 node-2 kernel: [    0.008579] CPU: Processor Core ID: 0
Jul 25 14:21:30 node-2 kernel: [    0.008583] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 25 14:21:30 node-2 kernel: [    0.008583] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 25 14:21:30 node-2 kernel: [    0.009276] mce: CPU supports 22 MCE banks
Jul 25 14:21:30 node-2 kernel: [    0.009304] CPU0: Thermal monitoring enabled (TM1)
Jul 25 14:21:30 node-2 kernel: [    0.009324] process: using mwait in idle threads
Jul 25 14:21:30 node-2 kernel: [    0.009328] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 25 14:21:30 node-2 kernel: [    0.009328] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 25 14:21:30 node-2 kernel: [    0.009328] tlb_flushall_shift: 6
Jul 25 14:21:30 node-2 kernel: [    0.009416] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 25 14:21:30 node-2 kernel: [    0.010141] ACPI: Core revision 20131115
Jul 25 14:21:30 node-2 kernel: [    0.022816] ACPI: All ACPI Tables successfully acquired
Jul 25 14:21:30 node-2 kernel: [    0.022975] ftrace: allocating 28617 entries in 112 pages
Jul 25 14:21:30 node-2 kernel: [    0.031848] dmar: Host address width 46
Jul 25 14:21:30 node-2 kernel: [    0.031850] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 25 14:21:30 node-2 kernel: [    0.031856] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 14:21:30 node-2 kernel: [    0.031857] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 25 14:21:30 node-2 kernel: [    0.031861] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 14:21:30 node-2 kernel: [    0.031863] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 25 14:21:30 node-2 kernel: [    0.031864] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 25 14:21:30 node-2 kernel: [    0.031865] dmar: ATSR flags: 0x0
Jul 25 14:21:30 node-2 kernel: [    0.031866] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 25 14:21:30 node-2 kernel: [    0.031868] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 25 14:21:30 node-2 kernel: [    0.031983] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 25 14:21:30 node-2 kernel: [    0.031984] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 14:21:30 node-2 kernel: [    0.031985] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 14:21:30 node-2 kernel: [    0.031986] HPET id 0 under DRHD base 0xc7ffc000
Jul 25 14:21:30 node-2 kernel: [    0.031987] Your BIOS is broken and requested that x2apic be disabled.
Jul 25 14:21:30 node-2 kernel: [    0.031987] This will slightly decrease performance.
Jul 25 14:21:30 node-2 kernel: [    0.031987] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 25 14:21:30 node-2 kernel: [    0.032420] Enabled IRQ remapping in xapic mode
Jul 25 14:21:30 node-2 kernel: [    0.032421] x2apic not enabled, IRQ remapping is in xapic mode
Jul 25 14:21:30 node-2 kernel: [    0.032425] Switched APIC routing to physical flat.
Jul 25 14:21:30 node-2 kernel: [    0.033059] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 25 14:21:30 node-2 kernel: [    0.072712] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 25 14:21:30 node-2 kernel: [    0.072718] TSC deadline timer enabled
Jul 25 14:21:30 node-2 kernel: [    0.072725] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 25 14:21:30 node-2 kernel: [    0.072731] ... version:                3
Jul 25 14:21:30 node-2 kernel: [    0.072732] ... bit width:              48
Jul 25 14:21:30 node-2 kernel: [    0.072733] ... generic registers:      4
Jul 25 14:21:30 node-2 kernel: [    0.072734] ... value mask:             0000ffffffffffff
Jul 25 14:21:30 node-2 kernel: [    0.072735] ... max period:             0000ffffffffffff
Jul 25 14:21:30 node-2 kernel: [    0.072736] ... fixed-purpose events:   3
Jul 25 14:21:30 node-2 kernel: [    0.072737] ... event mask:             000000070000000f
Jul 25 14:21:30 node-2 kernel: [    0.074172] x86: Booting SMP configuration:
Jul 25 14:21:30 node-2 kernel: [    0.088300] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 25 14:21:30 node-2 kernel: [    0.074174] .... node  #0, CPUs:        #1  #2  #3
Jul 25 14:21:30 node-2 kernel: [    0.116217] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 25 14:21:30 node-2 kernel: [    0.270384] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 25 14:21:30 node-2 kernel: [    0.326010] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 25 14:21:30 node-2 kernel: [    0.382876] x86: Booted up 2 nodes, 16 CPUs
Jul 25 14:21:30 node-2 kernel: [    0.382879] smpboot: Total of 16 processors activated (111760.92 BogoMIPS)
Jul 25 14:21:30 node-2 kernel: [    0.407010] devtmpfs: initialized
Jul 25 14:21:30 node-2 kernel: [    0.410103] EVM: security.selinux
Jul 25 14:21:30 node-2 kernel: [    0.410105] EVM: security.SMACK64
Jul 25 14:21:30 node-2 kernel: [    0.410106] EVM: security.ima
Jul 25 14:21:30 node-2 kernel: [    0.410107] EVM: security.capability
Jul 25 14:21:30 node-2 kernel: [    0.410156] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.410843] pinctrl core: initialized pinctrl subsystem
Jul 25 14:21:30 node-2 kernel: [    0.410903] regulator-dummy: no parameters
Jul 25 14:21:30 node-2 kernel: [    0.410935] RTC time: 14:20:51, date: 07/25/16
Jul 25 14:21:30 node-2 kernel: [    0.410970] NET: Registered protocol family 16
Jul 25 14:21:30 node-2 kernel: [    0.411055] cpuidle: using governor ladder
Jul 25 14:21:30 node-2 kernel: [    0.411056] cpuidle: using governor menu
Jul 25 14:21:30 node-2 kernel: [    0.411090] ACPI: bus type PCI registered
Jul 25 14:21:30 node-2 kernel: [    0.411092] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 25 14:21:30 node-2 kernel: [    0.411139] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 25 14:21:30 node-2 kernel: [    0.411141] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 25 14:21:30 node-2 kernel: [    0.424871] PCI: Using configuration type 1 for base access
Jul 25 14:21:30 node-2 kernel: [    0.425884] bio: create slab <bio-0> at 0
Jul 25 14:21:30 node-2 kernel: [    0.426166] ACPI: Added _OSI(Module Device)
Jul 25 14:21:30 node-2 kernel: [    0.426168] ACPI: Added _OSI(Processor Device)
Jul 25 14:21:30 node-2 kernel: [    0.426169] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 25 14:21:30 node-2 kernel: [    0.426170] ACPI: Added _OSI(Processor Aggregator Device)
Jul 25 14:21:30 node-2 kernel: [    0.438800] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 25 14:21:30 node-2 kernel: [    0.449254] ACPI: Interpreter enabled
Jul 25 14:21:30 node-2 kernel: [    0.449259] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 25 14:21:30 node-2 kernel: [    0.449263] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 25 14:21:30 node-2 kernel: [    0.449266] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 25 14:21:30 node-2 kernel: [    0.449272] ACPI: (supports S0 S4 S5)
Jul 25 14:21:30 node-2 kernel: [    0.449274] ACPI: Using IOAPIC for interrupt routing
Jul 25 14:21:30 node-2 kernel: [    0.449315] HEST: Table parsing has been initialized.
Jul 25 14:21:30 node-2 kernel: [    0.449318] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 25 14:21:30 node-2 kernel: [    0.449870] ACPI: No dock devices found.
Jul 25 14:21:30 node-2 kernel: [    0.461402] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 25 14:21:30 node-2 kernel: [    0.461407] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:30 node-2 kernel: [    0.461411] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 14:21:30 node-2 kernel: [    0.461441] PCI host bridge to bus 0000:ff
Jul 25 14:21:30 node-2 kernel: [    0.461444] pci_bus 0000:ff: root bus resource [bus ff]
Jul 25 14:21:30 node-2 kernel: [    0.461452] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461490] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.461521] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461556] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461585] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.461615] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.461646] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461675] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461706] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461734] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461760] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461787] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461814] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461840] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461867] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461894] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461922] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461949] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.461976] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.462004] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462030] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.462055] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462081] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462111] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.462146] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462177] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462206] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462237] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462268] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462299] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462329] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462359] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462390] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462427] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462458] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462490] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462524] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462555] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462582] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462615] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462650] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462688] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462721] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462754] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462782] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462811] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462840] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462869] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462900] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462930] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462961] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.462990] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463018] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463047] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463076] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463106] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463137] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463193] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 25 14:21:30 node-2 kernel: [    0.463196] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:30 node-2 kernel: [    0.463199] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 14:21:30 node-2 kernel: [    0.463216] PCI host bridge to bus 0000:7f
Jul 25 14:21:30 node-2 kernel: [    0.463218] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 25 14:21:30 node-2 kernel: [    0.463223] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463249] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.463277] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463308] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463330] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.463354] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.463379] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463404] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463427] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463449] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463471] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463493] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463517] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463539] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463562] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463594] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463617] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463642] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463667] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.463693] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463718] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.463742] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463767] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463795] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 14:21:30 node-2 kernel: [    0.463830] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463856] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463882] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463908] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463933] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463959] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.463985] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464012] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464037] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464066] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464094] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464124] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464152] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464176] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464200] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464229] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464254] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464280] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464308] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464336] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464362] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464387] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464413] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464442] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464469] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464496] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464526] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464550] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464572] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464598] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464624] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464654] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.464680] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.465936] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 25 14:21:30 node-2 kernel: [    0.465939] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:30 node-2 kernel: [    0.467066] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 14:21:30 node-2 kernel: [    0.467573] PCI host bridge to bus 0000:00
Jul 25 14:21:30 node-2 kernel: [    0.467575] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 25 14:21:30 node-2 kernel: [    0.467577] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 25 14:21:30 node-2 kernel: [    0.467581] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 25 14:21:30 node-2 kernel: [    0.467583] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 25 14:21:30 node-2 kernel: [    0.467584] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 25 14:21:30 node-2 kernel: [    0.467586] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 25 14:21:30 node-2 kernel: [    0.467587] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 25 14:21:30 node-2 kernel: [    0.467593] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 25 14:21:30 node-2 kernel: [    0.467677] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.467707] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.467749] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 25 14:21:30 node-2 kernel: [    0.467768] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.467797] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.467838] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 25 14:21:30 node-2 kernel: [    0.467857] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.467886] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.467929] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 25 14:21:30 node-2 kernel: [    0.467950] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 14:21:30 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 25 14:21:30 node-2 kernel: [    0.468020] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.468098] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.468176] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 14:21:30 node-2 kernel: [    0.468180] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 25 14:21:30 node-2 kernel: [    0.468265] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 25 14:21:30 node-2 kernel: [    0.468412] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 25 14:21:30 node-2 kernel: [    0.468429] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 25 14:21:30 node-2 kernel: [    0.468506] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.468560] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 25 14:21:30 node-2 kernel: [    0.468581] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.468636] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.468679] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 25 14:21:30 node-2 kernel: [    0.468705] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.468761] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.468804] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 25 14:21:30 node-2 kernel: [    0.468828] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 25 14:21:30 node-2 kernel: [    0.468845] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 25 14:21:30 node-2 kernel: [    0.468922] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.468972] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 25 14:21:30 node-2 kernel: [    0.468997] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 25 14:21:30 node-2 kernel: [    0.469244] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 25 14:21:30 node-2 kernel: [    0.469250] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 25 14:21:30 node-2 kernel: [    0.469256] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.469261] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.469269] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 25 14:21:30 node-2 kernel: [    0.469299] pci 0000:01:00.0: supports D1 D2
Jul 25 14:21:30 node-2 kernel: [    0.479595] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 14:21:30 node-2 kernel: [    0.479617] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 14:21:30 node-2 kernel: [    0.479618] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 14:21:30 node-2 kernel: [    0.479725] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.479759] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 25 14:21:30 node-2 kernel: [    0.487601] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 14:21:30 node-2 kernel: [    0.487603] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.487605] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:30 node-2 kernel: [    0.487660] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.487732] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.487808] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.487852] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 14:21:30 node-2 kernel: [    0.487856] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.487858] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:30 node-2 kernel: [    0.487909] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.488031] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.488084] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 14:21:30 node-2 kernel: [    0.488087] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.488089] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.488138] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.488259] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.488300] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.488419] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.488455] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.488593] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.488629] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:30 node-2 kernel: [    0.488751] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:30 node-2 kernel: [    0.488791] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 14:21:30 node-2 kernel: [    0.488794] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.488796] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.488855] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:30 node-2 kernel: [    0.488918] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.488970] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.489012] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 25 14:21:30 node-2 kernel: [    0.489093] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 25 14:21:30 node-2 kernel: [    0.489198] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 14:21:30 node-2 kernel: [    0.489201] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.489203] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.489259] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:30 node-2 kernel: [    0.489312] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.489361] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.489595] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 14:21:30 node-2 kernel: [    0.489599] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 14:21:30 node-2 kernel: [    0.489661] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:30 node-2 kernel: [    0.489720] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.489769] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.489977] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 14:21:30 node-2 kernel: [    0.489981] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 14:21:30 node-2 kernel: [    0.490039] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:30 node-2 kernel: [    0.490098] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.490151] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 25 14:21:30 node-2 kernel: [    0.490374] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 14:21:30 node-2 kernel: [    0.490377] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 14:21:30 node-2 kernel: [    0.490551] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 14:21:30 node-2 kernel: [    0.490589] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 14:21:30 node-2 kernel: [    0.490662] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 25 14:21:30 node-2 kernel: [    0.490681] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 25 14:21:30 node-2 kernel: [    0.490694] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 25 14:21:30 node-2 kernel: [    0.490707] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 25 14:21:30 node-2 kernel: [    0.490757] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 25 14:21:30 node-2 kernel: [    0.495615] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 14:21:30 node-2 kernel: [    0.495624] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 14:21:30 node-2 kernel: [    0.495676] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 25 14:21:30 node-2 kernel: [    0.496164] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 25 14:21:30 node-2 kernel: [    0.496167] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:30 node-2 kernel: [    0.496291] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 14:21:30 node-2 kernel: [    0.496399] PCI host bridge to bus 0000:80
Jul 25 14:21:30 node-2 kernel: [    0.496401] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 25 14:21:30 node-2 kernel: [    0.496402] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 25 14:21:30 node-2 kernel: [    0.496404] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 25 14:21:30 node-2 kernel: [    0.496412] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.496475] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.496542] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 14:21:30 node-2 kernel: [    0.496603] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 14:21:30 node-2 kernel: [    0.496608] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 25 14:21:30 node-2 kernel: [    0.496681] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 25 14:21:30 node-2 kernel: [    0.496980] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 25 14:21:30 node-2 kernel: [    0.497011] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 25 14:21:30 node-2 kernel: [    0.497041] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 25 14:21:30 node-2 kernel: [    0.497069] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 25 14:21:30 node-2 kernel: [    0.497099] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:30 node-2 kernel: [    0.497128] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:30 node-2 kernel: [    0.497158] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:30 node-2 kernel: [    0.497187] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:30 node-2 kernel: [    0.497271] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 25 14:21:30 node-2 kernel: [    0.497275] ACPI: \_SB_.UNC1: notify handler is installed
Jul 25 14:21:30 node-2 kernel: [    0.497277] ACPI: \_SB_.UNC0: notify handler is installed
Jul 25 14:21:30 node-2 kernel: [    0.497291] ACPI: \_SB_.PCI0: notify handler is installed
Jul 25 14:21:30 node-2 kernel: [    0.497345] ACPI: \_SB_.PCI1: notify handler is installed
Jul 25 14:21:30 node-2 kernel: [    0.497424] Found 4 acpi root devices
Jul 25 14:21:30 node-2 kernel: [    0.497541] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 25 14:21:30 node-2 kernel: [    0.497543] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 25 14:21:30 node-2 kernel: [    0.497544] vgaarb: loaded
Jul 25 14:21:30 node-2 kernel: [    0.497546] vgaarb: bridge control possible 0000:0c:00.0
Jul 25 14:21:30 node-2 kernel: [    0.497657] SCSI subsystem initialized
Jul 25 14:21:30 node-2 kernel: [    0.497720] libata version 3.00 loaded.
Jul 25 14:21:30 node-2 kernel: [    0.497735] ACPI: bus type USB registered
Jul 25 14:21:30 node-2 kernel: [    0.497745] usbcore: registered new interface driver usbfs
Jul 25 14:21:30 node-2 kernel: [    0.497750] usbcore: registered new interface driver hub
Jul 25 14:21:30 node-2 kernel: [    0.497770] usbcore: registered new device driver usb
Jul 25 14:21:30 node-2 kernel: [    0.497932] PCI: Using ACPI for IRQ routing
Jul 25 14:21:30 node-2 kernel: [    0.501536] PCI: pci_cache_line_size set to 64 bytes
Jul 25 14:21:30 node-2 kernel: [    0.501747] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 25 14:21:30 node-2 kernel: [    0.501748] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 25 14:21:30 node-2 kernel: [    0.501749] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 25 14:21:30 node-2 kernel: [    0.501813] NetLabel: Initializing
Jul 25 14:21:30 node-2 kernel: [    0.501814] NetLabel:  domain hash size = 128
Jul 25 14:21:30 node-2 kernel: [    0.501815] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 25 14:21:30 node-2 kernel: [    0.501824] NetLabel:  unlabeled traffic allowed by default
Jul 25 14:21:30 node-2 kernel: [    0.501879] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 25 14:21:30 node-2 kernel: [    0.501884] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 25 14:21:30 node-2 kernel: [    0.503951] Switched to clocksource hpet
Jul 25 14:21:30 node-2 kernel: [    0.507789] AppArmor: AppArmor Filesystem Enabled
Jul 25 14:21:30 node-2 kernel: [    0.507803] pnp: PnP ACPI init
Jul 25 14:21:30 node-2 kernel: [    0.507810] ACPI: bus type PNP registered
Jul 25 14:21:30 node-2 kernel: [    0.507928] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 25 14:21:30 node-2 kernel: [    0.507936] pnp 00:01: [dma 4]
Jul 25 14:21:30 node-2 kernel: [    0.507953] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 25 14:21:30 node-2 kernel: [    0.507980] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 25 14:21:30 node-2 kernel: [    0.507999] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 25 14:21:30 node-2 kernel: [    0.508016] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 25 14:21:30 node-2 kernel: [    0.508049] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 25 14:21:30 node-2 kernel: [    0.508100] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508103] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 25 14:21:30 node-2 kernel: [    0.508104] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508106] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508107] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508112] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508114] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 25 14:21:30 node-2 kernel: [    0.508115] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508117] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508118] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508120] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508121] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508123] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 25 14:21:30 node-2 kernel: [    0.508125] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 25 14:21:30 node-2 kernel: [    0.508208] pnp 00:07: [dma 0 disabled]
Jul 25 14:21:30 node-2 kernel: [    0.508237] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 14:21:30 node-2 kernel: [    0.508311] pnp 00:08: [dma 0 disabled]
Jul 25 14:21:30 node-2 kernel: [    0.508343] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 14:21:30 node-2 kernel: [    0.508394] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 25 14:21:30 node-2 kernel: [    0.508742] pnp: PnP ACPI: found 10 devices
Jul 25 14:21:30 node-2 kernel: [    0.508744] ACPI: bus type PNP unregistered
Jul 25 14:21:30 node-2 kernel: [    0.515048] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 14:21:30 node-2 kernel: [    0.515051] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 14:21:30 node-2 kernel: [    0.515054] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 14:21:30 node-2 kernel: [    0.515058] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 14:21:30 node-2 kernel: [    0.515060] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515075] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515104] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 14:21:30 node-2 kernel: [    0.515118] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515147] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 14:21:30 node-2 kernel: [    0.515162] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 14:21:30 node-2 kernel: [    0.515190] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 14:21:30 node-2 kernel: [    0.515205] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 14:21:30 node-2 kernel: [    0.515234] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 14:21:30 node-2 kernel: [    0.515236] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515253] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515282] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 14:21:30 node-2 kernel: [    0.515284] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515298] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515327] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 14:21:30 node-2 kernel: [    0.515329] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515331] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515335] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 14:21:30 node-2 kernel: [    0.515337] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515340] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515343] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 14:21:30 node-2 kernel: [    0.515348] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 14:21:30 node-2 kernel: [    0.515356] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 14:21:30 node-2 kernel: [    0.515360] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 14:21:30 node-2 kernel: [    0.515366] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 25 14:21:30 node-2 kernel: [    0.515367] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 25 14:21:30 node-2 kernel: [    0.515368] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 25 14:21:30 node-2 kernel: [    0.515369] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 25 14:21:30 node-2 kernel: [    0.515369] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 25 14:21:30 node-2 kernel: [    0.515370] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 25 14:21:30 node-2 kernel: [    0.515371] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 25 14:21:30 node-2 kernel: [    0.515372] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 25 14:21:30 node-2 kernel: [    0.515373] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515374] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515375] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515376] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515376] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515377] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515378] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515379] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515380] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:30 node-2 kernel: [    0.515381] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515382] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 25 14:21:30 node-2 kernel: [    0.515383] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 25 14:21:30 node-2 kernel: [    0.515384] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 25 14:21:30 node-2 kernel: [    0.515385] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 25 14:21:30 node-2 kernel: [    0.515387] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 25 14:21:30 node-2 kernel: [    0.515388] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 25 14:21:30 node-2 kernel: [    0.515428] NET: Registered protocol family 2
Jul 25 14:21:30 node-2 kernel: [    0.515681] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.516023] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.516171] TCP: Hash tables configured (established 262144 bind 65536)
Jul 25 14:21:30 node-2 kernel: [    0.516214] TCP: reno registered
Jul 25 14:21:30 node-2 kernel: [    0.516244] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.516338] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.516485] NET: Registered protocol family 1
Jul 25 14:21:30 node-2 kernel: [    0.552049] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 25 14:21:30 node-2 kernel: [    0.552063] PCI: CLS 64 bytes, default 64
Jul 25 14:21:30 node-2 kernel: [    0.552138] Trying to unpack rootfs image as initramfs...
Jul 25 14:21:30 node-2 kernel: [    0.771394] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 25 14:21:30 node-2 kernel: [    0.771438] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 25 14:21:30 node-2 kernel: [    0.771442] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 25 14:21:30 node-2 kernel: [    0.771878] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771885] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771890] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771895] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771920] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771931] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771940] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771949] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771957] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771966] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771972] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771978] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771985] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.771993] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.772000] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.772008] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:30 node-2 kernel: [    0.772087] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 25 14:21:30 node-2 kernel: [    0.772090] Scanning for low memory corruption every 60 seconds
Jul 25 14:21:30 node-2 kernel: [    0.772467] Initialise system trusted keyring
Jul 25 14:21:30 node-2 kernel: [    0.772521] audit: initializing netlink socket (disabled)
Jul 25 14:21:30 node-2 kernel: [    0.772537] type=2000 audit(1469456451.728:1): initialized
Jul 25 14:21:30 node-2 kernel: [    0.790422] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 25 14:21:30 node-2 kernel: [    0.791936] zbud: loaded
Jul 25 14:21:30 node-2 kernel: [    0.792063] VFS: Disk quotas dquot_6.5.2
Jul 25 14:21:30 node-2 kernel: [    0.792097] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 25 14:21:30 node-2 kernel: [    0.792484] fuse init (API version 7.22)
Jul 25 14:21:30 node-2 kernel: [    0.792549] msgmni has been set to 32768
Jul 25 14:21:30 node-2 kernel: [    0.792599] Key type big_key registered
Jul 25 14:21:30 node-2 kernel: [    0.793127] Key type asymmetric registered
Jul 25 14:21:30 node-2 kernel: [    0.793128] Asymmetric key parser 'x509' registered
Jul 25 14:21:30 node-2 kernel: [    0.793151] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 25 14:21:30 node-2 kernel: [    0.793222] io scheduler noop registered
Jul 25 14:21:30 node-2 kernel: [    0.793224] io scheduler deadline registered (default)
Jul 25 14:21:30 node-2 kernel: [    0.793245] io scheduler cfq registered
Jul 25 14:21:30 node-2 kernel: [    0.793790] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    0.793941] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    0.794060] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    0.794171] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    0.794285] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    0.794423] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    0.794782] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 25 14:21:30 node-2 kernel: [    0.794807] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 25 14:21:30 node-2 kernel: [    0.794823] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 25 14:21:30 node-2 kernel: [    0.794833] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794835] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794838] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:30 node-2 kernel: [    0.794843] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794844] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794845] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794847] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794848] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794850] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794851] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794853] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794854] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794856] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794857] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794858] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794860] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:30 node-2 kernel: [    0.794866] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794868] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:30 node-2 kernel: [    0.794880] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794883] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:30 node-2 kernel: [    0.794893] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794895] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:30 node-2 kernel: [    0.794898] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 25 14:21:30 node-2 kernel: [    0.794955] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 25 14:21:30 node-2 kernel: [    0.794961] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 25 14:21:30 node-2 kernel: [    0.794965] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 25 14:21:30 node-2 kernel: [    0.794974] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 25 14:21:30 node-2 kernel: [    0.795014] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 25 14:21:30 node-2 kernel: [    0.795016] vesafb: scrolling: redraw
Jul 25 14:21:30 node-2 kernel: [    0.795017] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 25 14:21:30 node-2 kernel: [    0.815643] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 25 14:21:30 node-2 kernel: [    0.824194] Console: switching to colour frame buffer device 80x30
Jul 25 14:21:30 node-2 kernel: [    0.832856] fb0: VESA VGA frame buffer device
Jul 25 14:21:30 node-2 kernel: [    0.833053] intel_idle: MWAIT substates: 0x2120
Jul 25 14:21:30 node-2 kernel: [    0.833054] intel_idle: v0.4 model 0x3F
Jul 25 14:21:30 node-2 kernel: [    0.833055] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 25 14:21:30 node-2 kernel: [    0.833287] ipmi message handler version 39.2
Jul 25 14:21:30 node-2 kernel: [    0.833565] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 25 14:21:30 node-2 kernel: [    0.834002] ACPI: AC Adapter [P111] (on-line)
Jul 25 14:21:30 node-2 kernel: [    0.839239] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 25 14:21:30 node-2 kernel: [    0.850289] ACPI: Power Button [PWRB]
Jul 25 14:21:30 node-2 kernel: [    0.856081] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 25 14:21:30 node-2 kernel: [    0.867747] ACPI: Power Button [PWRF]
Jul 25 14:21:30 node-2 kernel: [    0.885426] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 25 14:21:30 node-2 kernel: [    0.897131] pstore: Registered erst as persistent store backend
Jul 25 14:21:30 node-2 kernel: [    0.903349] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 25 14:21:30 node-2 kernel: [    0.915354] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 25 14:21:30 node-2 kernel: [    0.942121] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 25 14:21:30 node-2 kernel: [    0.975418] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 25 14:21:30 node-2 kernel: [    0.989500] Linux agpgart interface v0.103
Jul 25 14:21:30 node-2 kernel: [    0.997182] brd: module loaded
Jul 25 14:21:30 node-2 kernel: [    1.004302] loop: module loaded
Jul 25 14:21:30 node-2 kernel: [    1.011118] libphy: Fixed MDIO Bus: probed
Jul 25 14:21:30 node-2 kernel: [    1.017701] tun: Universal TUN/TAP device driver, 1.6
Jul 25 14:21:30 node-2 kernel: [    1.024271] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 25 14:21:30 node-2 kernel: [    1.030835] PPP generic driver version 2.4.2
Jul 25 14:21:30 node-2 kernel: [    1.037214] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 25 14:21:30 node-2 kernel: [    1.043652] ehci-pci: EHCI PCI platform driver
Jul 25 14:21:30 node-2 kernel: [    1.050164] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 25 14:21:30 node-2 kernel: [    1.056579] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 25 14:21:30 node-2 kernel: [    1.069108] ehci-pci 0000:00:1a.0: debug port 2
Jul 25 14:21:30 node-2 kernel: [    1.079286] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 25 14:21:30 node-2 kernel: [    1.079304] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 25 14:21:30 node-2 kernel: [    1.095453] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 25 14:21:30 node-2 kernel: [    1.101611] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 14:21:30 node-2 kernel: [    1.107875] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 14:21:30 node-2 kernel: [    1.119791] usb usb1: Product: EHCI Host Controller
Jul 25 14:21:30 node-2 kernel: [    1.125818] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 14:21:30 node-2 kernel: [    1.131869] usb usb1: SerialNumber: 0000:00:1a.0
Jul 25 14:21:30 node-2 kernel: [    1.137829] hub 1-0:1.0: USB hub found
Jul 25 14:21:30 node-2 kernel: [    1.143602] hub 1-0:1.0: 2 ports detected
Jul 25 14:21:30 node-2 kernel: [    1.149395] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 25 14:21:30 node-2 kernel: [    1.155007] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 25 14:21:30 node-2 kernel: [    1.165957] ehci-pci 0000:00:1d.0: debug port 2
Jul 25 14:21:30 node-2 kernel: [    1.175270] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 25 14:21:30 node-2 kernel: [    1.175273] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 25 14:21:30 node-2 kernel: [    1.191372] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 25 14:21:30 node-2 kernel: [    1.196595] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 14:21:30 node-2 kernel: [    1.201899] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 14:21:30 node-2 kernel: [    1.212474] usb usb2: Product: EHCI Host Controller
Jul 25 14:21:30 node-2 kernel: [    1.217957] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 14:21:30 node-2 kernel: [    1.223504] usb usb2: SerialNumber: 0000:00:1d.0
Jul 25 14:21:30 node-2 kernel: [    1.229022] hub 2-0:1.0: USB hub found
Jul 25 14:21:30 node-2 kernel: [    1.234380] hub 2-0:1.0: 2 ports detected
Jul 25 14:21:30 node-2 kernel: [    1.239680] ehci-platform: EHCI generic platform driver
Jul 25 14:21:30 node-2 kernel: [    1.244902] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 25 14:21:30 node-2 kernel: [    1.250202] ohci-pci: OHCI PCI platform driver
Jul 25 14:21:30 node-2 kernel: [    1.255490] ohci-platform: OHCI generic platform driver
Jul 25 14:21:30 node-2 kernel: [    1.260666] uhci_hcd: USB Universal Host Controller Interface driver
Jul 25 14:21:30 node-2 kernel: [    1.266003] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 25 14:21:30 node-2 kernel: [    1.459152] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 25 14:21:30 node-2 kernel: [    1.766931] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 25 14:21:30 node-2 kernel: [    1.783192] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 25 14:21:30 node-2 kernel: [    1.788785] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 14:21:30 node-2 kernel: [    1.794459] hub 1-1:1.0: USB hub found
Jul 25 14:21:30 node-2 kernel: [    1.800053] hub 1-1:1.0: 6 ports detected
Jul 25 14:21:30 node-2 kernel: [    1.914784] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 25 14:21:30 node-2 kernel: [    2.304673] i8042: No controller found
Jul 25 14:21:30 node-2 kernel: [    2.310196] mousedev: PS/2 mouse device common for all mice
Jul 25 14:21:30 node-2 kernel: [    2.315908] rtc_cmos 00:02: RTC can wake from S4
Jul 25 14:21:30 node-2 kernel: [    2.319309] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 25 14:21:30 node-2 kernel: [    2.319310] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 14:21:30 node-2 kernel: [    2.320068] hub 2-1:1.0: USB hub found
Jul 25 14:21:30 node-2 kernel: [    2.320305] hub 2-1:1.0: 8 ports detected
Jul 25 14:21:30 node-2 kernel: [    2.344204] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 25 14:21:30 node-2 kernel: [    2.349966] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 25 14:21:30 node-2 kernel: [    2.361283] device-mapper: uevent: version 1.0.3
Jul 25 14:21:30 node-2 kernel: [    2.367009] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 25 14:21:30 node-2 kernel: [    2.378388] ledtrig-cpu: registered to indicate activity on CPUs
Jul 25 14:21:30 node-2 kernel: [    2.384376] TCP: cubic registered
Jul 25 14:21:30 node-2 kernel: [    2.390251] NET: Registered protocol family 10
Jul 25 14:21:30 node-2 kernel: [    2.396312] NET: Registered protocol family 17
Jul 25 14:21:30 node-2 kernel: [    2.402091] Key type dns_resolver registered
Jul 25 14:21:30 node-2 kernel: [    2.408188] Loading compiled-in X.509 certificates
Jul 25 14:21:30 node-2 kernel: [    2.414412] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 25 14:21:30 node-2 kernel: [    2.426073] registered taskstats version 1
Jul 25 14:21:30 node-2 kernel: [    2.434123] Key type trusted registered
Jul 25 14:21:30 node-2 kernel: [    2.441738] Key type encrypted registered
Jul 25 14:21:30 node-2 kernel: [    2.447244] AppArmor: AppArmor sha1 policy hashing enabled
Jul 25 14:21:30 node-2 kernel: [    2.452761] IMA: No TPM chip found, activating TPM-bypass!
Jul 25 14:21:30 node-2 kernel: [    2.458866] regulator-dummy: disabling
Jul 25 14:21:30 node-2 kernel: [    2.464351]   Magic number: 8:640:334
Jul 25 14:21:30 node-2 kernel: [    2.469840] tty tty55: hash matches
Jul 25 14:21:30 node-2 kernel: [    2.475366] memory memory184: hash matches
Jul 25 14:21:30 node-2 kernel: [    2.480746] rtc_cmos 00:02: setting system clock to 2016-07-25 14:20:54 UTC (1469456454)
Jul 25 14:21:30 node-2 kernel: [    2.492995] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 25 14:21:30 node-2 kernel: [    2.498505] EDD information not available.
Jul 25 14:21:30 node-2 kernel: [    2.503993] PM: Hibernation image not present or could not be loaded.
Jul 25 14:21:30 node-2 kernel: [    2.504867] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 25 14:21:30 node-2 kernel: [    2.516037] Write protecting the kernel read-only data: 12288k
Jul 25 14:21:30 node-2 kernel: [    2.522292] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 25 14:21:30 node-2 kernel: [    2.534901] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 25 14:21:30 node-2 kernel: [    2.566960] device-mapper: multipath: version 1.6.0 loaded
Jul 25 14:21:30 node-2 kernel: [    2.574807] systemd-udevd[216]: starting version 204
Jul 25 14:21:30 node-2 kernel: [    2.597172] md: linear personality registered for level -1
Jul 25 14:21:30 node-2 kernel: [    2.598592] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 25 14:21:30 node-2 kernel: [    2.617662] md: multipath personality registered for level -4
Jul 25 14:21:30 node-2 kernel: [    2.625777] md: raid0 personality registered for level 0
Jul 25 14:21:30 node-2 kernel: [    2.634300] md: raid1 personality registered for level 1
Jul 25 14:21:30 node-2 kernel: [    2.640381] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 25 14:21:30 node-2 kernel: [    2.646700] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 25 14:21:30 node-2 kernel: [    2.646697] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 25 14:21:30 node-2 kernel: [    2.665845] megasas: FW now in Ready state
Jul 25 14:21:30 node-2 kernel: [    2.672169] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672176] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672182] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672187] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672192] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672201] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672206] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672212] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672217] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672222] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672227] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672233] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672238] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672243] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672250] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672256] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.672300] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 25 14:21:30 node-2 kernel: [    2.693313] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 25 14:21:30 node-2 kernel: [    2.706584] 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 25 14:21:30 node-2 kernel: [    2.720241] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:30 node-2 kernel: [    2.727181] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.727187] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.727193] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.727199] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.727240] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:30 node-2 kernel: [    2.730249] raid6: sse2x1    2113 MB/s
Jul 25 14:21:30 node-2 kernel: [    2.755189] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 25 14:21:30 node-2 kernel: [    2.768214] 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 25 14:21:30 node-2 kernel: [    2.781405] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:30 node-2 kernel: [    2.798016] raid6: sse2x2    3911 MB/s
Jul 25 14:21:30 node-2 kernel: [    2.869957] raid6: sse2x4   10135 MB/s
Jul 25 14:21:30 node-2 kernel: [    2.941904] raid6: avx2x1   14952 MB/s
Jul 25 14:21:30 node-2 kernel: [    3.013840] raid6: avx2x2   18870 MB/s
Jul 25 14:21:30 node-2 kernel: [    3.085773] raid6: avx2x4   21112 MB/s
Jul 25 14:21:30 node-2 kernel: [    3.091700] raid6: using algorithm avx2x4 (21112 MB/s)
Jul 25 14:21:30 node-2 kernel: [    3.097556] raid6: using avx2x2 recovery algorithm
Jul 25 14:21:30 node-2 kernel: [    3.103286] megasas:IOC Init cmd success
Jul 25 14:21:30 node-2 kernel: [    3.103288] Switched to clocksource tsc
Jul 25 14:21:30 node-2 kernel: [    3.103447] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.103453] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.103484] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.103519] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.103624] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.117479] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 25 14:21:30 node-2 kernel: [    3.117480] 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 25 14:21:30 node-2 kernel: [    3.117481] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:30 node-2 kernel: [    3.117543] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.117581] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.117614] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.117652] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.117734] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.127107] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 25 14:21:30 node-2 kernel: [    3.127109] 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 25 14:21:30 node-2 kernel: [    3.127109] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:30 node-2 kernel: [    3.127170] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.127203] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.127240] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.127276] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.127361] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:30 node-2 kernel: [    3.129739] megasas: INIT adapter done
Jul 25 14:21:30 node-2 kernel: [    3.130574] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 25 14:21:30 node-2 kernel: [    3.130575] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 25 14:21:30 node-2 kernel: [    3.130575] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 25 14:21:30 node-2 kernel: [    3.130576] usb 2-1.4: Manufacturer: Avocent
Jul 25 14:21:30 node-2 kernel: [    3.130577] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 25 14:21:30 node-2 kernel: [    3.168466] xor: automatically using best checksumming function:
Jul 25 14:21:30 node-2 kernel: [    3.216616] hidraw: raw HID events driver (C) Jiri Kosina
Jul 25 14:21:30 node-2 kernel: [    3.221667] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 25 14:21:30 node-2 kernel: [    3.222028] scsi0 : LSI SAS based MegaRAID driver
Jul 25 14:21:30 node-2 kernel: [    3.229197] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 14:21:30 node-2 kernel: [    3.233644]    avx       : 66600.000 MB/sec
Jul 25 14:21:30 node-2 kernel: [    3.240033] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 14:21:30 node-2 kernel: [    3.244132] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 25 14:21:30 node-2 kernel: [    3.244188] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 25 14:21:30 node-2 kernel: [    3.244510] sd 0:2:0:0: [sda] Write Protect is off
Jul 25 14:21:30 node-2 kernel: [    3.244511] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 25 14:21:30 node-2 kernel: [    3.244580] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 25 14:21:30 node-2 kernel: [    3.266767]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 25 14:21:30 node-2 kernel: [    3.267367] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 25 14:21:30 node-2 kernel: [    3.311098] usbcore: registered new interface driver usbhid
Jul 25 14:21:30 node-2 kernel: [    3.311099] usbhid: USB HID core driver
Jul 25 14:21:30 node-2 kernel: [    3.314612] async_tx: api initialized (async)
Jul 25 14:21:30 node-2 kernel: [    3.375317] 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 25 14:21:30 node-2 kernel: [    3.387502] 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 25 14:21:30 node-2 kernel: [    3.400068] 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 25 14:21:30 node-2 kernel: [    3.409063] random: lvm urandom read with 28 bits of entropy available
Jul 25 14:21:30 node-2 kernel: [    3.419335] 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 25 14:21:30 node-2 kernel: [    3.432722] 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 25 14:21:30 node-2 kernel: [    3.446415] 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 25 14:21:30 node-2 kernel: [    3.446891] md: raid6 personality registered for level 6
Jul 25 14:21:30 node-2 kernel: [    3.446891] md: raid5 personality registered for level 5
Jul 25 14:21:30 node-2 kernel: [    3.446892] md: raid4 personality registered for level 4
Jul 25 14:21:30 node-2 kernel: [    3.484753] md: raid10 personality registered for level 10
Jul 25 14:21:30 node-2 kernel: [    3.540114] multipathd (375): /proc/375/oom_adj is deprecated, please use /proc/375/oom_score_adj instead.
Jul 25 14:21:30 node-2 kernel: [    3.572374] bio: create slab <bio-1> at 1
Jul 25 14:21:30 node-2 kernel: [    4.427081] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 14:21:30 node-2 kernel: [    5.128891] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 25 14:21:30 node-2 kernel: [    5.162366] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 25 14:21:30 node-2 kernel: [    5.270777] random: nonblocking pool is initialized
Jul 25 14:21:30 node-2 kernel: [    5.286683] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 25 14:21:30 node-2 kernel: [    5.328573] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 25 14:21:30 node-2 kernel: [    5.398167] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 14:21:30 node-2 kernel: [    5.558461] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 25 14:21:30 node-2 kernel: [    5.585732] XFS (dm-1): Mounting Filesystem
Jul 25 14:21:30 node-2 kernel: [    5.872720] XFS (dm-1): Ending clean mount
Jul 25 14:21:30 node-2 kernel: [    5.919367] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 14:21:30 node-2 kernel: [    5.967117] XFS (dm-2): Mounting Filesystem
Jul 25 14:21:30 node-2 kernel: [    6.131885] XFS (dm-2): Ending clean mount
Jul 25 14:21:30 node-2 kernel: [    6.293558] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 14:21:30 node-2 kernel: [    8.244080] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 25 14:21:30 node-2 kernel: [    8.271697] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 25 14:21:30 node-2 kernel: [    8.404766] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 25 14:21:30 node-2 kernel: [    8.404771] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 25 14:21:30 node-2 kernel: [    8.404775] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 25 14:21:30 node-2 kernel: [    8.404780] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 25 14:21:30 node-2 kernel: [    8.449959] systemd-udevd[801]: starting version 204
Jul 25 14:21:30 node-2 kernel: [    8.651244] power_meter ACPI000D:00: Found ACPI power meter.
Jul 25 14:21:30 node-2 kernel: [    8.651253] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 25 14:21:30 node-2 kernel: [    8.659417] wmi: Mapper loaded
Jul 25 14:21:30 node-2 kernel: [    8.718650] IPMI System Interface driver.
Jul 25 14:21:30 node-2 kernel: [    8.718721] ipmi_si: probing via ACPI
Jul 25 14:21:30 node-2 kernel: [    8.718739] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 25 14:21:30 node-2 kernel: [    8.718741] ipmi_si: Adding ACPI-specified kcs state machine
Jul 25 14:21:30 node-2 kernel: [    8.718760] ipmi_si: probing via SMBIOS
Jul 25 14:21:30 node-2 kernel: [    8.718762] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 14:21:30 node-2 kernel: [    8.718763] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 25 14:21:30 node-2 kernel: [    8.718765] ipmi_si: probing via SPMI
Jul 25 14:21:30 node-2 kernel: [    8.718766] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 14:21:30 node-2 kernel: [    8.718767] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 25 14:21:30 node-2 kernel: [    8.718769] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 25 14:21:30 node-2 kernel: [    8.734404] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 25 14:21:30 node-2 kernel: [    8.741091] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 25 14:21:30 node-2 kernel: [    8.741096] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 14:21:30 node-2 kernel: [    8.741098] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 25 14:21:30 node-2 kernel: [    8.741100] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 14:21:30 node-2 kernel: [    8.741113] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 25 14:21:30 node-2 kernel: [    8.809407] systemd-udevd[823]: renamed network interface eth1 to enp7s0
Jul 25 14:21:30 node-2 kernel: [    8.833306] systemd-udevd[821]: renamed network interface eth0 to enp6s0
Jul 25 14:21:30 node-2 kernel: [    8.870552] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 25 14:21:30 node-2 kernel: [    8.870626] ipmi_si 00:09: IPMI kcs interface initialized
Jul 25 14:21:30 node-2 kernel: [    8.877686] systemd-udevd[831]: renamed network interface eth2 to enp8s0
Jul 25 14:21:30 node-2 kernel: [    8.905249] systemd-udevd[819]: renamed network interface eth3 to enp9s0
Jul 25 14:21:30 node-2 kernel: [    9.193213] type=1400 audit(1469456461.214:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1080 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.193360] type=1400 audit(1469456461.214:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1080 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.193506] type=1400 audit(1469456461.214:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1080 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.194879] type=1400 audit(1469456461.214:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1078 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.195026] type=1400 audit(1469456461.214:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1078 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.195149] type=1400 audit(1469456461.214:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1078 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.206489] type=1400 audit(1469456461.226:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1097 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.206625] type=1400 audit(1469456461.226:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1097 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.206740] type=1400 audit(1469456461.226:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1097 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.211589] type=1400 audit(1469456461.230:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1079 comm="apparmor_parser"
Jul 25 14:21:30 node-2 kernel: [    9.710208] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 25 14:21:30 node-2 kernel: [    9.724611] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 25 14:21:30 node-2 kernel: [    9.967268] enic 0000:06:00.0 enp6s0: Link UP
Jul 25 14:21:30 node-2 kernel: [    9.968289] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 25 14:21:30 node-2 kernel: [    9.968299] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 25 14:21:30 node-2 kernel: [   20.933926] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 25 14:21:30 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 25 14:21:31 node-2 kernel: [   39.455718] init: failsafe main process (8442) killed by TERM signal
Jul 25 14:21:31 node-2 dbus[8488]: [system] AppArmor D-Bus mediation is enabled
Jul 25 14:21:31 node-2 kernel: [   39.694858] audit_printk_skb: 30 callbacks suppressed
Jul 25 14:21:31 node-2 kernel: [   39.694860] type=1400 audit(1469456491.310:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8562 comm="apparmor_parser"
Jul 25 14:21:31 node-2 kernel: [   39.695127] type=1400 audit(1469456491.310:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8561 comm="apparmor_parser"
Jul 25 14:21:31 node-2 kernel: [   39.695131] type=1400 audit(1469456491.310:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8561 comm="apparmor_parser"
Jul 25 14:21:31 node-2 kernel: [   39.695134] type=1400 audit(1469456491.310:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8561 comm="apparmor_parser"
Jul 25 14:21:31 node-2 kernel: [   39.695364] type=1400 audit(1469456491.310:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8561 comm="apparmor_parser"
Jul 25 14:21:31 node-2 kernel: [   39.695366] type=1400 audit(1469456491.310:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8561 comm="apparmor_parser"
Jul 25 14:21:31 node-2 kernel: [   39.695479] type=1400 audit(1469456491.310:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8561 comm="apparmor_parser"
Jul 25 14:21:31 node-2 kernel: [   39.785947] type=1400 audit(1469456491.402:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8564 comm="apparmor_parser"
Jul 25 14:21:31 node-2 cron[8600]: (CRON) INFO (pidfile fd = 3)
Jul 25 14:21:31 node-2 anacron[8616]: Anacron 2.3 started on 2016-07-25
Jul 25 14:21:31 node-2 cron[8623]: (CRON) STARTUP (fork ok)
Jul 25 14:21:31 node-2 cron[8623]: (CRON) INFO (Running @reboot jobs)
Jul 25 14:21:31 node-2 anacron[8616]: Will run job `cron.daily' in 5 min.
Jul 25 14:21:31 node-2 anacron[8616]: Will run job `cron.weekly' in 10 min.
Jul 25 14:21:31 node-2 anacron[8616]: Will run job `cron.monthly' in 15 min.
Jul 25 14:21:31 node-2 anacron[8616]: Jobs will be executed sequentially
Jul 25 14:21:31 node-2 multipathd: path checkers start up
Jul 25 14:21:32 node-2 postfix/master[8779]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 25 14:21:36 node-2 puppet-agent[8963]: Reopening log files
Jul 25 14:21:36 node-2 puppet-agent[8963]: Could not request certificate: Connection refused - connect(2)
Jul 25 14:21:47 node-2 puppet-user[9171]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 25 14:21:47 node-2 puppet-user[9171]: Compiled catalog for node-2.domain.tld in environment production in 0.05 seconds
Jul 25 14:21:48 node-2 puppet-user[9171]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 25 14:21:48 node-2 puppet-user[9171]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 25 14:21:48 node-2 puppet-user[9171]: Finished catalog run in 0.81 seconds
Jul 25 14:21:49 node-2 multipathd: uevent trigger error
Jul 25 14:21:49 node-2 puppet-user[9601]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 14:21:49 node-2 puppet-user[9601]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 25 14:21:49 node-2 puppet-user[9601]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 25 14:21:49 node-2 puppet-user[9601]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 25 14:21:49 node-2 puppet-user[9601]: (/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 25 14:21:49 node-2 puppet-user[9601]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 25 14:21:49 node-2 puppet-user[9601]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 25 14:21:49 node-2 puppet-user[9601]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 25 14:21:49 node-2 puppet-user[9601]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 25 14:21:49 node-2 puppet-user[9601]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 25 14:21:49 node-2 puppet-user[9601]: Finished catalog run in 0.06 seconds
Jul 25 14:21:51 node-2 puppet-user[10068]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 25 14:21:51 node-2 puppet-user[10068]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Jul 25 14:21:51 node-2 puppet-user[10068]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 25 14:21:51 node-2 puppet-user[10068]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 25 14:21:51 node-2 puppet-user[10068]: Finished catalog run in 0.03 seconds
Jul 25 14:21:52 node-2 puppet-user[10706]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 25 14:21:52 node-2 puppet-user[10706]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 25 14:21:52 node-2 puppet-user[10706]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 25 14:21:52 node-2 puppet-user[10706]: Finished catalog run in 0.05 seconds
Jul 25 14:21:54 node-2 puppet-user[11155]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 25 14:21:54 node-2 puppet-user[11155]: Compiled catalog for node-2.domain.tld in environment production in 0.26 seconds
Jul 25 14:21:54 node-2 puppet-user[11155]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 25 14:21:54 node-2 puppet-user[11155]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 25 14:21:55 node-2 puppet-user[11155]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 25 14:21:55 node-2 puppet-user[11155]: Finished catalog run in 0.83 seconds
Jul 25 14:21:56 node-2 puppet-user[11664]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 25 14:21:56 node-2 puppet-user[11664]: Compiled catalog for node-2.domain.tld in environment production in 0.22 seconds
Jul 25 14:21:56 node-2 puppet-user[11664]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 25 14:21:56 node-2 puppet-user[11664]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 25 14:21:56 node-2 puppet-user[11664]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 25 14:21:57 node-2 puppet-user[11664]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 25 14:21:57 node-2 puppet-user[11664]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 25 14:21:57 node-2 puppet-user[11664]: Finished catalog run in 0.34 seconds
Jul 25 14:21:58 node-2 puppet-user[12148]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 25 14:21:58 node-2 puppet-user[12148]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Jul 25 14:21:58 node-2 puppet-user[12148]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 25 14:21:58 node-2 kernel: [   67.315044] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 25 14:21:58 node-2 kernel: [   67.315097] 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 25 14:21:58 node-2 puppet-user[12148]: (/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 25 14:21:58 node-2 puppet-user[12148]: Finished catalog run in 0.06 seconds
Jul 25 14:22:00 node-2 puppet-user[12602]: (Scope(Class[main])) MODULAR: sync_time
Jul 25 14:22:00 node-2 puppet-user[12602]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 25 14:22:00 node-2 ntpdate[13020]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 25 14:22:01 node-2 CRON[13047]: (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 25 14:22:02 node-2 kernel: [   70.982124] init: plymouth-upstart-bridge main process ended, respawning
Jul 25 14:22:02 node-2 puppet-agent[8963]: Could not run: SIGTERM
Jul 25 14:22:02 node-2 kernel: [   71.265322] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 25 14:22:03 node-2 ec2: 
Jul 25 14:22:03 node-2 ec2: #############################################################
Jul 25 14:22:03 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 25 14:22:03 node-2 ec2: 1024 49:e0:3e:02:ff:0c:c9:cb:43:02:f1:d5:ea:e4:18:52  root@node-2.domain.tld (DSA)
Jul 25 14:22:03 node-2 ec2: 256 d8:6c:98:31:09:7e:26:d6:61:77:70:03:41:f3:33:6a  root@node-2.domain.tld (ECDSA)
Jul 25 14:22:03 node-2 ec2: 256 ad:04:d8:fb:18:37:74:0d:d7:29:c3:9b:c4:f5:e9:d3  root@node-2.domain.tld (ED25519)
Jul 25 14:22:03 node-2 ec2: 2048 29:eb:1f:f1:1c:78:38:8c:d7:cd:e3:27:e9:75:80:18  root@node-2.domain.tld (RSA)
Jul 25 14:22:03 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 25 14:22:03 node-2 ec2: #############################################################
Jul 25 14:22:06 node-2 ntpdate[13020]: adjust time server 10.20.0.2 offset 0.002425 sec
Jul 25 14:22:06 node-2 puppet-user[12602]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 25 14:22:06 node-2 puppet-user[12602]: Finished catalog run in 6.17 seconds
Jul 25 14:22:14 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:22:14 node-2 nailgun-agent: D, [2016-07-25T14:22:01.807573 #13050] DEBUG -- : Sleep for 13 seconds before sending request
Jul 25 14:22:14 node-2 nailgun-agent: I, [2016-07-25T14:22:14.823443 #13050]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 14:22:15 node-2 nailgun-agent: D, [2016-07-25T14:22:15.234294 #13050] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.399673 #13050] DEBUG -- : Trying to find block devices
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.399813 #13050] DEBUG -- : Found block device: sda
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.399876 #13050] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.399901 #13050] DEBUG -- : Trying to get list of physical devices
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.400055 #13050] DEBUG -- : Getting udev properties for device: sda
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.401953 #13050] 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 25 14:22:27 node-2 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"25529", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.402003 #13050] DEBUG -- : Trying to find out if device sda is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.402056 #13050] DEBUG -- : Device sda removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.402072 #13050] DEBUG -- : Device sda seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.402546 #13050] DEBUG -- : Getting udev properties for device: dm-0
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.404621 #13050] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-aXyA8yieJbwj5GtKEXg43eHpXu7NQjcQd0SyDEC9oPIe2LMv3DA08fO8WdVQATlQ /dev/disk/by-uuid/cb99ca31-930a-4d58-b3ad-3b7623403e37 /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-aXyA8yieJbwj5GtKEXg43eHpXu7NQjcQd0SyDEC9oPIe2LMv3DA08fO8WdVQATlQ", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cb99ca31-930a-4d58-b3ad-3b7623403e37", "ID_FS_UUID_ENC"=>"cb99ca31-930a-4d58-b3ad-3b7623403e37", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3
Jul 25 14:22:27 node-2 nailgun-agent: 0940", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.404662 #13050] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.404695 #13050] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.404709 #13050] DEBUG -- : Device dm-0 seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.404726 #13050] DEBUG -- : Getting udev properties for device: dm-1
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.406603 #13050] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-FzFJOB3fdblUhmBj8OySNlmReZ17wDQfj67LiV94D4kngTG2VC4espejo3HiPpzo /dev/disk/by-uuid/9e73ab71-4354-49a2-b3b2-565f4afc0c34 /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-FzFJOB3fdblUhmBj8OySNlmReZ17wDQfj67LiV94D4kngTG2VC4espejo3HiPpzo", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9e73ab71-4354-49a2-b3b2-565f4afc0c34", "ID_FS_UUID_ENC"=>"9e73ab71-4354-49a2-b3b2-565f4afc0c34", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64562", "nomdmonddf"=>"1", "nom
Jul 25 14:22:27 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.406632 #13050] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.406664 #13050] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.406703 #13050] DEBUG -- : Device dm-1 seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.406718 #13050] DEBUG -- : Getting udev properties for device: dm-2
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.408351 #13050] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-zAm0yrnkWKZsALRDyOzQYpXE801ewGZ0BNwPd2rceR3Hs1vcvVla1RC5AP6xkd2D /dev/disk/by-uuid/bc53699b-e3d4-4131-b780-d20e3724220e /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-zAm0yrnkWKZsALRDyOzQYpXE801ewGZ0BNwPd2rceR3Hs1vcvVla1RC5AP6xkd2D", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"bc53699b-e3d4-4131-b780-d20e3724220e", "ID_FS_UUID_ENC"=>"bc53699b-e3d4-4131-b780-d20e3724220e", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7
Jul 25 14:22:27 node-2 nailgun-agent: 2397", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.408396 #13050] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.408437 #13050] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.408451 #13050] DEBUG -- : Device dm-2 seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.408466 #13050] DEBUG -- : Getting udev properties for device: dm-3
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.410120 #13050] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-DCh1PUfn821dv906b5y6LwC976kGGsikrdzaJO1V2estCAC20n5zgwblzpH0GY58 /dev/disk/by-uuid/c68a13e3-3f6d-4a35-9dfb-116f18e0ee56 /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-DCh1PUfn821dv906b5y6LwC976kGGsikrdzaJO1V2estCAC20n5zgwblzpH0GY58", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c68a13e3-3f6d-4a35-9dfb-116f18e0ee56", "ID_FS_UUID_ENC"=>"c68a13e3-3f6d-4a35-9dfb-116f18e0ee56", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75602", "nomdmon
Jul 25 14:22:27 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.410146 #13050] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.410203 #13050] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.410217 #13050] DEBUG -- : Device dm-3 seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.410232 #13050] DEBUG -- : Getting udev properties for device: dm-4
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.411806 #13050] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-FpL6jef5QQqrZOylfkzcmKvh1W8nSBCxj6Rq6qAnJLXjp7U3FRmTGgMQTEjnXkuZ /dev/disk/by-uuid/2c9a163f-d824-4be8-b161-4bcee501106f /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-FpL6jef5QQqrZOylfkzcmKvh1W8nSBCxj6Rq6qAnJLXjp7U3FRmTGgMQTEjnXkuZ", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2c9a163f-d824-4be8-b161-4bcee501106f", "ID_FS_UUID_ENC"=>"2c9a163f-d824-4be8-b161-4bcee501106f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73835", "nomdmonddf"=>"1",
Jul 25 14:22:27 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.411841 #13050] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.411881 #13050] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.411896 #13050] DEBUG -- : Device dm-4 seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.411912 #13050] DEBUG -- : Getting udev properties for device: dm-5
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.413714 #13050] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-cvsCCN7GW3esuqWMIjr0KE6pAQbucBkjlkh6T25RBzVG09C4VTBrcZiT186iERlq /dev/disk/by-uuid/7f830f36-5ee4-49df-8419-c0facfc77428 /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-cvsCCN7GW3esuqWMIjr0KE6pAQbucBkjlkh6T25RBzVG09C4VTBrcZiT186iERlq", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"7f830f36-5ee4-49df-8419-c0facfc77428", "ID_FS_UUID_ENC"=>"7f830f36-5ee4-49df-8419-c0facfc77428", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70308", "nomdmonddf"=>"1", "nom
Jul 25 14:22:27 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.413740 #13050] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.413780 #13050] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.413809 #13050] DEBUG -- : Device dm-5 seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.413824 #13050] DEBUG -- : Getting udev properties for device: dm-6
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.415501 #13050] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-cvsCCN7GW3esuqWMIjr0KE6pAQbucBkjcGgwzLxJDZTzUVU28JzIkT7ttZqKXYB9 /dev/disk/by-uuid/ac5fa484-2dc6-41b8-9dd5-ce1dc1476ae6 /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-cvsCCN7GW3esuqWMIjr0KE6pAQbucBkjcGgwzLxJDZTzUVU28JzIkT7ttZqKXYB9", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"ac5fa484-2dc6-41b8-9dd5-ce1dc1476ae6", "ID_FS_UUID_ENC"=>"ac5fa484-2dc6-41b8-9dd5-ce1dc1476ae6", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70665", "nomdmonddf"=>"1", "nomdmonisw
Jul 25 14:22:27 node-2 nailgun-agent: "=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.415528 #13050] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.415582 #13050] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.415596 #13050] DEBUG -- : Device dm-6 seems to be appropriate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.415612 #13050] DEBUG -- : Getting udev properties for device: ram0
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.417109 #13050] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47249", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.417130 #13050] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.417180 #13050] DEBUG -- : Device ram0 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.417207 #13050] DEBUG -- : Getting udev properties for device: ram1
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.418691 #13050] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47265", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.418718 #13050] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.418768 #13050] DEBUG -- : Device ram1 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.418804 #13050] DEBUG -- : Getting udev properties for device: ram2
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.420245 #13050] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47367", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.420266 #13050] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.420295 #13050] DEBUG -- : Device ram2 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.420323 #13050] DEBUG -- : Getting udev properties for device: ram3
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.421923 #13050] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47381", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.421948 #13050] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.422005 #13050] DEBUG -- : Device ram3 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.422024 #13050] DEBUG -- : Getting udev properties for device: ram4
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.423537 #13050] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47396", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.423563 #13050] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.423597 #13050] DEBUG -- : Device ram4 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.423630 #13050] DEBUG -- : Getting udev properties for device: ram5
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.425108 #13050] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47409", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.425137 #13050] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.425181 #13050] DEBUG -- : Device ram5 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.425202 #13050] DEBUG -- : Getting udev properties for device: ram6
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.426765 #13050] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47429", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.426791 #13050] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.426853 #13050] DEBUG -- : Device ram6 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.426884 #13050] DEBUG -- : Getting udev properties for device: ram7
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.428369 #13050] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47445", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.428397 #13050] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.428442 #13050] DEBUG -- : Device ram7 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.428476 #13050] DEBUG -- : Getting udev properties for device: ram8
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.430178 #13050] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47465", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.430201 #13050] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.430243 #13050] DEBUG -- : Device ram8 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.430262 #13050] DEBUG -- : Getting udev properties for device: ram9
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.431691 #13050] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47484", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.431729 #13050] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.431761 #13050] DEBUG -- : Device ram9 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.431781 #13050] DEBUG -- : Getting udev properties for device: loop0
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.433254 #13050] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47105", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.433293 #13050] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.433349 #13050] DEBUG -- : Device loop0 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.433367 #13050] DEBUG -- : Getting udev properties for device: loop1
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.439580 #13050] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47133", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.439611 #13050] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.439656 #13050] DEBUG -- : Device loop1 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.439677 #13050] DEBUG -- : Getting udev properties for device: loop2
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.441449 #13050] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47147", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.441471 #13050] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.441513 #13050] DEBUG -- : Device loop2 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.441533 #13050] DEBUG -- : Getting udev properties for device: loop3
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.443216 #13050] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47163", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.443277 #13050] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.443318 #13050] DEBUG -- : Device loop3 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.443338 #13050] DEBUG -- : Getting udev properties for device: loop4
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.445018 #13050] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47178", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.445042 #13050] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.445111 #13050] DEBUG -- : Device loop4 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.445130 #13050] DEBUG -- : Getting udev properties for device: loop5
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.446827 #13050] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47193", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.446853 #13050] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.446884 #13050] DEBUG -- : Device loop5 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.446938 #13050] DEBUG -- : Getting udev properties for device: loop6
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.448402 #13050] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47219", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.448424 #13050] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.448452 #13050] DEBUG -- : Device loop6 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.448470 #13050] DEBUG -- : Getting udev properties for device: loop7
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.450266 #13050] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47235", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.450288 #13050] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.450322 #13050] DEBUG -- : Device loop7 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.450342 #13050] DEBUG -- : Getting udev properties for device: ram10
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.451988 #13050] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47281", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.452010 #13050] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.452044 #13050] DEBUG -- : Device ram10 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.452062 #13050] DEBUG -- : Getting udev properties for device: ram11
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.453718 #13050] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47296", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.453739 #13050] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.453770 #13050] DEBUG -- : Device ram11 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.453788 #13050] DEBUG -- : Getting udev properties for device: ram12
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.455247 #13050] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47311", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.455309 #13050] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.455349 #13050] DEBUG -- : Device ram12 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.455369 #13050] DEBUG -- : Getting udev properties for device: ram13
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.456799 #13050] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47326", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.456821 #13050] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.456899 #13050] DEBUG -- : Device ram13 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.456919 #13050] DEBUG -- : Getting udev properties for device: ram14
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.458405 #13050] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47339", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.458433 #13050] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.458466 #13050] DEBUG -- : Device ram14 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.458518 #13050] DEBUG -- : Getting udev properties for device: ram15
Jul 25 14:22:27 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460081 #13050] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47352", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460104 #13050] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460135 #13050] DEBUG -- : Device ram15 removable parameter: "0"
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460172 #13050] 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 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460221 #13050] DEBUG -- : Block device seems to be physical data storage: sda
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460259 #13050] DEBUG -- : Found block device: dm-0
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460284 #13050] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460297 #13050] DEBUG -- : Found block device: dm-1
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460309 #13050] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460318 #13050] DEBUG -- : Found block device: dm-2
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460329 #13050] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460338 #13050] DEBUG -- : Found block device: dm-3
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460348 #13050] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460357 #13050] DEBUG -- : Found block device: dm-4
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460367 #13050] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460410 #13050] DEBUG -- : Found block device: dm-5
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460421 #13050] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460430 #13050] DEBUG -- : Found block device: dm-6
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460439 #13050] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460447 #13050] DEBUG -- : Found block device: ram0
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460457 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460466 #13050] DEBUG -- : Found block device: ram1
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460477 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460486 #13050] DEBUG -- : Found block device: ram2
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460495 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460541 #13050] DEBUG -- : Found block device: ram3
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460551 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460560 #13050] DEBUG -- : Found block device: ram4
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460570 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460579 #13050] DEBUG -- : Found block device: ram5
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460589 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460597 #13050] DEBUG -- : Found block device: ram6
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460607 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460616 #13050] DEBUG -- : Found block device: ram7
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460625 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460683 #13050] DEBUG -- : Found block device: ram8
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460694 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460703 #13050] DEBUG -- : Found block device: ram9
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460714 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460723 #13050] DEBUG -- : Found block device: loop0
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460732 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460741 #13050] DEBUG -- : Found block device: loop1
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460750 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460759 #13050] DEBUG -- : Found block device: loop2
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460769 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460832 #13050] DEBUG -- : Found block device: loop3
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460842 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460851 #13050] DEBUG -- : Found block device: loop4
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460861 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460870 #13050] DEBUG -- : Found block device: loop5
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460879 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460888 #13050] DEBUG -- : Found block device: loop6
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460897 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460951 #13050] DEBUG -- : Found block device: loop7
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460962 #13050] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460971 #13050] DEBUG -- : Found block device: ram10
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460982 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.460990 #13050] DEBUG -- : Found block device: ram11
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461000 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461009 #13050] DEBUG -- : Found block device: ram12
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461020 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461028 #13050] DEBUG -- : Found block device: ram13
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461038 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461094 #13050] DEBUG -- : Found block device: ram14
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461106 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461115 #13050] DEBUG -- : Found block device: ram15
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461124 #13050] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.461151 #13050] 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 25 14:22:27 node-2 nailgun-agent: D, [2016-07-25T14:22:27.594597 #13050] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 25 14:22:27 node-2 nailgun-agent: I, [2016-07-25T14:22:27.594787 #13050]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 25 14:22:55 node-2 puppet-user[13708]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 14:22:55 node-2 puppet-user[13708]: Compiled catalog for node-2.domain.tld in environment production in 0.11 seconds
Jul 25 14:22:55 node-2 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 25 14:22:55 node-2 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 25 14:22:55 node-2 puppet-user[13708]: Finished catalog run in 0.09 seconds
Jul 25 14:22:57 node-2 puppet-user[14158]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 25 14:22:58 node-2 puppet-user[14158]: Compiled catalog for node-2.domain.tld in environment production in 1.03 seconds
Jul 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:22:58 node-2 puppet-user[14158]: (/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 25 14:23:01 node-2 CRON[14710]: (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 25 14:23:14 node-2 puppet-user[14158]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 25 14:23:15 node-2 puppet-user[14158]: Finished catalog run in 16.83 seconds
Jul 25 14:23:17 node-2 puppet-user[15056]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 25 14:23:17 node-2 puppet-user[15056]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Jul 25 14:23:19 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:23:19 node-2 nailgun-agent: I, [2016-07-25T14:23:19.764283 #14713]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 14:23:22 node-2 puppet-user[15056]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 25 14:23:32 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:23:32 node-2 nailgun-agent: I, [2016-07-25T14:23:32.921023 #14713]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 25 14:23:58 node-2 puppet-user[15056]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 25 14:23:58 node-2 puppet-user[15056]: Finished catalog run in 41.08 seconds
Jul 25 14:24:00 node-2 puppet-user[17905]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 25 14:24:00 node-2 puppet-user[17905]: Compiled catalog for node-2.domain.tld in environment production in 0.76 seconds
Jul 25 14:24:01 node-2 puppet-user[17905]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 25 14:24:01 node-2 puppet-user[17905]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 25 14:24:01 node-2 puppet-user[17905]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 25 14:24:01 node-2 puppet-user[17905]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 25 14:24:01 node-2 puppet-user[17905]: Finished catalog run in 0.10 seconds
Jul 25 14:24:01 node-2 CRON[18398]: (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 25 14:24:02 node-2 puppet-user[18370]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 25 14:24:03 node-2 puppet-user[18370]: Compiled catalog for node-2.domain.tld in environment production in 0.87 seconds
Jul 25 14:24:04 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 25 14:24:04 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 25 14:24:04 node-2 crontab[18813]: (root) LIST (root)
Jul 25 14:24:04 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 25 14:24:04 node-2 crontab[18814]: (root) REPLACE (root)
Jul 25 14:24:06 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 25 14:24:07 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 25 14:24:07 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 25 14:24:07 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/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 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 25 14:24:08 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 25 14:24:09 node-2 puppet-user[18370]: (/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 25 14:24:09 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 25 14:24:09 node-2 puppet-user[18370]: (/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 25 14:24:09 node-2 puppet-user[18370]: (/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 25 14:24:09 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 25 14:24:09 node-2 puppet-user[18370]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 25 14:24:09 node-2 puppet-user[18370]: (/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 25 14:24:09 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8415" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:09 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 25 14:24:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:24:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:25:35 node-2 ntpdate[29819]: no servers can be used, exiting
<27>Jul 25 14:26:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:23 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:23 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:23 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:23 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:26 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:26:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:32 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:32 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:32 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:32 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:32 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:27:43 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 14:27:43 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 14:27:49 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 14:27:49 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 14:27:55 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 14:28:01 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 14:28:01 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 14:28:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:27 node-2 multipathd: uevent trigger error
<129>Jul 25 14:28:29 node-2 haproxy[19386]: 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 25 14:28:30 node-2 haproxy[19390]: 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 25 14:28:30 node-2 haproxy[19390]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:30 node-2 haproxy[19390]: proxy mysqld has no server available!
<27>Jul 25 14:28:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:36 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:36 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:36 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:36 node-2 multipathd: uevent trigger error
<129>Jul 25 14:28:39 node-2 haproxy[22043]: 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 25 14:28:39 node-2 haproxy[22043]: 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 25 14:28:39 node-2 haproxy[22043]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:39 node-2 haproxy[22043]: proxy mysqld has no server available!
<129>Jul 25 14:28:40 node-2 haproxy[22047]: 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 25 14:28:40 node-2 haproxy[22047]: 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 25 14:28:40 node-2 haproxy[22047]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:40 node-2 haproxy[22047]: proxy object-storage has no server available!
<27>Jul 25 14:28:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:42 node-2 multipathd: uevent trigger error
<129>Jul 25 14:28:44 node-2 haproxy[23508]: 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 25 14:28:45 node-2 haproxy[23512]: 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 25 14:28:45 node-2 haproxy[23512]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:45 node-2 haproxy[23512]: proxy neutron has no server available!
<129>Jul 25 14:28:45 node-2 haproxy[23512]: 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 25 14:28:45 node-2 haproxy[23512]: 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 25 14:28:45 node-2 haproxy[23512]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:45 node-2 haproxy[23512]: proxy mysqld has no server available!
<129>Jul 25 14:28:46 node-2 haproxy[23512]: 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 25 14:28:46 node-2 haproxy[23512]: 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 25 14:28:46 node-2 haproxy[23512]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:46 node-2 haproxy[23512]: proxy object-storage has no server available!
<27>Jul 25 14:28:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:48 node-2 multipathd: uevent trigger error
<129>Jul 25 14:28:50 node-2 haproxy[24951]: 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 25 14:28:50 node-2 haproxy[24951]: 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 25 14:28:50 node-2 haproxy[24951]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:50 node-2 haproxy[24951]: proxy keystone-1 has no server available!
<129>Jul 25 14:28:51 node-2 haproxy[24955]: 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 25 14:28:51 node-2 haproxy[24955]: 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 25 14:28:51 node-2 haproxy[24955]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:51 node-2 haproxy[24955]: proxy keystone-2 has no server available!
<129>Jul 25 14:28:51 node-2 haproxy[24955]: 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 25 14:28:51 node-2 haproxy[24955]: 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 25 14:28:51 node-2 haproxy[24955]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:51 node-2 haproxy[24955]: proxy neutron has no server available!
<129>Jul 25 14:28:51 node-2 haproxy[24955]: 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 25 14:28:51 node-2 haproxy[24955]: 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 25 14:28:51 node-2 haproxy[24955]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:51 node-2 haproxy[24955]: proxy mysqld has no server available!
<129>Jul 25 14:28:52 node-2 haproxy[24955]: 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 25 14:28:52 node-2 haproxy[24955]: 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 25 14:28:52 node-2 haproxy[24955]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:52 node-2 haproxy[24955]: proxy object-storage has no server available!
<27>Jul 25 14:28:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:53 node-2 multipathd: uevent trigger error
<129>Jul 25 14:28:56 node-2 haproxy[26341]: 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 25 14:28:56 node-2 haproxy[26341]: 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 25 14:28:56 node-2 haproxy[26341]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:56 node-2 haproxy[26341]: proxy keystone-1 has no server available!
<129>Jul 25 14:28:56 node-2 haproxy[26341]: 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 25 14:28:56 node-2 haproxy[26341]: 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 25 14:28:56 node-2 haproxy[26341]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:56 node-2 haproxy[26341]: proxy keystone-2 has no server available!
<129>Jul 25 14:28:56 node-2 haproxy[26341]: 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 25 14:28:56 node-2 haproxy[26341]: 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 25 14:28:56 node-2 haproxy[26341]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:56 node-2 haproxy[26341]: proxy neutron has no server available!
<129>Jul 25 14:28:56 node-2 haproxy[26341]: 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 25 14:28:57 node-2 haproxy[26348]: 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 25 14:28:57 node-2 haproxy[26348]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:57 node-2 haproxy[26348]: proxy mysqld has no server available!
<129>Jul 25 14:28:57 node-2 haproxy[26348]: 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 25 14:28:57 node-2 haproxy[26348]: 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 25 14:28:57 node-2 haproxy[26348]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:57 node-2 haproxy[26348]: proxy object-storage has no server available!
<129>Jul 25 14:28:57 node-2 haproxy[26348]: 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 25 14:28:57 node-2 haproxy[26348]: 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 25 14:28:57 node-2 haproxy[26348]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:28:57 node-2 haproxy[26348]: proxy aodh has no server available!
<27>Jul 25 14:28:59 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:59 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:59 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:59 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:59 node-2 multipathd: uevent trigger error
<27>Jul 25 14:28:59 node-2 multipathd: uevent trigger error
<129>Jul 25 14:29:01 node-2 haproxy[27782]: 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 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:02 node-2 haproxy[27789]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:02 node-2 haproxy[27789]: proxy keystone-1 has no server available!
<129>Jul 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:02 node-2 haproxy[27789]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:02 node-2 haproxy[27789]: proxy keystone-2 has no server available!
<129>Jul 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:02 node-2 haproxy[27789]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:02 node-2 haproxy[27789]: proxy neutron has no server available!
<129>Jul 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:02 node-2 haproxy[27789]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:02 node-2 haproxy[27789]: proxy mysqld has no server available!
<129>Jul 25 14:29:02 node-2 haproxy[27789]: 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 25 14:29:03 node-2 haproxy[27789]: 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 25 14:29:03 node-2 haproxy[27789]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:03 node-2 haproxy[27789]: proxy object-storage has no server available!
<129>Jul 25 14:29:03 node-2 haproxy[27789]: 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 25 14:29:03 node-2 haproxy[27789]: 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 25 14:29:03 node-2 haproxy[27789]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:03 node-2 haproxy[27789]: proxy aodh has no server available!
<129>Jul 25 14:29:03 node-2 haproxy[27789]: 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 25 14:29:03 node-2 haproxy[27789]: 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 25 14:29:03 node-2 haproxy[27789]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:03 node-2 haproxy[27789]: proxy ceilometer has no server available!
<27>Jul 25 14:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:05 node-2 multipathd: uevent trigger error
<129>Jul 25 14:29:07 node-2 haproxy[29187]: 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 25 14:29:07 node-2 haproxy[29187]: 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 25 14:29:07 node-2 haproxy[29187]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:07 node-2 haproxy[29187]: proxy keystone-1 has no server available!
<129>Jul 25 14:29:07 node-2 haproxy[29187]: 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 25 14:29:07 node-2 haproxy[29187]: 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 25 14:29:07 node-2 haproxy[29187]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:07 node-2 haproxy[29187]: proxy keystone-2 has no server available!
<129>Jul 25 14:29:07 node-2 haproxy[29187]: 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 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:08 node-2 haproxy[29191]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:08 node-2 haproxy[29191]: proxy neutron has no server available!
<129>Jul 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:08 node-2 haproxy[29191]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:08 node-2 haproxy[29191]: proxy mysqld has no server available!
<129>Jul 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:08 node-2 haproxy[29191]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:08 node-2 haproxy[29191]: proxy object-storage has no server available!
<129>Jul 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:08 node-2 haproxy[29191]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:08 node-2 haproxy[29191]: proxy aodh has no server available!
<129>Jul 25 14:29:08 node-2 haproxy[29191]: 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 25 14:29:09 node-2 haproxy[29191]: 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 25 14:29:09 node-2 haproxy[29191]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:09 node-2 haproxy[29191]: proxy ceilometer has no server available!
<27>Jul 25 14:29:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:10 node-2 multipathd: uevent trigger error
<129>Jul 25 14:29:12 node-2 haproxy[30590]: 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 25 14:29:12 node-2 haproxy[30590]: 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 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:13 node-2 haproxy[30594]: proxy keystone-1 has no server available!
<129>Jul 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:13 node-2 haproxy[30594]: proxy keystone-2 has no server available!
<129>Jul 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:13 node-2 haproxy[30594]: proxy neutron has no server available!
<129>Jul 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:13 node-2 haproxy[30594]: proxy mysqld has no server available!
<129>Jul 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:13 node-2 haproxy[30594]: 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 25 14:29:14 node-2 haproxy[30594]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:14 node-2 haproxy[30594]: proxy object-storage has no server available!
<129>Jul 25 14:29:14 node-2 haproxy[30594]: 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 25 14:29:14 node-2 haproxy[30594]: 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 25 14:29:14 node-2 haproxy[30594]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:14 node-2 haproxy[30594]: proxy aodh has no server available!
<129>Jul 25 14:29:14 node-2 haproxy[30594]: 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 25 14:29:14 node-2 haproxy[30594]: 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 25 14:29:14 node-2 haproxy[30594]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:14 node-2 haproxy[30594]: proxy ceilometer has no server available!
<27>Jul 25 14:29:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:15 node-2 multipathd: uevent trigger error
<129>Jul 25 14:29:18 node-2 haproxy[32074]: 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 25 14:29:18 node-2 haproxy[32074]: 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 25 14:29:18 node-2 haproxy[32074]: 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 25 14:29:18 node-2 haproxy[32074]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:18 node-2 haproxy[32074]: proxy keystone-1 has no server available!
<129>Jul 25 14:29:18 node-2 haproxy[32074]: 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 25 14:29:18 node-2 haproxy[32074]: 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 25 14:29:18 node-2 haproxy[32074]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:18 node-2 haproxy[32074]: proxy keystone-2 has no server available!
<129>Jul 25 14:29:18 node-2 haproxy[32074]: 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 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:19 node-2 haproxy[32078]: proxy glance-api has no server available!
<129>Jul 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:19 node-2 haproxy[32078]: proxy glance-glare has no server available!
<129>Jul 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:19 node-2 haproxy[32078]: proxy neutron has no server available!
<129>Jul 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:19 node-2 haproxy[32078]: proxy glance-registry has no server available!
<129>Jul 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:19 node-2 haproxy[32078]: proxy mysqld has no server available!
<129>Jul 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: 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 25 14:29:19 node-2 haproxy[32078]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:19 node-2 haproxy[32078]: proxy object-storage has no server available!
<129>Jul 25 14:29:20 node-2 haproxy[32078]: 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 25 14:29:20 node-2 haproxy[32078]: 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 25 14:29:20 node-2 haproxy[32078]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:20 node-2 haproxy[32078]: proxy aodh has no server available!
<129>Jul 25 14:29:20 node-2 haproxy[32078]: 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 25 14:29:20 node-2 haproxy[32078]: 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 25 14:29:20 node-2 haproxy[32078]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:20 node-2 haproxy[32078]: proxy ceilometer has no server available!
<27>Jul 25 14:29:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-2 multipathd: uevent trigger error
<129>Jul 25 14:29:24 node-2 haproxy[1274]: 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 25 14:29:24 node-2 haproxy[1274]: 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 25 14:29:24 node-2 haproxy[1274]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:24 node-2 haproxy[1274]: proxy keystone-1 has no server available!
<129>Jul 25 14:29:24 node-2 haproxy[1274]: 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 25 14:29:24 node-2 haproxy[1274]: 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 25 14:29:24 node-2 haproxy[1274]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:24 node-2 haproxy[1274]: proxy keystone-2 has no server available!
<129>Jul 25 14:29:24 node-2 haproxy[1274]: 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 25 14:29:24 node-2 haproxy[1274]: 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 25 14:29:25 node-2 haproxy[1293]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy nova-api has no server available!
<129>Jul 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy nova-metadata-api has no server available!
<129>Jul 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy glance-api has no server available!
<129>Jul 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy glance-glare has no server available!
<129>Jul 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy neutron has no server available!
<129>Jul 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy glance-registry has no server available!
<129>Jul 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy mysqld has no server available!
<129>Jul 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: 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 25 14:29:25 node-2 haproxy[1293]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:25 node-2 haproxy[1293]: proxy object-storage has no server available!
<129>Jul 25 14:29:26 node-2 haproxy[1293]: 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 25 14:29:26 node-2 haproxy[1293]: 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 25 14:29:26 node-2 haproxy[1293]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:26 node-2 haproxy[1293]: proxy aodh has no server available!
<129>Jul 25 14:29:26 node-2 haproxy[1293]: 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 25 14:29:26 node-2 haproxy[1293]: 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 25 14:29:26 node-2 haproxy[1293]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:26 node-2 haproxy[1293]: proxy ceilometer has no server available!
<129>Jul 25 14:29:26 node-2 haproxy[1293]: 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 25 14:29:26 node-2 haproxy[1293]: 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 25 14:29:26 node-2 haproxy[1293]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:26 node-2 haproxy[1293]: proxy nova-novncproxy has no server available!
<27>Jul 25 14:29:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-2 multipathd: uevent trigger error
<129>Jul 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:30 node-2 haproxy[2714]: proxy keystone-1 has no server available!
<129>Jul 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:30 node-2 haproxy[2714]: proxy keystone-2 has no server available!
<129>Jul 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:30 node-2 haproxy[2714]: proxy nova-api has no server available!
<129>Jul 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:30 node-2 haproxy[2714]: proxy nova-metadata-api has no server available!
<129>Jul 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:30 node-2 haproxy[2714]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:30 node-2 haproxy[2714]: proxy cinder-api has no server available!
<129>Jul 25 14:29:30 node-2 haproxy[2714]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy glance-api has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy glance-glare has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy neutron has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy glance-registry has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy mysqld has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy object-storage has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy aodh has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:31 node-2 haproxy[2725]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:31 node-2 haproxy[2725]: proxy ceilometer has no server available!
<129>Jul 25 14:29:31 node-2 haproxy[2725]: 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 25 14:29:32 node-2 haproxy[2725]: 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 25 14:29:32 node-2 haproxy[2725]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:32 node-2 haproxy[2725]: proxy nova-novncproxy has no server available!
<27>Jul 25 14:29:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:33 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:33 node-2 multipathd: uevent trigger error
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:36 node-2 haproxy[4195]: proxy keystone-1 has no server available!
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:36 node-2 haproxy[4195]: proxy keystone-2 has no server available!
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:36 node-2 haproxy[4195]: proxy nova-api has no server available!
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:36 node-2 haproxy[4195]: proxy nova-metadata-api has no server available!
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:36 node-2 haproxy[4195]: proxy cinder-api has no server available!
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:36 node-2 haproxy[4195]: proxy glance-api has no server available!
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:36 node-2 haproxy[4195]: proxy glance-glare has no server available!
<129>Jul 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:36 node-2 haproxy[4195]: 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 25 14:29:37 node-2 haproxy[4199]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy neutron has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy glance-registry has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy mysqld has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy object-storage has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy aodh has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy ceilometer has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy heat-api has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy heat-api-cfn has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy heat-api-cloudwatch has no server available!
<129>Jul 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: 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 25 14:29:37 node-2 haproxy[4199]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:37 node-2 haproxy[4199]: proxy nova-novncproxy has no server available!
<27>Jul 25 14:29:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:42 node-2 multipathd: uevent trigger error
<27>Jul 25 14:29:54 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 25 14:30:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:30:17 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 14:30:23 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 25 14:30:25 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 25 14:31:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:33:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:48 node-2 multipathd: uevent trigger error
<27>Jul 25 14:33:48 node-2 multipathd: uevent trigger error
<43>Jul 25 14:34:10 node-2 apache2_error [Mon Jul 25 14:34:03.056595 2016] [mpm_event:notice] [pid 16930:tid 139906614994816] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 14:34:10 node-2 apache2_error [Mon Jul 25 14:34:03.056736 2016] [core:notice] [pid 16930:tid 139906614994816] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 14:34:10 node-2 apache2_error [Mon Jul 25 14:34:06.614667 2016] [mpm_event:notice] [pid 16930:tid 139906614994816] AH00491: caught SIGTERM, shutting down
<43>Jul 25 14:34:10 node-2 apache2_error [Mon Jul 25 14:34:07.706404 2016] [mpm_worker:notice] [pid 17379:tid 140147722786688] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 14:34:10 node-2 apache2_error [Mon Jul 25 14:34:07.706426 2016] [core:notice] [pid 17379:tid 140147722786688] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:34:12 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:12 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:12 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:12 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:12 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:17 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:17 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:17 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:17 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:17 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:34:20 node-2 multipathd: uevent trigger error
<43>Jul 25 14:35:40 node-2 apache2_error [Mon Jul 25 14:35:39.202847 2016] [mpm_worker:notice] [pid 17379:tid 140147722786688] AH00295: caught SIGTERM, shutting down
<43>Jul 25 14:35:40 node-2 apache2_error [Mon Jul 25 14:35:39.960888 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:35:40 node-2 apache2_error [Mon Jul 25 14:35:39.960954 2016] [core:notice] [pid 2166:tid 139731254581120] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:36:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 25 14:36:30 node-2 apache2_error [Mon Jul 25 14:36:26.977150 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:36:30 node-2 apache2_error [Mon Jul 25 14:36:27.361174 2016] [mpm_worker:warn] [pid 2166:tid 139731254581120] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:36:30 node-2 apache2_error [Mon Jul 25 14:36:27.365750 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:36:30 node-2 apache2_error [Mon Jul 25 14:36:27.365786 2016] [core:notice] [pid 2166:tid 139731254581120] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:37:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:38:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:38:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:38:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:38:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:38:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:38:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:39:06 node-2 multipathd: uevent trigger error
<27>Jul 25 14:39:06 node-2 multipathd: uevent trigger error
<27>Jul 25 14:39:06 node-2 multipathd: uevent trigger error
<27>Jul 25 14:39:06 node-2 multipathd: uevent trigger error
<27>Jul 25 14:39:06 node-2 multipathd: uevent trigger error
<27>Jul 25 14:39:14 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:40:01 node-2 multipathd: uevent trigger error
<27>Jul 25 14:40:01 node-2 multipathd: uevent trigger error
<27>Jul 25 14:40:01 node-2 multipathd: uevent trigger error
<27>Jul 25 14:40:01 node-2 multipathd: uevent trigger error
<27>Jul 25 14:40:01 node-2 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-2 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-2 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-2 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-2 multipathd: uevent trigger error
<27>Jul 25 14:41:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:41:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:42:19 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:19 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:19 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:19 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:19 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:19 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:42:41 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:08 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:45:24 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:24 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:24 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:24 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:24 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:29 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:29 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:29 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:29 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:56 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:56 node-2 multipathd: uevent trigger error
<27>Jul 25 14:45:56 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:00 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:00 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:00 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:00 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:00 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:46:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:47:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:48:02 node-2 multipathd: uevent trigger error
<27>Jul 25 14:48:02 node-2 multipathd: uevent trigger error
<27>Jul 25 14:48:02 node-2 multipathd: uevent trigger error
<27>Jul 25 14:48:02 node-2 multipathd: uevent trigger error
<27>Jul 25 14:48:02 node-2 multipathd: uevent trigger error
<27>Jul 25 14:48:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:50:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:50 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:50 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:50 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:50 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:50:55 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:51:44 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:44 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:45 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:45 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:45 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:49 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:49 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:49 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:49 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:49 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:51:53 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:40 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:40 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:40 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:40 node-2 multipathd: uevent trigger error
<27>Jul 25 14:52:40 node-2 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:05 node-2 multipathd: uevent trigger error
<11>Jul 25 14:54:18 node-2 liberasurecode[23177]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:18 node-2 liberasurecode[23177]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:18 node-2 liberasurecode[23177]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:18 node-2 liberasurecode[23177]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:18 node-2 liberasurecode[23206]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:18 node-2 liberasurecode[23206]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:18 node-2 liberasurecode[23206]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:18 node-2 liberasurecode[23206]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:21 node-2 liberasurecode[23656]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:21 node-2 liberasurecode[23656]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:21 node-2 liberasurecode[23656]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:21 node-2 liberasurecode[23656]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 14:54:22 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 25 14:54:26 node-2 liberasurecode[24519]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24519]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24519]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24519]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24556]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24556]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24556]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24556]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24603]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:26 node-2 liberasurecode[24603]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24665]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24665]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24679]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24679]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24679]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24679]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24691]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24691]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24691]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24704]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:27 node-2 liberasurecode[24704]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:35 node-2 liberasurecode[26828]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:35 node-2 liberasurecode[26828]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:35 node-2 liberasurecode[26828]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:35 node-2 liberasurecode[26828]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 14:54:44 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:44 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:44 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:44 node-2 multipathd: uevent trigger error
<27>Jul 25 14:54:44 node-2 multipathd: uevent trigger error
<11>Jul 25 14:55:01 node-2 liberasurecode[29532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-2 liberasurecode[29532]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-2 liberasurecode[29532]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-2 liberasurecode[29532]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Jul 25 14:55:32 node-2 apache2_error [Mon Jul 25 14:55:31.882567 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:55:42 node-2 apache2_error [Mon Jul 25 14:55:32.265621 2016] [mpm_worker:warn] [pid 2166:tid 139731254581120] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:55:42 node-2 apache2_error [Mon Jul 25 14:55:32.270074 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:55:42 node-2 apache2_error [Mon Jul 25 14:55:32.270092 2016] [core:notice] [pid 2166:tid 139731254581120] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 14:56:12 node-2 apache2_error [Mon Jul 25 14:56:09.277316 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:56:12 node-2 apache2_error [Mon Jul 25 14:56:09.473023 2016] [mpm_worker:warn] [pid 2166:tid 139731254581120] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:56:12 node-2 apache2_error [Mon Jul 25 14:56:09.482862 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:56:12 node-2 apache2_error [Mon Jul 25 14:56:09.482893 2016] [core:notice] [pid 2166:tid 139731254581120] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:56:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:13 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:58 node-2 multipathd: uevent trigger error
<27>Jul 25 14:56:58 node-2 multipathd: uevent trigger error
<43>Jul 25 14:57:02 node-2 apache2_error [Mon Jul 25 14:56:54.732283 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:57:02 node-2 apache2_error [Mon Jul 25 14:56:54.928788 2016] [mpm_worker:warn] [pid 2166:tid 139731254581120] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:57:02 node-2 apache2_error [Mon Jul 25 14:56:54.937434 2016] [mpm_worker:notice] [pid 2166:tid 139731254581120] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:57:02 node-2 apache2_error [Mon Jul 25 14:56:54.937457 2016] [core:notice] [pid 2166:tid 139731254581120] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:57:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:05 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:11 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:57:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:35 node-2 multipathd: uevent trigger error
<27>Jul 25 14:57:59 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:07 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 25 14:58:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:16 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:20 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:25 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:42 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 14:58:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:58:43 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:10 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:15 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:27 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:39 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:51 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:51 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:51 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:51 node-2 multipathd: uevent trigger error
<27>Jul 25 14:59:51 node-2 multipathd: uevent trigger error
<11>Jul 25 15:00:01 node-2 liberasurecode[2450]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 15:00:01 node-2 liberasurecode[2450]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 15:00:01 node-2 liberasurecode[2450]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 15:00:01 node-2 liberasurecode[2450]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 15:00:21 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:21 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:21 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:21 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:21 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:25 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:25 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:25 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:25 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:25 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:29 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:29 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:29 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:29 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:29 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:34 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:34 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:34 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:34 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:34 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:34 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:39 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:39 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:39 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:39 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:39 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:44 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:44 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:44 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:44 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:44 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:49 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:49 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:49 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:49 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:49 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:53 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:53 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:53 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:54 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:54 node-2 multipathd: uevent trigger error
<27>Jul 25 15:00:54 node-2 multipathd: uevent trigger error
