Jul 29 04:08:26 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8409" x-info="http://www.rsyslog.com"] start
Jul 29 04:08:26 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 29 04:08:26 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 29 04:08:26 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 29 04:08:26 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 29 04:08:26 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 29 04:08:26 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 29 04:08:26 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 29 04:08:26 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=2412558c-77ba-4a40-8577-74ac4cd89780 nomdmonddf nomdmonisw
Jul 29 04:08:26 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 29 04:08:26 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 29 04:08:26 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 29 04:08:26 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 29 04:08:26 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 29 04:08:26 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 29 04:08:26 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 29 04:08:26 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 29 04:08:26 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 29 04:08:26 node-2 kernel: [    0.000000] No AGP bridge found
Jul 29 04:08:26 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 29 04:08:26 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 29 04:08:26 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 29 04:08:26 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 29 04:08:26 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 29 04:08:26 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 29 04:08:26 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 29 04:08:26 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 29 04:08:26 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 29 04:08:26 node-2 kernel: [    0.000000]   2 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000]   3 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000]   4 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000]   5 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000]   6 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000]   7 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000]   8 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000]   9 disabled
Jul 29 04:08:26 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 29 04:08:26 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 29 04:08:26 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 29 04:08:26 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 29 04:08:26 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 29 04:08:26 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 29 04:08:26 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 29 04:08:26 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 29 04:08:26 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 29 04:08:26 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 29 04:08:26 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 29 04:08:26 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 29 04:08:26 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 29 04:08:26 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 29 04:08:26 node-2 kernel: [    0.000000] Zone ranges:
Jul 29 04:08:26 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 29 04:08:26 node-2 kernel: [    0.000000] Early memory node ranges
Jul 29 04:08:26 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 29 04:08:26 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 29 04:08:26 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 29 04:08:26 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 29 04:08:26 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 29 04:08:26 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 29 04:08:26 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 29 04:08:26 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 29 04:08:26 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 29 04:08:26 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 29 04:08:26 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 29 04:08:26 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 29 04:08:26 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 29 04:08:26 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 29 04:08:26 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 29 04:08:26 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 29 04:08:26 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 29 04:08:26 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 29 04:08:26 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 29 04:08:26 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 29 04:08:26 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 29 04:08:26 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 29 04:08:26 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 29 04:08:26 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 29 04:08:26 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 29 04:08:26 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 29 04:08:26 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=2412558c-77ba-4a40-8577-74ac4cd89780 nomdmonddf nomdmonisw
Jul 29 04:08:26 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 29 04:08:26 node-2 kernel: [    0.000000] Checking aperture...
Jul 29 04:08:26 node-2 kernel: [    0.000000] No AGP bridge found
Jul 29 04:08:26 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 29 04:08:26 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 29 04:08:26 node-2 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 29 04:08:26 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 29 04:08:26 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 29 04:08:26 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 29 04:08:26 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 29 04:08:26 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 29 04:08:26 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 29 04:08:26 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 29 04:08:26 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 29 04:08:26 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 29 04:08:26 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 29 04:08:26 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 29 04:08:26 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 29 04:08:26 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 29 04:08:26 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 29 04:08:26 node-2 kernel: [    0.004000] tsc: Detected 3491.887 MHz processor
Jul 29 04:08:26 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.77 BogoMIPS (lpj=13967548)
Jul 29 04:08:26 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 29 04:08:26 node-2 kernel: [    0.000043] Security Framework initialized
Jul 29 04:08:26 node-2 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 29 04:08:26 node-2 kernel: [    0.000062] Yama: becoming mindful.
Jul 29 04:08:26 node-2 kernel: [    0.001460] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.006401] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.008327] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.008354] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.008645] Initializing cgroup subsys memory
Jul 29 04:08:26 node-2 kernel: [    0.008653] Initializing cgroup subsys devices
Jul 29 04:08:26 node-2 kernel: [    0.008655] Initializing cgroup subsys freezer
Jul 29 04:08:26 node-2 kernel: [    0.008657] Initializing cgroup subsys blkio
Jul 29 04:08:26 node-2 kernel: [    0.008659] Initializing cgroup subsys perf_event
Jul 29 04:08:26 node-2 kernel: [    0.008661] Initializing cgroup subsys hugetlb
Jul 29 04:08:26 node-2 kernel: [    0.008680] CPU: Physical Processor ID: 0
Jul 29 04:08:26 node-2 kernel: [    0.008681] CPU: Processor Core ID: 0
Jul 29 04:08:26 node-2 kernel: [    0.008685] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 29 04:08:26 node-2 kernel: [    0.008685] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 29 04:08:26 node-2 kernel: [    0.009379] mce: CPU supports 22 MCE banks
Jul 29 04:08:26 node-2 kernel: [    0.009407] CPU0: Thermal monitoring enabled (TM1)
Jul 29 04:08:26 node-2 kernel: [    0.009427] process: using mwait in idle threads
Jul 29 04:08:26 node-2 kernel: [    0.009430] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 29 04:08:26 node-2 kernel: [    0.009430] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 29 04:08:26 node-2 kernel: [    0.009430] tlb_flushall_shift: 6
Jul 29 04:08:26 node-2 kernel: [    0.009519] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 29 04:08:26 node-2 kernel: [    0.010245] ACPI: Core revision 20131115
Jul 29 04:08:26 node-2 kernel: [    0.022918] ACPI: All ACPI Tables successfully acquired
Jul 29 04:08:26 node-2 kernel: [    0.023082] ftrace: allocating 28617 entries in 112 pages
Jul 29 04:08:26 node-2 kernel: [    0.031881] dmar: Host address width 46
Jul 29 04:08:26 node-2 kernel: [    0.031883] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 29 04:08:26 node-2 kernel: [    0.031889] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 04:08:26 node-2 kernel: [    0.031891] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 29 04:08:26 node-2 kernel: [    0.031895] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 04:08:26 node-2 kernel: [    0.031897] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 29 04:08:26 node-2 kernel: [    0.031898] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 29 04:08:26 node-2 kernel: [    0.031899] dmar: ATSR flags: 0x0
Jul 29 04:08:26 node-2 kernel: [    0.031900] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 29 04:08:26 node-2 kernel: [    0.031901] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 29 04:08:26 node-2 kernel: [    0.032017] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 29 04:08:26 node-2 kernel: [    0.032018] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 04:08:26 node-2 kernel: [    0.032019] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 04:08:26 node-2 kernel: [    0.032020] HPET id 0 under DRHD base 0xc7ffc000
Jul 29 04:08:26 node-2 kernel: [    0.032021] Your BIOS is broken and requested that x2apic be disabled.
Jul 29 04:08:26 node-2 kernel: [    0.032021] This will slightly decrease performance.
Jul 29 04:08:26 node-2 kernel: [    0.032021] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 29 04:08:26 node-2 kernel: [    0.032454] Enabled IRQ remapping in xapic mode
Jul 29 04:08:26 node-2 kernel: [    0.032455] x2apic not enabled, IRQ remapping is in xapic mode
Jul 29 04:08:26 node-2 kernel: [    0.032459] Switched APIC routing to physical flat.
Jul 29 04:08:26 node-2 kernel: [    0.033085] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 29 04:08:26 node-2 kernel: [    0.072734] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 29 04:08:26 node-2 kernel: [    0.072739] TSC deadline timer enabled
Jul 29 04:08:26 node-2 kernel: [    0.072747] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 29 04:08:26 node-2 kernel: [    0.072753] ... version:                3
Jul 29 04:08:26 node-2 kernel: [    0.072754] ... bit width:              48
Jul 29 04:08:26 node-2 kernel: [    0.072755] ... generic registers:      4
Jul 29 04:08:26 node-2 kernel: [    0.072756] ... value mask:             0000ffffffffffff
Jul 29 04:08:26 node-2 kernel: [    0.072757] ... max period:             0000ffffffffffff
Jul 29 04:08:26 node-2 kernel: [    0.072758] ... fixed-purpose events:   3
Jul 29 04:08:26 node-2 kernel: [    0.072759] ... event mask:             000000070000000f
Jul 29 04:08:26 node-2 kernel: [    0.074187] x86: Booting SMP configuration:
Jul 29 04:08:26 node-2 kernel: [    0.088292] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 29 04:08:26 node-2 kernel: [    0.074189] .... node  #0, CPUs:        #1  #2  #3
Jul 29 04:08:26 node-2 kernel: [    0.116203] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 29 04:08:26 node-2 kernel: [    0.270145] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 29 04:08:26 node-2 kernel: [    0.325753] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 29 04:08:26 node-2 kernel: [    0.382436] x86: Booted up 2 nodes, 16 CPUs
Jul 29 04:08:26 node-2 kernel: [    0.382439] smpboot: Total of 16 processors activated (111753.03 BogoMIPS)
Jul 29 04:08:26 node-2 kernel: [    0.405100] devtmpfs: initialized
Jul 29 04:08:26 node-2 kernel: [    0.408208] EVM: security.selinux
Jul 29 04:08:26 node-2 kernel: [    0.408210] EVM: security.SMACK64
Jul 29 04:08:26 node-2 kernel: [    0.408211] EVM: security.ima
Jul 29 04:08:26 node-2 kernel: [    0.408212] EVM: security.capability
Jul 29 04:08:26 node-2 kernel: [    0.408262] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.408933] pinctrl core: initialized pinctrl subsystem
Jul 29 04:08:26 node-2 kernel: [    0.408995] regulator-dummy: no parameters
Jul 29 04:08:26 node-2 kernel: [    0.409026] RTC time:  4:07:48, date: 07/29/16
Jul 29 04:08:26 node-2 kernel: [    0.409059] NET: Registered protocol family 16
Jul 29 04:08:26 node-2 kernel: [    0.409143] cpuidle: using governor ladder
Jul 29 04:08:26 node-2 kernel: [    0.409144] cpuidle: using governor menu
Jul 29 04:08:26 node-2 kernel: [    0.409177] ACPI: bus type PCI registered
Jul 29 04:08:26 node-2 kernel: [    0.409179] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 29 04:08:26 node-2 kernel: [    0.409225] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 29 04:08:26 node-2 kernel: [    0.409228] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 29 04:08:26 node-2 kernel: [    0.422961] PCI: Using configuration type 1 for base access
Jul 29 04:08:26 node-2 kernel: [    0.423957] bio: create slab <bio-0> at 0
Jul 29 04:08:26 node-2 kernel: [    0.424235] ACPI: Added _OSI(Module Device)
Jul 29 04:08:26 node-2 kernel: [    0.424237] ACPI: Added _OSI(Processor Device)
Jul 29 04:08:26 node-2 kernel: [    0.424238] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 29 04:08:26 node-2 kernel: [    0.424239] ACPI: Added _OSI(Processor Aggregator Device)
Jul 29 04:08:26 node-2 kernel: [    0.436905] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 29 04:08:26 node-2 kernel: [    0.447358] ACPI: Interpreter enabled
Jul 29 04:08:26 node-2 kernel: [    0.447363] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 29 04:08:26 node-2 kernel: [    0.447367] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 29 04:08:26 node-2 kernel: [    0.447370] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 29 04:08:26 node-2 kernel: [    0.447377] ACPI: (supports S0 S4 S5)
Jul 29 04:08:26 node-2 kernel: [    0.447378] ACPI: Using IOAPIC for interrupt routing
Jul 29 04:08:26 node-2 kernel: [    0.447419] HEST: Table parsing has been initialized.
Jul 29 04:08:26 node-2 kernel: [    0.447422] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 29 04:08:26 node-2 kernel: [    0.447972] ACPI: No dock devices found.
Jul 29 04:08:26 node-2 kernel: [    0.459530] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 29 04:08:26 node-2 kernel: [    0.459535] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:26 node-2 kernel: [    0.459539] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 04:08:26 node-2 kernel: [    0.459565] PCI host bridge to bus 0000:ff
Jul 29 04:08:26 node-2 kernel: [    0.459567] pci_bus 0000:ff: root bus resource [bus ff]
Jul 29 04:08:26 node-2 kernel: [    0.459575] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459612] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.459643] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459677] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459705] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.459733] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.459763] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459791] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459821] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459849] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459875] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459900] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459928] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459957] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.459983] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460011] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460039] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460066] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460092] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.460119] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460145] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.460170] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460196] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460225] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.460258] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460288] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460318] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460348] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460378] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460408] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460438] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460468] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460497] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460528] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460558] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460589] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460622] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460650] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460677] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460707] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460739] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460776] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460810] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460842] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460870] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460899] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460930] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460959] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.460990] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461020] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461051] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461079] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461106] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461135] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461163] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461194] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461224] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461281] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 29 04:08:26 node-2 kernel: [    0.461283] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:26 node-2 kernel: [    0.461286] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 04:08:26 node-2 kernel: [    0.461304] PCI host bridge to bus 0000:7f
Jul 29 04:08:26 node-2 kernel: [    0.461305] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 29 04:08:26 node-2 kernel: [    0.461310] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461337] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.461364] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461394] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461415] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.461440] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.461465] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461490] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461512] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461535] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461557] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461579] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461603] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461624] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461648] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461673] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461698] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461723] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461746] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.461770] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461793] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.461816] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461842] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461867] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 04:08:26 node-2 kernel: [    0.461900] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461926] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461952] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.461977] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462002] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462028] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462054] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462081] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462105] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462132] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462160] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462187] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462215] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462241] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462266] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462293] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462318] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462344] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462373] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462401] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462427] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462452] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462478] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462507] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462534] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462561] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462594] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462619] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462642] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462668] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462694] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462723] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.462749] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.463989] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 29 04:08:26 node-2 kernel: [    0.463993] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:26 node-2 kernel: [    0.465107] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 04:08:26 node-2 kernel: [    0.465614] PCI host bridge to bus 0000:00
Jul 29 04:08:26 node-2 kernel: [    0.465616] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 29 04:08:26 node-2 kernel: [    0.465617] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 29 04:08:26 node-2 kernel: [    0.465619] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 29 04:08:26 node-2 kernel: [    0.465620] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 29 04:08:26 node-2 kernel: [    0.465621] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 29 04:08:26 node-2 kernel: [    0.465623] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 29 04:08:26 node-2 kernel: [    0.465624] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 29 04:08:26 node-2 kernel: [    0.465630] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 29 04:08:26 node-2 kernel: [    0.465716] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.465746] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.465788] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 29 04:08:26 node-2 kernel: [    0.465807] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.465837] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.465877] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 29 04:08:26 node-2 kernel: [    0.465897] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.465927] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.465967] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 29 04:08:26 node-2 kernel: [    0.465984] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.466054] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.466132] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.466210] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 04:08:26 node-2 kernel: [    0.466215] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 29 04:08:26 node-2 kernel: [    0.466299] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 29 04:08:26 node-2 kernel: [    0.466446] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 29 04:08:26 node-2 kernel: [    0.466464] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 29 04:08:26 node-2 kernel: [    0.466542] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.466597] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 29 04:08:26 node-2 kernel: [    0.466619] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.466674] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.466718] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 29 04:08:26 node-2 kernel: [    0.466746] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.466802] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.466845] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 29 04:08:26 node-2 kernel: [    0.466870] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 29 04:08:26 node-2 kernel: [    0.466887] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 29 04:08:26 node-2 kernel: [    0.466965] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.467015] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 29 04:08:26 node-2 kernel: [    0.467041] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 29 04:08:26 node-2 kernel: [    0.467289] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 29 04:08:26 node-2 kernel: [    0.467295] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 29 04:08:26 node-2 kernel: [    0.467301] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.467307] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.467314] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 29 04:08:26 node-2 kernel: [    0.467344] pci 0000:01:00.0: supports D1 D2
Jul 29 04:08:26 node-2 kernel: [    0.473703] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 04:08:26 node-2 kernel: [    0.473709] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 04:08:26 node-2 kernel: [    0.473714] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:26 node-2 kernel: [    0.473975] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.474035] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 29 04:08:26 node-2 kernel: [    0.481699] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 04:08:26 node-2 kernel: [    0.481706] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.481710] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:26 node-2 kernel: [    0.481793] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.481861] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.481937] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.481982] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 04:08:26 node-2 kernel: [    0.481986] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.481988] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:26 node-2 kernel: [    0.482040] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.482167] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.482220] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 04:08:26 node-2 kernel: [    0.482223] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.482225] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.482274] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.482393] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.482435] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.482556] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.482595] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.482734] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.482773] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:26 node-2 kernel: [    0.482892] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:26 node-2 kernel: [    0.482933] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 04:08:26 node-2 kernel: [    0.482936] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.482938] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.482997] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:26 node-2 kernel: [    0.483061] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.483113] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.483154] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 29 04:08:26 node-2 kernel: [    0.483236] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 29 04:08:26 node-2 kernel: [    0.483342] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 04:08:26 node-2 kernel: [    0.483345] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.483347] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.483402] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:26 node-2 kernel: [    0.483456] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.483504] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.483757] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 04:08:26 node-2 kernel: [    0.483761] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:26 node-2 kernel: [    0.483828] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:26 node-2 kernel: [    0.483888] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.483936] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.484152] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 04:08:26 node-2 kernel: [    0.484156] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:26 node-2 kernel: [    0.484221] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:26 node-2 kernel: [    0.484286] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.484337] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 29 04:08:26 node-2 kernel: [    0.484563] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 04:08:26 node-2 kernel: [    0.484567] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:26 node-2 kernel: [    0.484773] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 04:08:26 node-2 kernel: [    0.484811] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 04:08:26 node-2 kernel: [    0.484889] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 29 04:08:26 node-2 kernel: [    0.484908] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 29 04:08:26 node-2 kernel: [    0.484921] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 29 04:08:26 node-2 kernel: [    0.484935] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 29 04:08:26 node-2 kernel: [    0.484985] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 29 04:08:26 node-2 kernel: [    0.489706] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 04:08:26 node-2 kernel: [    0.489715] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:26 node-2 kernel: [    0.489767] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 29 04:08:26 node-2 kernel: [    0.490291] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 29 04:08:26 node-2 kernel: [    0.490294] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:26 node-2 kernel: [    0.490413] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 04:08:26 node-2 kernel: [    0.490521] PCI host bridge to bus 0000:80
Jul 29 04:08:26 node-2 kernel: [    0.490523] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 29 04:08:26 node-2 kernel: [    0.490524] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 29 04:08:26 node-2 kernel: [    0.490526] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 29 04:08:26 node-2 kernel: [    0.490534] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.490597] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.490665] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 04:08:26 node-2 kernel: [    0.490728] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 04:08:26 node-2 kernel: [    0.490733] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 29 04:08:26 node-2 kernel: [    0.490806] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 29 04:08:26 node-2 kernel: [    0.491102] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 29 04:08:26 node-2 kernel: [    0.491133] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 29 04:08:26 node-2 kernel: [    0.491163] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 29 04:08:26 node-2 kernel: [    0.491192] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 29 04:08:26 node-2 kernel: [    0.491221] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:26 node-2 kernel: [    0.491251] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:26 node-2 kernel: [    0.491281] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:26 node-2 kernel: [    0.491310] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:26 node-2 kernel: [    0.491396] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 29 04:08:26 node-2 kernel: [    0.491400] ACPI: \_SB_.UNC1: notify handler is installed
Jul 29 04:08:26 node-2 kernel: [    0.491401] ACPI: \_SB_.UNC0: notify handler is installed
Jul 29 04:08:26 node-2 kernel: [    0.491416] ACPI: \_SB_.PCI0: notify handler is installed
Jul 29 04:08:26 node-2 kernel: [    0.491469] ACPI: \_SB_.PCI1: notify handler is installed
Jul 29 04:08:26 node-2 kernel: [    0.491549] Found 4 acpi root devices
Jul 29 04:08:26 node-2 kernel: [    0.491658] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 29 04:08:26 node-2 kernel: [    0.491660] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 29 04:08:26 node-2 kernel: [    0.491662] vgaarb: loaded
Jul 29 04:08:26 node-2 kernel: [    0.491663] vgaarb: bridge control possible 0000:0c:00.0
Jul 29 04:08:26 node-2 kernel: [    0.491779] SCSI subsystem initialized
Jul 29 04:08:26 node-2 kernel: [    0.491842] libata version 3.00 loaded.
Jul 29 04:08:26 node-2 kernel: [    0.491858] ACPI: bus type USB registered
Jul 29 04:08:26 node-2 kernel: [    0.491868] usbcore: registered new interface driver usbfs
Jul 29 04:08:26 node-2 kernel: [    0.491873] usbcore: registered new interface driver hub
Jul 29 04:08:26 node-2 kernel: [    0.491897] usbcore: registered new device driver usb
Jul 29 04:08:26 node-2 kernel: [    0.492068] PCI: Using ACPI for IRQ routing
Jul 29 04:08:26 node-2 kernel: [    0.495680] PCI: pci_cache_line_size set to 64 bytes
Jul 29 04:08:26 node-2 kernel: [    0.495882] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 29 04:08:26 node-2 kernel: [    0.495883] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 29 04:08:26 node-2 kernel: [    0.495884] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 29 04:08:26 node-2 kernel: [    0.495952] NetLabel: Initializing
Jul 29 04:08:26 node-2 kernel: [    0.495953] NetLabel:  domain hash size = 128
Jul 29 04:08:26 node-2 kernel: [    0.495954] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 29 04:08:26 node-2 kernel: [    0.495964] NetLabel:  unlabeled traffic allowed by default
Jul 29 04:08:26 node-2 kernel: [    0.496020] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 29 04:08:26 node-2 kernel: [    0.496024] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 29 04:08:26 node-2 kernel: [    0.498093] Switched to clocksource hpet
Jul 29 04:08:26 node-2 kernel: [    0.502440] AppArmor: AppArmor Filesystem Enabled
Jul 29 04:08:26 node-2 kernel: [    0.502479] pnp: PnP ACPI init
Jul 29 04:08:26 node-2 kernel: [    0.502491] ACPI: bus type PNP registered
Jul 29 04:08:26 node-2 kernel: [    0.502670] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 29 04:08:26 node-2 kernel: [    0.502681] pnp 00:01: [dma 4]
Jul 29 04:08:26 node-2 kernel: [    0.502699] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 29 04:08:26 node-2 kernel: [    0.502734] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 29 04:08:26 node-2 kernel: [    0.502759] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 29 04:08:26 node-2 kernel: [    0.502779] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 29 04:08:26 node-2 kernel: [    0.502827] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 29 04:08:26 node-2 kernel: [    0.502939] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502942] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 29 04:08:26 node-2 kernel: [    0.502943] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502945] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502946] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502948] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502951] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 29 04:08:26 node-2 kernel: [    0.502953] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502954] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502956] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502957] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502959] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502960] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 29 04:08:26 node-2 kernel: [    0.502963] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 29 04:08:26 node-2 kernel: [    0.503064] pnp 00:07: [dma 0 disabled]
Jul 29 04:08:26 node-2 kernel: [    0.503097] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 04:08:26 node-2 kernel: [    0.503178] pnp 00:08: [dma 0 disabled]
Jul 29 04:08:26 node-2 kernel: [    0.503214] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 04:08:26 node-2 kernel: [    0.503272] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 29 04:08:26 node-2 kernel: [    0.503715] pnp: PnP ACPI: found 10 devices
Jul 29 04:08:26 node-2 kernel: [    0.503717] ACPI: bus type PNP unregistered
Jul 29 04:08:26 node-2 kernel: [    0.509734] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 04:08:26 node-2 kernel: [    0.509738] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 04:08:26 node-2 kernel: [    0.509740] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:26 node-2 kernel: [    0.509746] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 04:08:26 node-2 kernel: [    0.509748] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.509763] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.509792] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 04:08:26 node-2 kernel: [    0.509806] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:26 node-2 kernel: [    0.509835] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 04:08:26 node-2 kernel: [    0.509850] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:26 node-2 kernel: [    0.509879] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 04:08:26 node-2 kernel: [    0.509893] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:26 node-2 kernel: [    0.509922] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 04:08:26 node-2 kernel: [    0.509924] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.509939] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.509968] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 04:08:26 node-2 kernel: [    0.509970] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.509985] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510014] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 04:08:26 node-2 kernel: [    0.510015] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.510018] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510023] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 04:08:26 node-2 kernel: [    0.510025] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.510028] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510032] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 04:08:26 node-2 kernel: [    0.510038] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 04:08:26 node-2 kernel: [    0.510047] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 04:08:26 node-2 kernel: [    0.510050] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:26 node-2 kernel: [    0.510057] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 29 04:08:26 node-2 kernel: [    0.510058] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 29 04:08:26 node-2 kernel: [    0.510059] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 29 04:08:26 node-2 kernel: [    0.510060] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 29 04:08:26 node-2 kernel: [    0.510061] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 29 04:08:26 node-2 kernel: [    0.510062] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 29 04:08:26 node-2 kernel: [    0.510063] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 29 04:08:26 node-2 kernel: [    0.510064] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:26 node-2 kernel: [    0.510069] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.510070] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510071] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.510072] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510073] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.510074] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510075] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.510076] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510077] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:26 node-2 kernel: [    0.510078] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510079] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:26 node-2 kernel: [    0.510080] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:26 node-2 kernel: [    0.510081] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:26 node-2 kernel: [    0.510083] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:26 node-2 kernel: [    0.510085] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 29 04:08:26 node-2 kernel: [    0.510086] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 29 04:08:26 node-2 kernel: [    0.510128] NET: Registered protocol family 2
Jul 29 04:08:26 node-2 kernel: [    0.510433] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.510807] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.510976] TCP: Hash tables configured (established 262144 bind 65536)
Jul 29 04:08:26 node-2 kernel: [    0.511019] TCP: reno registered
Jul 29 04:08:26 node-2 kernel: [    0.511049] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.511157] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.511316] NET: Registered protocol family 1
Jul 29 04:08:26 node-2 kernel: [    0.546184] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 29 04:08:26 node-2 kernel: [    0.546198] PCI: CLS 64 bytes, default 64
Jul 29 04:08:26 node-2 kernel: [    0.546283] Trying to unpack rootfs image as initramfs...
Jul 29 04:08:26 node-2 kernel: [    0.767793] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 29 04:08:26 node-2 kernel: [    0.767849] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 29 04:08:26 node-2 kernel: [    0.767874] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 29 04:08:26 node-2 kernel: [    0.768252] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768258] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768265] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768271] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768279] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768288] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768303] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768309] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768317] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768324] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768330] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768336] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768342] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768349] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768356] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768362] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:26 node-2 kernel: [    0.768442] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 29 04:08:26 node-2 kernel: [    0.768445] Scanning for low memory corruption every 60 seconds
Jul 29 04:08:26 node-2 kernel: [    0.768763] Initialise system trusted keyring
Jul 29 04:08:26 node-2 kernel: [    0.768813] audit: initializing netlink socket (disabled)
Jul 29 04:08:26 node-2 kernel: [    0.768824] type=2000 audit(1469765267.720:1): initialized
Jul 29 04:08:26 node-2 kernel: [    0.786730] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 29 04:08:26 node-2 kernel: [    0.788190] zbud: loaded
Jul 29 04:08:26 node-2 kernel: [    0.788309] VFS: Disk quotas dquot_6.5.2
Jul 29 04:08:26 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 29 04:08:26 node-2 kernel: [    0.788345] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 29 04:08:26 node-2 kernel: [    0.788696] fuse init (API version 7.22)
Jul 29 04:08:26 node-2 kernel: [    0.788750] msgmni has been set to 32768
Jul 29 04:08:26 node-2 kernel: [    0.788798] Key type big_key registered
Jul 29 04:08:26 node-2 kernel: [    0.789299] Key type asymmetric registered
Jul 29 04:08:26 node-2 kernel: [    0.789301] Asymmetric key parser 'x509' registered
Jul 29 04:08:26 node-2 kernel: [    0.789324] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 29 04:08:26 node-2 kernel: [    0.789411] io scheduler noop registered
Jul 29 04:08:26 node-2 kernel: [    0.789412] io scheduler deadline registered (default)
Jul 29 04:08:26 node-2 kernel: [    0.789430] io scheduler cfq registered
Jul 29 04:08:26 node-2 kernel: [    0.789761] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    0.789901] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    0.790024] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    0.790136] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    0.790267] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    0.790359] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    0.790781] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 29 04:08:26 node-2 kernel: [    0.790821] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 29 04:08:26 node-2 kernel: [    0.790848] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 29 04:08:26 node-2 kernel: [    0.790871] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790876] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790882] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:26 node-2 kernel: [    0.790893] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790897] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790900] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790904] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790907] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790911] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790915] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790919] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790922] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790926] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790929] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790933] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790938] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:26 node-2 kernel: [    0.790957] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790963] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:26 node-2 kernel: [    0.790982] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.790988] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:26 node-2 kernel: [    0.791008] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.791012] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:26 node-2 kernel: [    0.791018] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 29 04:08:26 node-2 kernel: [    0.791065] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 29 04:08:26 node-2 kernel: [    0.791076] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 29 04:08:26 node-2 kernel: [    0.791086] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 29 04:08:26 node-2 kernel: [    0.791107] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 29 04:08:26 node-2 kernel: [    0.791185] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 29 04:08:26 node-2 kernel: [    0.791186] vesafb: scrolling: redraw
Jul 29 04:08:26 node-2 kernel: [    0.791188] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 29 04:08:26 node-2 kernel: [    0.811394] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 29 04:08:26 node-2 kernel: [    0.819967] Console: switching to colour frame buffer device 80x30
Jul 29 04:08:26 node-2 kernel: [    0.828730] fb0: VESA VGA frame buffer device
Jul 29 04:08:26 node-2 kernel: [    0.828958] intel_idle: MWAIT substates: 0x2120
Jul 29 04:08:26 node-2 kernel: [    0.828959] intel_idle: v0.4 model 0x3F
Jul 29 04:08:26 node-2 kernel: [    0.828960] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 29 04:08:26 node-2 kernel: [    0.829196] ipmi message handler version 39.2
Jul 29 04:08:26 node-2 kernel: [    0.829473] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 29 04:08:26 node-2 kernel: [    0.829921] ACPI: AC Adapter [P111] (on-line)
Jul 29 04:08:26 node-2 kernel: [    0.835186] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 29 04:08:26 node-2 kernel: [    0.846255] ACPI: Power Button [PWRB]
Jul 29 04:08:26 node-2 kernel: [    0.852044] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 29 04:08:26 node-2 kernel: [    0.863780] ACPI: Power Button [PWRF]
Jul 29 04:08:26 node-2 kernel: [    0.891643] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 29 04:08:26 node-2 kernel: [    0.903332] pstore: Registered erst as persistent store backend
Jul 29 04:08:26 node-2 kernel: [    0.909550] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 29 04:08:26 node-2 kernel: [    0.921522] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 29 04:08:26 node-2 kernel: [    0.948271] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 29 04:08:26 node-2 kernel: [    0.981564] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 29 04:08:26 node-2 kernel: [    0.995602] Linux agpgart interface v0.103
Jul 29 04:08:26 node-2 kernel: [    1.003245] brd: module loaded
Jul 29 04:08:26 node-2 kernel: [    1.010288] loop: module loaded
Jul 29 04:08:26 node-2 kernel: [    1.017004] libphy: Fixed MDIO Bus: probed
Jul 29 04:08:26 node-2 kernel: [    1.023477] tun: Universal TUN/TAP device driver, 1.6
Jul 29 04:08:26 node-2 kernel: [    1.029960] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 29 04:08:26 node-2 kernel: [    1.036481] PPP generic driver version 2.4.2
Jul 29 04:08:26 node-2 kernel: [    1.042888] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 29 04:08:26 node-2 kernel: [    1.049334] ehci-pci: EHCI PCI platform driver
Jul 29 04:08:26 node-2 kernel: [    1.055853] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 29 04:08:26 node-2 kernel: [    1.062275] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 29 04:08:26 node-2 kernel: [    1.074826] ehci-pci 0000:00:1a.0: debug port 2
Jul 29 04:08:26 node-2 kernel: [    1.085043] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 29 04:08:26 node-2 kernel: [    1.085062] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 29 04:08:26 node-2 kernel: [    1.101573] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 29 04:08:26 node-2 kernel: [    1.107662] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 04:08:26 node-2 kernel: [    1.113847] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 04:08:26 node-2 kernel: [    1.125747] usb usb1: Product: EHCI Host Controller
Jul 29 04:08:26 node-2 kernel: [    1.131780] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 04:08:26 node-2 kernel: [    1.137830] usb usb1: SerialNumber: 0000:00:1a.0
Jul 29 04:08:26 node-2 kernel: [    1.143781] hub 1-0:1.0: USB hub found
Jul 29 04:08:26 node-2 kernel: [    1.149562] hub 1-0:1.0: 2 ports detected
Jul 29 04:08:26 node-2 kernel: [    1.155373] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 29 04:08:26 node-2 kernel: [    1.160964] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 29 04:08:26 node-2 kernel: [    1.171880] ehci-pci 0000:00:1d.0: debug port 2
Jul 29 04:08:26 node-2 kernel: [    1.181178] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 29 04:08:26 node-2 kernel: [    1.181181] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 29 04:08:26 node-2 kernel: [    1.197491] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 29 04:08:26 node-2 kernel: [    1.202692] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 04:08:26 node-2 kernel: [    1.208004] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 04:08:26 node-2 kernel: [    1.218610] usb usb2: Product: EHCI Host Controller
Jul 29 04:08:26 node-2 kernel: [    1.224084] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 04:08:26 node-2 kernel: [    1.229660] usb usb2: SerialNumber: 0000:00:1d.0
Jul 29 04:08:26 node-2 kernel: [    1.235188] hub 2-0:1.0: USB hub found
Jul 29 04:08:26 node-2 kernel: [    1.240551] hub 2-0:1.0: 2 ports detected
Jul 29 04:08:26 node-2 kernel: [    1.245872] ehci-platform: EHCI generic platform driver
Jul 29 04:08:26 node-2 kernel: [    1.251129] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 29 04:08:26 node-2 kernel: [    1.256457] ohci-pci: OHCI PCI platform driver
Jul 29 04:08:26 node-2 kernel: [    1.261757] ohci-platform: OHCI generic platform driver
Jul 29 04:08:26 node-2 kernel: [    1.266946] uhci_hcd: USB Universal Host Controller Interface driver
Jul 29 04:08:26 node-2 kernel: [    1.272304] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 29 04:08:26 node-2 kernel: [    1.465269] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 29 04:08:26 node-2 kernel: [    1.621476] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 29 04:08:26 node-2 kernel: [    1.626988] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 04:08:26 node-2 kernel: [    1.632744] hub 1-1:1.0: USB hub found
Jul 29 04:08:26 node-2 kernel: [    1.638213] hub 1-1:1.0: 6 ports detected
Jul 29 04:08:26 node-2 kernel: [    1.753018] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 29 04:08:26 node-2 kernel: [    1.765009] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 29 04:08:26 node-2 kernel: [    2.021137] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 29 04:08:26 node-2 kernel: [    2.026690] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 04:08:26 node-2 kernel: [    2.032529] hub 2-1:1.0: USB hub found
Jul 29 04:08:26 node-2 kernel: [    2.038248] hub 2-1:1.0: 8 ports detected
Jul 29 04:08:26 node-2 kernel: [    2.313735] i8042: No controller found
Jul 29 04:08:26 node-2 kernel: [    2.319157] mousedev: PS/2 mouse device common for all mice
Jul 29 04:08:26 node-2 kernel: [    2.320584] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 29 04:08:26 node-2 kernel: [    2.330266] rtc_cmos 00:02: RTC can wake from S4
Jul 29 04:08:26 node-2 kernel: [    2.336022] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 29 04:08:26 node-2 kernel: [    2.341634] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 29 04:08:26 node-2 kernel: [    2.352716] device-mapper: uevent: version 1.0.3
Jul 29 04:08:26 node-2 kernel: [    2.358373] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 29 04:08:26 node-2 kernel: [    2.369599] ledtrig-cpu: registered to indicate activity on CPUs
Jul 29 04:08:26 node-2 kernel: [    2.375513] TCP: cubic registered
Jul 29 04:08:26 node-2 kernel: [    2.381407] NET: Registered protocol family 10
Jul 29 04:08:26 node-2 kernel: [    2.387392] NET: Registered protocol family 17
Jul 29 04:08:26 node-2 kernel: [    2.393067] Key type dns_resolver registered
Jul 29 04:08:26 node-2 kernel: [    2.399035] Loading compiled-in X.509 certificates
Jul 29 04:08:26 node-2 kernel: [    2.405195] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 29 04:08:26 node-2 kernel: [    2.416593] registered taskstats version 1
Jul 29 04:08:26 node-2 kernel: [    2.424510] Key type trusted registered
Jul 29 04:08:26 node-2 kernel: [    2.432066] Key type encrypted registered
Jul 29 04:08:26 node-2 kernel: [    2.437527] AppArmor: AppArmor sha1 policy hashing enabled
Jul 29 04:08:26 node-2 kernel: [    2.443033] IMA: No TPM chip found, activating TPM-bypass!
Jul 29 04:08:26 node-2 kernel: [    2.449198] regulator-dummy: disabling
Jul 29 04:08:26 node-2 kernel: [    2.452842] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 29 04:08:26 node-2 kernel: [    2.452843] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 04:08:26 node-2 kernel: [    2.452843] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 29 04:08:26 node-2 kernel: [    2.452844] usb 2-1.4: Manufacturer: Avocent
Jul 29 04:08:26 node-2 kernel: [    2.452845] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 29 04:08:26 node-2 kernel: [    2.488234]   Magic number: 8:671:111
Jul 29 04:08:26 node-2 kernel: [    2.494122] rtc_cmos 00:02: setting system clock to 2016-07-29 04:07:50 UTC (1469765270)
Jul 29 04:08:26 node-2 kernel: [    2.506740] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 29 04:08:26 node-2 kernel: [    2.512605] EDD information not available.
Jul 29 04:08:26 node-2 kernel: [    2.518448] PM: Hibernation image not present or could not be loaded.
Jul 29 04:08:26 node-2 kernel: [    2.519316] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 29 04:08:26 node-2 kernel: [    2.530790] Write protecting the kernel read-only data: 12288k
Jul 29 04:08:26 node-2 kernel: [    2.537136] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 29 04:08:26 node-2 kernel: [    2.549779] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 29 04:08:26 node-2 kernel: [    2.581885] device-mapper: multipath: version 1.6.0 loaded
Jul 29 04:08:26 node-2 kernel: [    2.590134] systemd-udevd[218]: starting version 204
Jul 29 04:08:26 node-2 kernel: [    2.615293] md: linear personality registered for level -1
Jul 29 04:08:26 node-2 kernel: [    2.629511] md: multipath personality registered for level -4
Jul 29 04:08:26 node-2 kernel: [    2.637649] md: raid0 personality registered for level 0
Jul 29 04:08:26 node-2 kernel: [    2.645939] md: raid1 personality registered for level 1
Jul 29 04:08:26 node-2 kernel: [    2.655448] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 29 04:08:26 node-2 kernel: [    2.661887] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 29 04:08:26 node-2 kernel: [    2.668325] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 29 04:08:26 node-2 kernel: [    2.669261] megasas: FW now in Ready state
Jul 29 04:08:26 node-2 kernel: [    2.669430] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.669521] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.669596] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.669708] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.669816] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.669900] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670003] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670094] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670165] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670241] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670336] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670408] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670502] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670587] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670665] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.670759] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.671262] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 29 04:08:26 node-2 kernel: [    2.693851] hidraw: raw HID events driver (C) Jiri Kosina
Jul 29 04:08:26 node-2 kernel: [    2.702344] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 29 04:08:26 node-2 kernel: [    2.715466] 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 29 04:08:26 node-2 kernel: [    2.720400] raid6: sse2x1    1274 MB/s
Jul 29 04:08:26 node-2 kernel: [    2.735895] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:26 node-2 kernel: [    2.742754] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.742758] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.742765] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.742769] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.742808] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:26 node-2 kernel: [    2.756484] usbcore: registered new interface driver usbhid
Jul 29 04:08:26 node-2 kernel: [    2.763045] usbhid: USB HID core driver
Jul 29 04:08:26 node-2 kernel: [    2.765764] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 29 04:08:26 node-2 kernel: [    2.765766] 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 29 04:08:26 node-2 kernel: [    2.765767] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:26 node-2 kernel: [    2.788374] raid6: sse2x2    5193 MB/s
Jul 29 04:08:26 node-2 kernel: [    2.856105] raid6: sse2x4    9947 MB/s
Jul 29 04:08:26 node-2 kernel: [    2.928034] raid6: avx2x1   14939 MB/s
Jul 29 04:08:26 node-2 kernel: [    2.999977] raid6: avx2x2   18903 MB/s
Jul 29 04:08:26 node-2 kernel: [    3.071912] raid6: avx2x4   21179 MB/s
Jul 29 04:08:26 node-2 kernel: [    3.077773] raid6: using algorithm avx2x4 (21179 MB/s)
Jul 29 04:08:26 node-2 kernel: [    3.083665] raid6: using avx2x2 recovery algorithm
Jul 29 04:08:26 node-2 kernel: [    3.089638] megasas:IOC Init cmd success
Jul 29 04:08:26 node-2 kernel: [    3.089642] Switched to clocksource tsc
Jul 29 04:08:26 node-2 kernel: [    3.089703] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.089742] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.089779] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.089798] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.089892] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.097615] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 29 04:08:26 node-2 kernel: [    3.097617] 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 29 04:08:26 node-2 kernel: [    3.097619] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:26 node-2 kernel: [    3.097689] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.097729] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.097766] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.097783] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.097872] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.107389] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 29 04:08:26 node-2 kernel: [    3.107390] 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 29 04:08:26 node-2 kernel: [    3.107391] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:26 node-2 kernel: [    3.107446] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.107482] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.107518] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.107556] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.107643] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:26 node-2 kernel: [    3.119725] megasas: INIT adapter done
Jul 29 04:08:26 node-2 kernel: [    3.202253] xor: automatically using best checksumming function:
Jul 29 04:08:26 node-2 kernel: [    3.208252] 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 29 04:08:26 node-2 kernel: [    3.211797] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 29 04:08:26 node-2 kernel: [    3.212192] scsi0 : LSI SAS based MegaRAID driver
Jul 29 04:08:26 node-2 kernel: [    3.219452] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 04:08:26 node-2 kernel: [    3.230366] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 04:08:26 node-2 kernel: [    3.234584] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 29 04:08:26 node-2 kernel: [    3.234815] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 29 04:08:26 node-2 kernel: [    3.235122] sd 0:2:0:0: [sda] Write Protect is off
Jul 29 04:08:26 node-2 kernel: [    3.235123] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 29 04:08:26 node-2 kernel: [    3.235200] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 29 04:08:26 node-2 kernel: [    3.247915]    avx       : 37846.000 MB/sec
Jul 29 04:08:26 node-2 kernel: [    3.263875]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 29 04:08:26 node-2 kernel: [    3.265157] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 29 04:08:26 node-2 kernel: [    3.316609] 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 29 04:08:26 node-2 kernel: [    3.329858] async_tx: api initialized (async)
Jul 29 04:08:26 node-2 kernel: [    3.329901] 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 29 04:08:26 node-2 kernel: [    3.329954] 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 29 04:08:26 node-2 kernel: [    3.330005] 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 29 04:08:26 node-2 kernel: [    3.330142] 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 29 04:08:26 node-2 kernel: [    3.394971] md: raid6 personality registered for level 6
Jul 29 04:08:26 node-2 kernel: [    3.402124] md: raid5 personality registered for level 5
Jul 29 04:08:26 node-2 kernel: [    3.409069] md: raid4 personality registered for level 4
Jul 29 04:08:26 node-2 kernel: [    3.418936] md: raid10 personality registered for level 10
Jul 29 04:08:26 node-2 kernel: [    3.452887] random: lvm urandom read with 27 bits of entropy available
Jul 29 04:08:26 node-2 kernel: [    3.480883] multipathd (367): /proc/367/oom_adj is deprecated, please use /proc/367/oom_score_adj instead.
Jul 29 04:08:26 node-2 kernel: [    3.614040] bio: create slab <bio-1> at 1
Jul 29 04:08:26 node-2 kernel: [    4.504108] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:26 node-2 kernel: [    5.077367] init: plymouth-upstart-bridge main process (575) terminated with status 1
Jul 29 04:08:26 node-2 kernel: [    5.090187] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 04:08:26 node-2 kernel: [    5.103730] random: nonblocking pool is initialized
Jul 29 04:08:26 node-2 kernel: [    5.247837] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 29 04:08:26 node-2 kernel: [    5.297263] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 29 04:08:26 node-2 kernel: [    5.423585] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:26 node-2 kernel: [    5.501412] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:26 node-2 kernel: [    5.571034] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:26 node-2 kernel: [    5.723316] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 29 04:08:26 node-2 kernel: [    5.768274] XFS (dm-1): Mounting Filesystem
Jul 29 04:08:26 node-2 kernel: [    6.075396] XFS (dm-1): Ending clean mount
Jul 29 04:08:26 node-2 kernel: [    6.115950] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:26 node-2 kernel: [    6.155610] XFS (dm-2): Mounting Filesystem
Jul 29 04:08:26 node-2 kernel: [    6.237811] XFS (dm-2): Ending clean mount
Jul 29 04:08:26 node-2 kernel: [    6.322788] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:26 node-2 kernel: [    8.240751] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:26 node-2 kernel: [    8.265042] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:26 node-2 kernel: [    8.425097] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 29 04:08:26 node-2 kernel: [    8.425103] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 29 04:08:26 node-2 kernel: [    8.425107] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 29 04:08:26 node-2 kernel: [    8.425111] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 29 04:08:26 node-2 kernel: [    8.473683] systemd-udevd[804]: starting version 204
Jul 29 04:08:26 node-2 kernel: [    8.702811] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 29 04:08:26 node-2 kernel: [    8.702817] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 04:08:26 node-2 kernel: [    8.702820] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 29 04:08:26 node-2 kernel: [    8.702822] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 04:08:26 node-2 kernel: [    8.702866] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 29 04:08:26 node-2 kernel: [    8.705546] power_meter ACPI000D:00: Found ACPI power meter.
Jul 29 04:08:26 node-2 kernel: [    8.705566] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 29 04:08:26 node-2 kernel: [    8.712525] IPMI System Interface driver.
Jul 29 04:08:26 node-2 kernel: [    8.712591] ipmi_si: probing via ACPI
Jul 29 04:08:26 node-2 kernel: [    8.712615] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 29 04:08:26 node-2 kernel: [    8.712616] ipmi_si: Adding ACPI-specified kcs state machine
Jul 29 04:08:26 node-2 kernel: [    8.712632] ipmi_si: probing via SMBIOS
Jul 29 04:08:26 node-2 kernel: [    8.712634] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 04:08:26 node-2 kernel: [    8.712635] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 29 04:08:26 node-2 kernel: [    8.712637] ipmi_si: probing via SPMI
Jul 29 04:08:26 node-2 kernel: [    8.712638] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 04:08:26 node-2 kernel: [    8.712639] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 29 04:08:26 node-2 kernel: [    8.712641] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 29 04:08:26 node-2 kernel: [    8.713821] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 29 04:08:26 node-2 kernel: [    8.763968] wmi: Mapper loaded
Jul 29 04:08:26 node-2 kernel: [    8.779532] systemd-udevd[843]: renamed network interface eth3 to enp9s0
Jul 29 04:08:26 node-2 kernel: [    8.799409] systemd-udevd[842]: renamed network interface eth2 to enp8s0
Jul 29 04:08:26 node-2 kernel: [    8.819479] systemd-udevd[835]: renamed network interface eth1 to enp7s0
Jul 29 04:08:26 node-2 kernel: [    8.855360] systemd-udevd[824]: renamed network interface eth0 to enp6s0
Jul 29 04:08:26 node-2 kernel: [    8.856958] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 29 04:08:26 node-2 kernel: [    8.856964] ipmi_si 00:09: IPMI kcs interface initialized
Jul 29 04:08:26 node-2 kernel: [    9.180020] type=1400 audit(1469765277.186:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1084 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.180170] type=1400 audit(1469765277.186:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1084 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.180296] type=1400 audit(1469765277.186:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1084 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.180597] type=1400 audit(1469765277.186:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1083 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.180756] type=1400 audit(1469765277.186:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1083 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.180879] type=1400 audit(1469765277.186:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1083 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.188054] type=1400 audit(1469765277.194:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1086 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.188195] type=1400 audit(1469765277.194:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1086 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.188316] type=1400 audit(1469765277.194:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1086 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.242002] type=1400 audit(1469765277.246:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1085 comm="apparmor_parser"
Jul 29 04:08:26 node-2 kernel: [    9.632970] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:26 node-2 kernel: [    9.658388] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:26 node-2 kernel: [    9.933331] enic 0000:06:00.0 enp6s0: Link UP
Jul 29 04:08:26 node-2 kernel: [    9.934463] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 29 04:08:26 node-2 kernel: [    9.934477] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 29 04:08:26 node-2 kernel: [   20.201185] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 04:08:27 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 29 04:08:27 node-2 kernel: [   39.731377] init: failsafe main process (8436) killed by TERM signal
Jul 29 04:08:27 node-2 dbus[8504]: [system] AppArmor D-Bus mediation is enabled
Jul 29 04:08:27 node-2 kernel: [   39.987842] audit_printk_skb: 30 callbacks suppressed
Jul 29 04:08:27 node-2 kernel: [   39.987842] type=1400 audit(1469765307.471:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8564 comm="apparmor_parser"
Jul 29 04:08:27 node-2 kernel: [   39.987846] type=1400 audit(1469765307.471:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8564 comm="apparmor_parser"
Jul 29 04:08:27 node-2 kernel: [   39.987849] type=1400 audit(1469765307.471:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8564 comm="apparmor_parser"
Jul 29 04:08:27 node-2 kernel: [   39.988071] type=1400 audit(1469765307.471:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8564 comm="apparmor_parser"
Jul 29 04:08:27 node-2 kernel: [   39.988073] type=1400 audit(1469765307.471:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8564 comm="apparmor_parser"
Jul 29 04:08:27 node-2 kernel: [   39.988189] type=1400 audit(1469765307.471:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8564 comm="apparmor_parser"
Jul 29 04:08:27 node-2 kernel: [   39.991228] type=1400 audit(1469765307.475:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8565 comm="apparmor_parser"
Jul 29 04:08:27 node-2 kernel: [   40.062169] type=1400 audit(1469765307.547:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8567 comm="apparmor_parser"
Jul 29 04:08:27 node-2 cron[8595]: (CRON) INFO (pidfile fd = 3)
Jul 29 04:08:27 node-2 anacron[8611]: Anacron 2.3 started on 2016-07-29
Jul 29 04:08:27 node-2 cron[8628]: (CRON) STARTUP (fork ok)
Jul 29 04:08:27 node-2 anacron[8611]: Will run job `cron.daily' in 5 min.
Jul 29 04:08:27 node-2 anacron[8611]: Will run job `cron.weekly' in 10 min.
Jul 29 04:08:27 node-2 anacron[8611]: Will run job `cron.monthly' in 15 min.
Jul 29 04:08:27 node-2 anacron[8611]: Jobs will be executed sequentially
Jul 29 04:08:27 node-2 cron[8628]: (CRON) INFO (Running @reboot jobs)
Jul 29 04:08:27 node-2 multipathd: path checkers start up
Jul 29 04:08:28 node-2 postfix/master[8774]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 29 04:08:32 node-2 puppet-agent[8958]: Reopening log files
Jul 29 04:08:32 node-2 puppet-agent[8958]: Could not request certificate: Connection refused - connect(2)
Jul 29 04:08:42 node-2 puppet-user[9037]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 29 04:08:42 node-2 puppet-user[9037]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 29 04:08:42 node-2 puppet-user[9037]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 29 04:08:42 node-2 puppet-user[9037]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 29 04:08:42 node-2 puppet-user[9037]: Finished catalog run in 0.56 seconds
Jul 29 04:08:44 node-2 multipathd: uevent trigger error
Jul 29 04:08:44 node-2 puppet-user[9467]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 04:08:44 node-2 puppet-user[9467]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Jul 29 04:08:44 node-2 puppet-user[9467]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 29 04:08:44 node-2 puppet-user[9467]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 29 04:08:44 node-2 puppet-user[9467]: (/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 29 04:08:44 node-2 puppet-user[9467]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 29 04:08:44 node-2 puppet-user[9467]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 29 04:08:44 node-2 puppet-user[9467]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 29 04:08:44 node-2 puppet-user[9467]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 29 04:08:44 node-2 puppet-user[9467]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 29 04:08:44 node-2 puppet-user[9467]: Finished catalog run in 0.09 seconds
Jul 29 04:08:46 node-2 puppet-user[9930]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 29 04:08:46 node-2 puppet-user[9930]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Jul 29 04:08:46 node-2 puppet-user[9930]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 29 04:08:46 node-2 puppet-user[9930]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 29 04:08:46 node-2 puppet-user[9930]: Finished catalog run in 0.03 seconds
Jul 29 04:08:48 node-2 puppet-user[10524]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 29 04:08:48 node-2 puppet-user[10524]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 29 04:08:48 node-2 puppet-user[10524]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 29 04:08:48 node-2 puppet-user[10524]: Finished catalog run in 0.04 seconds
Jul 29 04:08:49 node-2 puppet-user[10983]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 29 04:08:49 node-2 puppet-user[10983]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Jul 29 04:08:49 node-2 puppet-user[10983]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 29 04:08:50 node-2 puppet-user[10983]: (/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 29 04:08:50 node-2 puppet-user[10983]: Finished catalog run in 0.43 seconds
Jul 29 04:08:51 node-2 puppet-user[11459]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 29 04:08:51 node-2 puppet-user[11459]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Jul 29 04:08:51 node-2 puppet-user[11459]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 29 04:08:51 node-2 puppet-user[11459]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 29 04:08:51 node-2 puppet-user[11459]: (/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 29 04:08:52 node-2 puppet-user[11459]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 29 04:08:52 node-2 puppet-user[11459]: Finished catalog run in 0.27 seconds
Jul 29 04:08:53 node-2 puppet-user[11934]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 29 04:08:53 node-2 puppet-user[11934]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Jul 29 04:08:53 node-2 puppet-user[11934]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 29 04:08:53 node-2 kernel: [   65.988561] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 29 04:08:53 node-2 kernel: [   65.988610] 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 29 04:08:53 node-2 puppet-user[11934]: (/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 29 04:08:53 node-2 puppet-user[11934]: Finished catalog run in 0.08 seconds
Jul 29 04:08:55 node-2 puppet-user[12392]: (Scope(Class[main])) MODULAR: sync_time
Jul 29 04:08:55 node-2 puppet-user[12392]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 29 04:08:55 node-2 ntpdate[12814]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 29 04:09:01 node-2 ntpdate[12814]: adjust time server 10.20.0.2 offset 0.001161 sec
Jul 29 04:09:01 node-2 puppet-user[12392]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 29 04:09:01 node-2 puppet-user[12392]: Finished catalog run in 6.17 seconds
Jul 29 04:09:02 node-2 CRON[13152]: (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 29 04:09:07 node-2 puppet-user[13209]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 04:09:07 node-2 puppet-user[13209]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 29 04:09:07 node-2 puppet-user[13209]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 29 04:09:07 node-2 puppet-user[13209]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 29 04:09:07 node-2 puppet-user[13209]: Finished catalog run in 0.06 seconds
Jul 29 04:09:09 node-2 puppet-user[13664]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 29 04:09:10 node-2 puppet-user[13664]: Compiled catalog for node-2.domain.tld in environment production in 1.47 seconds
Jul 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:10 node-2 puppet-user[13664]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:10 node-2 puppet-user[13664]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 29 04:09:10 node-2 puppet-user[13664]: (/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 29 04:09:11 node-2 puppet-user[13664]: (/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 29 04:09:11 node-2 puppet-user[13664]: (/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 29 04:09:11 node-2 puppet-user[13664]: (/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 29 04:09:11 node-2 puppet-user[13664]: (/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 29 04:09:11 node-2 puppet-user[13664]: (/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 29 04:09:11 node-2 puppet-user[13664]: (/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 29 04:09:11 node-2 kernel: [   83.496080] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 04:09:11 node-2 puppet-agent[8958]: Could not run: SIGTERM
Jul 29 04:09:11 node-2 kernel: [   83.777038] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 04:09:11 node-2 ec2: 
Jul 29 04:09:11 node-2 ec2: #############################################################
Jul 29 04:09:11 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 29 04:09:11 node-2 ec2: 1024 49:c0:37:37:c4:29:e2:10:81:5a:af:d0:d6:2b:b5:f7  root@node-2.domain.tld (DSA)
Jul 29 04:09:11 node-2 ec2: 256 0a:ba:ac:aa:02:ee:07:b4:66:71:27:e7:67:63:12:46  root@node-2.domain.tld (ECDSA)
Jul 29 04:09:11 node-2 ec2: 256 61:a8:aa:bc:19:ac:b7:ef:56:53:72:69:d6:2e:47:f0  root@node-2.domain.tld (ED25519)
Jul 29 04:09:11 node-2 ec2: 2048 52:15:bd:82:57:4c:47:cc:ab:0d:cb:6a:38:e8:65:c5  root@node-2.domain.tld (RSA)
Jul 29 04:09:11 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 29 04:09:11 node-2 ec2: #############################################################
Jul 29 04:09:26 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:09:26 node-2 nailgun-agent: D, [2016-07-29T04:09:02.240748 #13155] DEBUG -- : Sleep for 24 seconds before sending request
Jul 29 04:09:26 node-2 nailgun-agent: I, [2016-07-29T04:09:26.255602 #13155]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 04:09:26 node-2 nailgun-agent: D, [2016-07-29T04:09:26.641495 #13155] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 29 04:09:28 node-2 puppet-user[13664]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 29 04:09:28 node-2 puppet-user[13664]: Finished catalog run in 17.50 seconds
Jul 29 04:09:29 node-2 puppet-user[15047]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 29 04:09:30 node-2 puppet-user[15047]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Jul 29 04:09:35 node-2 puppet-user[15047]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.864858 #13155] DEBUG -- : Trying to find block devices
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.865159 #13155] DEBUG -- : Found block device: sda
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.865258 #13155] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.865354 #13155] DEBUG -- : Trying to get list of physical devices
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.865790 #13155] DEBUG -- : Getting udev properties for device: sda
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.869926 #13155] 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 29 04:09:38 node-2 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21063", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.869996 #13155] DEBUG -- : Trying to find out if device sda is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.870108 #13155] DEBUG -- : Device sda removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.870152 #13155] DEBUG -- : Device sda seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.871330 #13155] DEBUG -- : Getting udev properties for device: dm-0
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.874650 #13155] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-rqHPEFZBlvQ3LU05l6iHQXsrQe6oYsdICY2B1EHAIcfEGjCKbiA1kPZePZTm86Y1 /dev/disk/by-uuid/aae42a81-d94e-4e44-8071-c4b7e60eee94 /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-rqHPEFZBlvQ3LU05l6iHQXsrQe6oYsdICY2B1EHAIcfEGjCKbiA1kPZePZTm86Y1", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"aae42a81-d94e-4e44-8071-c4b7e60eee94", "ID_FS_UUID_ENC"=>"aae42a81-d94e-4e44-8071-c4b7e60eee94", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"7
Jul 29 04:09:38 node-2 nailgun-agent: 0526", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.874779 #13155] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.874865 #13155] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.874906 #13155] DEBUG -- : Device dm-0 seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.874952 #13155] DEBUG -- : Getting udev properties for device: dm-1
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.878899 #13155] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-ghvCcKBI9yxk0jEM4mhb3TY6AZf4zMNICfxfFfiv9Pqu2khHp9IcWL4fRd5B01TK /dev/disk/by-uuid/061b8cc1-369b-4490-867b-5bc8e640df1f /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-ghvCcKBI9yxk0jEM4mhb3TY6AZf4zMNICfxfFfiv9Pqu2khHp9IcWL4fRd5B01TK", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"061b8cc1-369b-4490-867b-5bc8e640df1f", "ID_FS_UUID_ENC"=>"061b8cc1-369b-4490-867b-5bc8e640df1f", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96829", "nomdmonddf"=>"1", "nom
Jul 29 04:09:38 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.878973 #13155] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.879061 #13155] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.879098 #13155] DEBUG -- : Device dm-1 seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.879145 #13155] DEBUG -- : Getting udev properties for device: dm-2
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.883463 #13155] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-MfxKRs8wEyMLoP8quKdQ0pdl8rCEbwoUJFigJEuAlXG7caFow7gIEldfsYhITFQA /dev/disk/by-uuid/a101db25-3ecb-4949-809e-c4618c6c1707 /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-MfxKRs8wEyMLoP8quKdQ0pdl8rCEbwoUJFigJEuAlXG7caFow7gIEldfsYhITFQA", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a101db25-3ecb-4949-809e-c4618c6c1707", "ID_FS_UUID_ENC"=>"a101db25-3ecb-4949-809e-c4618c6c1707", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1
Jul 29 04:09:38 node-2 nailgun-agent: 6165", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.883544 #13155] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.883675 #13155] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.883715 #13155] DEBUG -- : Device dm-2 seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.883759 #13155] DEBUG -- : Getting udev properties for device: dm-3
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.887908 #13155] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-U9SMsXCQYQDrgt5RgPB36JRVTqcoX3WKdHiVhM8E4SzrE4fovfoD5yrHQifFif2s /dev/disk/by-uuid/90096397-7432-42d3-bd1d-c8c75fd82594 /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-U9SMsXCQYQDrgt5RgPB36JRVTqcoX3WKdHiVhM8E4SzrE4fovfoD5yrHQifFif2s", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"90096397-7432-42d3-bd1d-c8c75fd82594", "ID_FS_UUID_ENC"=>"90096397-7432-42d3-bd1d-c8c75fd82594", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28429", "nomdmon
Jul 29 04:09:38 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.887982 #13155] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.888118 #13155] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.888157 #13155] DEBUG -- : Device dm-3 seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.888203 #13155] DEBUG -- : Getting udev properties for device: dm-4
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.892164 #13155] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-WIUUOxlv7UbYaDBU55mIZljJN7KC9wW3OQg5TiLVxpqOD6MRPsClzyAZcGMfvxnP /dev/disk/by-uuid/edf89b9a-1a0c-4a27-a2b5-c12681412cfa /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-WIUUOxlv7UbYaDBU55mIZljJN7KC9wW3OQg5TiLVxpqOD6MRPsClzyAZcGMfvxnP", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"edf89b9a-1a0c-4a27-a2b5-c12681412cfa", "ID_FS_UUID_ENC"=>"edf89b9a-1a0c-4a27-a2b5-c12681412cfa", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36683", "nomdmonddf"=>"1",
Jul 29 04:09:38 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.892239 #13155] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.892326 #13155] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.892369 #13155] DEBUG -- : Device dm-4 seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.892457 #13155] DEBUG -- : Getting udev properties for device: dm-5
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.896400 #13155] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-uIw744uKASoQd1CSGry2cTt7ZieodsgCd8Erckz0S8GOZUTU9KW3lojw8CMGkdNP /dev/disk/by-uuid/2412558c-77ba-4a40-8577-74ac4cd89780 /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-uIw744uKASoQd1CSGry2cTt7ZieodsgCd8Erckz0S8GOZUTU9KW3lojw8CMGkdNP", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2412558c-77ba-4a40-8577-74ac4cd89780", "ID_FS_UUID_ENC"=>"2412558c-77ba-4a40-8577-74ac4cd89780", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37640", "nomdmonddf"=>"1", "nom
Jul 29 04:09:38 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.896474 #13155] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.896560 #13155] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.896662 #13155] DEBUG -- : Device dm-5 seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.896706 #13155] DEBUG -- : Getting udev properties for device: dm-6
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.900655 #13155] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-uIw744uKASoQd1CSGry2cTt7ZieodsgCmPOuZJh271VDWWCCaLetzuWnhcgoXrv8 /dev/disk/by-uuid/2032927c-2158-495c-af61-fce3ba2b2f30 /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-uIw744uKASoQd1CSGry2cTt7ZieodsgCmPOuZJh271VDWWCCaLetzuWnhcgoXrv8", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"2032927c-2158-495c-af61-fce3ba2b2f30", "ID_FS_UUID_ENC"=>"2032927c-2158-495c-af61-fce3ba2b2f30", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38172", "nomdmonddf"=>"1", "nomdmonisw
Jul 29 04:09:38 node-2 nailgun-agent: "=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.900756 #13155] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.900855 #13155] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.900898 #13155] DEBUG -- : Device dm-6 seems to be appropriate
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.900970 #13155] DEBUG -- : Getting udev properties for device: ram0
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.904675 #13155] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51752", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.904758 #13155] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.904880 #13155] DEBUG -- : Device ram0 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.904924 #13155] DEBUG -- : Getting udev properties for device: ram1
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.908397 #13155] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51764", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.908476 #13155] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.908543 #13155] DEBUG -- : Device ram1 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.908607 #13155] DEBUG -- : Getting udev properties for device: ram2
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.912081 #13155] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52074", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.912154 #13155] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.912245 #13155] DEBUG -- : Device ram2 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.912293 #13155] DEBUG -- : Getting udev properties for device: ram3
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.915707 #13155] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52084", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.915796 #13155] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.915884 #13155] DEBUG -- : Device ram3 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.915929 #13155] DEBUG -- : Getting udev properties for device: ram4
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.919268 #13155] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52094", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.919324 #13155] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.919406 #13155] DEBUG -- : Device ram4 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.919464 #13155] DEBUG -- : Getting udev properties for device: ram5
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.922892 #13155] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52106", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.922963 #13155] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.923059 #13155] DEBUG -- : Device ram5 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.923116 #13155] DEBUG -- : Getting udev properties for device: ram6
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.926649 #13155] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52117", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.926744 #13155] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.926870 #13155] DEBUG -- : Device ram6 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.926930 #13155] DEBUG -- : Getting udev properties for device: ram7
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.930469 #13155] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3052129", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.930541 #13155] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.930682 #13155] DEBUG -- : Device ram7 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.930738 #13155] DEBUG -- : Getting udev properties for device: ram8
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.934096 #13155] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52333", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.934187 #13155] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.934336 #13155] DEBUG -- : Device ram8 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.934391 #13155] DEBUG -- : Getting udev properties for device: ram9
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.937799 #13155] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52352", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.937871 #13155] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.937981 #13155] DEBUG -- : Device ram9 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.938073 #13155] DEBUG -- : Getting udev properties for device: loop0
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.941670 #13155] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51396", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.941761 #13155] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.941888 #13155] DEBUG -- : Device loop0 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.941977 #13155] DEBUG -- : Getting udev properties for device: loop1
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.954004 #13155] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51409", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.954044 #13155] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.954109 #13155] DEBUG -- : Device loop1 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.954142 #13155] DEBUG -- : Getting udev properties for device: loop2
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.957872 #13155] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51420", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.957911 #13155] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.957974 #13155] DEBUG -- : Device loop2 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.958006 #13155] DEBUG -- : Getting udev properties for device: loop3
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.961905 #13155] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51431", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.962038 #13155] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.962103 #13155] DEBUG -- : Device loop3 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.962137 #13155] DEBUG -- : Getting udev properties for device: loop4
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.965219 #13155] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51441", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.965290 #13155] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.965378 #13155] DEBUG -- : Device loop4 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.965587 #13155] DEBUG -- : Getting udev properties for device: loop5
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.968808 #13155] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51453", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.968878 #13155] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.968962 #13155] DEBUG -- : Device loop5 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.969017 #13155] DEBUG -- : Getting udev properties for device: loop6
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.972276 #13155] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51727", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.972334 #13155] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.972414 #13155] DEBUG -- : Device loop6 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.972466 #13155] DEBUG -- : Getting udev properties for device: loop7
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.977931 #13155] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51739", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.977999 #13155] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.978103 #13155] DEBUG -- : Device loop7 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.978156 #13155] DEBUG -- : Getting udev properties for device: ram10
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.981876 #13155] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51778", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.981944 #13155] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.982056 #13155] DEBUG -- : Device ram10 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.982112 #13155] DEBUG -- : Getting udev properties for device: ram11
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.985228 #13155] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52007", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.985326 #13155] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.985437 #13155] DEBUG -- : Device ram11 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.985491 #13155] DEBUG -- : Getting udev properties for device: ram12
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.990258 #13155] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52023", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.990394 #13155] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.990493 #13155] DEBUG -- : Device ram12 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.990549 #13155] DEBUG -- : Getting udev properties for device: ram13
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.995540 #13155] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52037", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.995610 #13155] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.995808 #13155] DEBUG -- : Device ram13 removable parameter: "0"
Jul 29 04:09:38 node-2 nailgun-agent: D, [2016-07-29T04:09:38.995864 #13155] DEBUG -- : Getting udev properties for device: ram14
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:38.999748 #13155] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52049", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:38.999821 #13155] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:38.999909 #13155] DEBUG -- : Device ram14 removable parameter: "0"
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.000038 #13155] DEBUG -- : Getting udev properties for device: ram15
Jul 29 04:09:39 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.002936 #13155] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52064", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003008 #13155] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003091 #13155] DEBUG -- : Device ram15 removable parameter: "0"
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003186 #13155] 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 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003304 #13155] DEBUG -- : Block device seems to be physical data storage: sda
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003390 #13155] DEBUG -- : Found block device: dm-0
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003430 #13155] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003465 #13155] DEBUG -- : Found block device: dm-1
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003495 #13155] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003521 #13155] DEBUG -- : Found block device: dm-2
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003551 #13155] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003581 #13155] DEBUG -- : Found block device: dm-3
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003610 #13155] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003635 #13155] DEBUG -- : Found block device: dm-4
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003735 #13155] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003762 #13155] DEBUG -- : Found block device: dm-5
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003790 #13155] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003814 #13155] DEBUG -- : Found block device: dm-6
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003839 #13155] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003863 #13155] DEBUG -- : Found block device: ram0
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003889 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003912 #13155] DEBUG -- : Found block device: ram1
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003938 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.003961 #13155] DEBUG -- : Found block device: ram2
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004058 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004084 #13155] DEBUG -- : Found block device: ram3
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004110 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004133 #13155] DEBUG -- : Found block device: ram4
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004158 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004181 #13155] DEBUG -- : Found block device: ram5
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004209 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004232 #13155] DEBUG -- : Found block device: ram6
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004264 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004288 #13155] DEBUG -- : Found block device: ram7
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004313 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004450 #13155] DEBUG -- : Found block device: ram8
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004477 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004501 #13155] DEBUG -- : Found block device: ram9
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004531 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004554 #13155] DEBUG -- : Found block device: loop0
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004580 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004602 #13155] DEBUG -- : Found block device: loop1
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004630 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004653 #13155] DEBUG -- : Found block device: loop2
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004776 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004801 #13155] DEBUG -- : Found block device: loop3
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004826 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004851 #13155] DEBUG -- : Found block device: loop4
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004876 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004900 #13155] DEBUG -- : Found block device: loop5
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004926 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004950 #13155] DEBUG -- : Found block device: loop6
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.004977 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005098 #13155] DEBUG -- : Found block device: loop7
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005125 #13155] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005154 #13155] DEBUG -- : Found block device: ram10
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005182 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005204 #13155] DEBUG -- : Found block device: ram11
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005234 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005258 #13155] DEBUG -- : Found block device: ram12
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005283 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005306 #13155] DEBUG -- : Found block device: ram13
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005467 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005494 #13155] DEBUG -- : Found block device: ram14
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005521 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005546 #13155] DEBUG -- : Found block device: ram15
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005574 #13155] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.005655 #13155] 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 29 04:09:39 node-2 nailgun-agent: D, [2016-07-29T04:09:39.205619 #13155] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 29 04:09:39 node-2 nailgun-agent: I, [2016-07-29T04:09:39.206011 #13155]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 29 04:10:01 node-2 CRON[16987]: (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 29 04:10:10 node-2 puppet-user[15047]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 29 04:10:10 node-2 puppet-user[15047]: Finished catalog run in 40.22 seconds
Jul 29 04:10:12 node-2 puppet-user[17763]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 29 04:10:12 node-2 puppet-user[17763]: Compiled catalog for node-2.domain.tld in environment production in 0.63 seconds
Jul 29 04:10:12 node-2 puppet-user[17763]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 29 04:10:12 node-2 puppet-user[17763]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 29 04:10:12 node-2 puppet-user[17763]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 29 04:10:13 node-2 puppet-user[17763]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 29 04:10:13 node-2 puppet-user[17763]: Finished catalog run in 0.09 seconds
Jul 29 04:10:14 node-2 puppet-user[18237]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 29 04:10:15 node-2 puppet-user[18237]: Compiled catalog for node-2.domain.tld in environment production in 0.93 seconds
Jul 29 04:10:16 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 29 04:10:16 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 29 04:10:16 node-2 crontab[18694]: (root) LIST (root)
Jul 29 04:10:16 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 29 04:10:16 node-2 crontab[18695]: (root) REPLACE (root)
Jul 29 04:10:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:10:16 node-2 nailgun-agent: I, [2016-07-29T04:10:16.389361 #16990]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 04:10:18 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:19 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:20 node-2 puppet-user[18237]: (/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 29 04:10:21 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 29 04:10:21 node-2 puppet-user[18237]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 29 04:10:21 node-2 puppet-user[18237]: (/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 29 04:10:21 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8409" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:21 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 29 04:10:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:11:47 node-2 ntpdate[29850]: no servers can be used, exiting
<27>Jul 29 04:12:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:37 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:37 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:37 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:37 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:37 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:37 node-2 multipathd: uevent trigger error
<27>Jul 29 04:12:37 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:42 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:42 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:13:53 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 04:13:53 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 04:13:59 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 04:13:59 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 04:14:04 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 04:14:10 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 04:14:10 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 04:14:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:36 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:36 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:36 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:36 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:36 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:36 node-2 multipathd: uevent trigger error
<129>Jul 29 04:14:38 node-2 haproxy[19219]: 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 29 04:14:38 node-2 haproxy[19219]: Backup Server mysqld/node-4 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 29 04:14:39 node-2 haproxy[19228]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:39 node-2 haproxy[19228]: proxy mysqld has no server available!
<27>Jul 29 04:14:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:45 node-2 multipathd: uevent trigger error
<129>Jul 29 04:14:47 node-2 haproxy[21842]: 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 29 04:14:48 node-2 haproxy[21849]: Backup Server mysqld/node-4 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 29 04:14:48 node-2 haproxy[21849]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:48 node-2 haproxy[21849]: proxy mysqld has no server available!
<129>Jul 29 04:14:48 node-2 haproxy[21849]: 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 29 04:14:48 node-2 haproxy[21849]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:14:49 node-2 haproxy[21849]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:49 node-2 haproxy[21849]: proxy object-storage has no server available!
<27>Jul 29 04:14:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:50 node-2 multipathd: uevent trigger error
<129>Jul 29 04:14:53 node-2 haproxy[23283]: 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 29 04:14:53 node-2 haproxy[23283]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:14:53 node-2 haproxy[23283]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:53 node-2 haproxy[23283]: proxy neutron has no server available!
<129>Jul 29 04:14:53 node-2 haproxy[23283]: 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 29 04:14:53 node-2 haproxy[23283]: Backup Server mysqld/node-4 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 29 04:14:53 node-2 haproxy[23283]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:53 node-2 haproxy[23283]: proxy mysqld has no server available!
<129>Jul 29 04:14:54 node-2 haproxy[23287]: 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 29 04:14:54 node-2 haproxy[23287]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:14:54 node-2 haproxy[23287]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:54 node-2 haproxy[23287]: proxy object-storage has no server available!
<27>Jul 29 04:14:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:14:56 node-2 multipathd: uevent trigger error
<129>Jul 29 04:14:58 node-2 haproxy[24751]: 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 29 04:14:58 node-2 haproxy[24751]: Server keystone-1/node-4 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 29 04:14:58 node-2 haproxy[24751]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:58 node-2 haproxy[24751]: proxy keystone-1 has no server available!
<129>Jul 29 04:14:59 node-2 haproxy[24755]: 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 29 04:14:59 node-2 haproxy[24755]: Server keystone-2/node-4 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 29 04:14:59 node-2 haproxy[24755]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:59 node-2 haproxy[24755]: proxy keystone-2 has no server available!
<129>Jul 29 04:14:59 node-2 haproxy[24755]: 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 29 04:14:59 node-2 haproxy[24755]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:14:59 node-2 haproxy[24755]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:14:59 node-2 haproxy[24755]: proxy neutron has no server available!
<129>Jul 29 04:14:59 node-2 haproxy[24755]: 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 29 04:14:59 node-2 haproxy[24755]: Backup Server mysqld/node-4 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 29 04:15:00 node-2 haproxy[24755]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:00 node-2 haproxy[24755]: proxy mysqld has no server available!
<129>Jul 29 04:15:00 node-2 haproxy[24755]: 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 29 04:15:00 node-2 haproxy[24755]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:00 node-2 haproxy[24755]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:00 node-2 haproxy[24755]: proxy object-storage has no server available!
<27>Jul 29 04:15:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:01 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:04 node-2 haproxy[26180]: 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 29 04:15:04 node-2 haproxy[26180]: Server keystone-1/node-4 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 29 04:15:04 node-2 haproxy[26180]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:04 node-2 haproxy[26180]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:04 node-2 haproxy[26180]: 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 29 04:15:04 node-2 haproxy[26180]: Server keystone-2/node-4 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 29 04:15:04 node-2 haproxy[26180]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:04 node-2 haproxy[26180]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:04 node-2 haproxy[26180]: 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 29 04:15:04 node-2 haproxy[26180]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:04 node-2 haproxy[26180]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:04 node-2 haproxy[26180]: proxy neutron has no server available!
<129>Jul 29 04:15:05 node-2 haproxy[26184]: 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 29 04:15:05 node-2 haproxy[26184]: Backup Server mysqld/node-4 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 29 04:15:05 node-2 haproxy[26184]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:05 node-2 haproxy[26184]: proxy mysqld has no server available!
<129>Jul 29 04:15:05 node-2 haproxy[26184]: 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 29 04:15:05 node-2 haproxy[26184]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:05 node-2 haproxy[26184]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:05 node-2 haproxy[26184]: proxy object-storage has no server available!
<129>Jul 29 04:15:05 node-2 haproxy[26184]: 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 29 04:15:05 node-2 haproxy[26184]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:05 node-2 haproxy[26184]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:05 node-2 haproxy[26184]: proxy aodh has no server available!
<27>Jul 29 04:15:07 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:09 node-2 haproxy[27613]: 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 29 04:15:09 node-2 haproxy[27613]: Server keystone-1/node-4 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 29 04:15:09 node-2 haproxy[27613]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:09 node-2 haproxy[27613]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:10 node-2 haproxy[27617]: 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 29 04:15:10 node-2 haproxy[27617]: Server keystone-2/node-4 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 29 04:15:10 node-2 haproxy[27617]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:10 node-2 haproxy[27617]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:10 node-2 haproxy[27617]: 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 29 04:15:10 node-2 haproxy[27617]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:10 node-2 haproxy[27617]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:10 node-2 haproxy[27617]: proxy neutron has no server available!
<129>Jul 29 04:15:10 node-2 haproxy[27617]: 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 29 04:15:10 node-2 haproxy[27617]: Backup Server mysqld/node-4 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 29 04:15:10 node-2 haproxy[27617]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:10 node-2 haproxy[27617]: proxy mysqld has no server available!
<129>Jul 29 04:15:10 node-2 haproxy[27617]: 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 29 04:15:10 node-2 haproxy[27617]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:11 node-2 haproxy[27617]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:11 node-2 haproxy[27617]: proxy object-storage has no server available!
<129>Jul 29 04:15:11 node-2 haproxy[27617]: 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 29 04:15:11 node-2 haproxy[27617]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:11 node-2 haproxy[27617]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:11 node-2 haproxy[27617]: proxy aodh has no server available!
<129>Jul 29 04:15:11 node-2 haproxy[27617]: 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 29 04:15:11 node-2 haproxy[27617]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:11 node-2 haproxy[27617]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:11 node-2 haproxy[27617]: proxy ceilometer has no server available!
<27>Jul 29 04:15:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:13 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:15 node-2 haproxy[29037]: 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 29 04:15:15 node-2 haproxy[29037]: Server keystone-1/node-4 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 29 04:15:15 node-2 haproxy[29037]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:15 node-2 haproxy[29037]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:15 node-2 haproxy[29037]: 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 29 04:15:15 node-2 haproxy[29037]: Server keystone-2/node-4 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 29 04:15:15 node-2 haproxy[29037]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:15 node-2 haproxy[29037]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:15 node-2 haproxy[29037]: 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 29 04:15:15 node-2 haproxy[29037]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:15 node-2 haproxy[29037]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:15 node-2 haproxy[29037]: proxy neutron has no server available!
<129>Jul 29 04:15:16 node-2 haproxy[29041]: 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 29 04:15:16 node-2 haproxy[29041]: Backup Server mysqld/node-4 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 29 04:15:16 node-2 haproxy[29041]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:16 node-2 haproxy[29041]: proxy mysqld has no server available!
<129>Jul 29 04:15:16 node-2 haproxy[29041]: 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 29 04:15:16 node-2 haproxy[29041]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:16 node-2 haproxy[29041]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:16 node-2 haproxy[29041]: proxy object-storage has no server available!
<129>Jul 29 04:15:16 node-2 haproxy[29041]: 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 29 04:15:16 node-2 haproxy[29041]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:16 node-2 haproxy[29041]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:16 node-2 haproxy[29041]: proxy aodh has no server available!
<129>Jul 29 04:15:16 node-2 haproxy[29041]: 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 29 04:15:16 node-2 haproxy[29041]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:16 node-2 haproxy[29041]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:16 node-2 haproxy[29041]: proxy ceilometer has no server available!
<27>Jul 29 04:15:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:18 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:20 node-2 haproxy[30430]: 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 29 04:15:20 node-2 haproxy[30430]: 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 29 04:15:20 node-2 haproxy[30430]: Server keystone-1/node-4 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 29 04:15:20 node-2 haproxy[30430]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:20 node-2 haproxy[30430]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:20 node-2 haproxy[30430]: 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 29 04:15:20 node-2 haproxy[30430]: Server keystone-2/node-4 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 29 04:15:21 node-2 haproxy[30434]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:21 node-2 haproxy[30434]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:21 node-2 haproxy[30434]: 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 29 04:15:21 node-2 haproxy[30434]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:21 node-2 haproxy[30434]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:21 node-2 haproxy[30434]: proxy neutron has no server available!
<129>Jul 29 04:15:21 node-2 haproxy[30434]: 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 29 04:15:21 node-2 haproxy[30434]: Backup Server mysqld/node-4 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 29 04:15:21 node-2 haproxy[30434]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:21 node-2 haproxy[30434]: proxy mysqld has no server available!
<129>Jul 29 04:15:21 node-2 haproxy[30434]: 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 29 04:15:21 node-2 haproxy[30434]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:21 node-2 haproxy[30434]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:21 node-2 haproxy[30434]: proxy object-storage has no server available!
<129>Jul 29 04:15:21 node-2 haproxy[30434]: 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 29 04:15:21 node-2 haproxy[30434]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:21 node-2 haproxy[30434]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:21 node-2 haproxy[30434]: proxy aodh has no server available!
<129>Jul 29 04:15:22 node-2 haproxy[30434]: 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 29 04:15:22 node-2 haproxy[30434]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:22 node-2 haproxy[30434]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:22 node-2 haproxy[30434]: proxy ceilometer has no server available!
<27>Jul 29 04:15:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:23 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:26 node-2 haproxy[31920]: 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 29 04:15:26 node-2 haproxy[31920]: 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 29 04:15:26 node-2 haproxy[31920]: Server keystone-1/node-4 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 29 04:15:26 node-2 haproxy[31920]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:26 node-2 haproxy[31920]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:26 node-2 haproxy[31920]: 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 29 04:15:26 node-2 haproxy[31920]: Server keystone-2/node-4 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 29 04:15:26 node-2 haproxy[31920]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:26 node-2 haproxy[31920]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:26 node-2 haproxy[31920]: 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 29 04:15:26 node-2 haproxy[31920]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:26 node-2 haproxy[31920]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:26 node-2 haproxy[31920]: proxy glance-api has no server available!
<129>Jul 29 04:15:26 node-2 haproxy[31920]: 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 29 04:15:26 node-2 haproxy[31920]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:27 node-2 haproxy[31940]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:27 node-2 haproxy[31940]: proxy glance-glare has no server available!
<129>Jul 29 04:15:27 node-2 haproxy[31940]: 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 29 04:15:27 node-2 haproxy[31940]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:27 node-2 haproxy[31940]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:27 node-2 haproxy[31940]: proxy neutron has no server available!
<129>Jul 29 04:15:27 node-2 haproxy[31940]: 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 29 04:15:27 node-2 haproxy[31940]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:27 node-2 haproxy[31940]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:27 node-2 haproxy[31940]: proxy glance-registry has no server available!
<129>Jul 29 04:15:27 node-2 haproxy[31940]: 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 29 04:15:27 node-2 haproxy[31940]: Backup Server mysqld/node-4 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 29 04:15:27 node-2 haproxy[31940]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:27 node-2 haproxy[31940]: proxy mysqld has no server available!
<129>Jul 29 04:15:27 node-2 haproxy[31940]: 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 29 04:15:27 node-2 haproxy[31940]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:27 node-2 haproxy[31940]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:27 node-2 haproxy[31940]: proxy object-storage has no server available!
<129>Jul 29 04:15:27 node-2 haproxy[31940]: 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 29 04:15:27 node-2 haproxy[31940]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:27 node-2 haproxy[31940]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:27 node-2 haproxy[31940]: proxy aodh has no server available!
<129>Jul 29 04:15:27 node-2 haproxy[31940]: 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 29 04:15:28 node-2 haproxy[31940]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:28 node-2 haproxy[31940]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:28 node-2 haproxy[31940]: proxy ceilometer has no server available!
<27>Jul 29 04:15:29 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:29 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:29 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:29 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:29 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:32 node-2 haproxy[1090]: 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 29 04:15:32 node-2 haproxy[1090]: 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 29 04:15:32 node-2 haproxy[1090]: Server keystone-1/node-4 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 29 04:15:32 node-2 haproxy[1090]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:32 node-2 haproxy[1090]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:32 node-2 haproxy[1090]: 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 29 04:15:32 node-2 haproxy[1090]: Server keystone-2/node-4 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 29 04:15:32 node-2 haproxy[1090]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:32 node-2 haproxy[1090]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:32 node-2 haproxy[1090]: 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 29 04:15:32 node-2 haproxy[1090]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:32 node-2 haproxy[1090]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:32 node-2 haproxy[1090]: proxy nova-api has no server available!
<129>Jul 29 04:15:32 node-2 haproxy[1090]: 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 29 04:15:32 node-2 haproxy[1090]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:32 node-2 haproxy[1090]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:32 node-2 haproxy[1090]: proxy nova-metadata-api has no server available!
<129>Jul 29 04:15:32 node-2 haproxy[1090]: 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 29 04:15:33 node-2 haproxy[1094]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:33 node-2 haproxy[1094]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:33 node-2 haproxy[1094]: proxy glance-api has no server available!
<129>Jul 29 04:15:33 node-2 haproxy[1094]: 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 29 04:15:33 node-2 haproxy[1094]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:33 node-2 haproxy[1094]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:33 node-2 haproxy[1094]: proxy glance-glare has no server available!
<129>Jul 29 04:15:33 node-2 haproxy[1094]: 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 29 04:15:33 node-2 haproxy[1094]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:33 node-2 haproxy[1094]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:33 node-2 haproxy[1094]: proxy neutron has no server available!
<129>Jul 29 04:15:33 node-2 haproxy[1094]: 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 29 04:15:33 node-2 haproxy[1094]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:33 node-2 haproxy[1094]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:33 node-2 haproxy[1094]: proxy glance-registry has no server available!
<129>Jul 29 04:15:33 node-2 haproxy[1094]: 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 29 04:15:33 node-2 haproxy[1094]: Backup Server mysqld/node-4 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 29 04:15:33 node-2 haproxy[1094]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:33 node-2 haproxy[1094]: proxy mysqld has no server available!
<129>Jul 29 04:15:33 node-2 haproxy[1094]: 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 29 04:15:33 node-2 haproxy[1094]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:33 node-2 haproxy[1094]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:33 node-2 haproxy[1094]: proxy object-storage has no server available!
<129>Jul 29 04:15:33 node-2 haproxy[1094]: 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 29 04:15:33 node-2 haproxy[1094]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:33 node-2 haproxy[1094]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:33 node-2 haproxy[1094]: proxy aodh has no server available!
<129>Jul 29 04:15:33 node-2 haproxy[1094]: 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 29 04:15:33 node-2 haproxy[1094]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:34 node-2 haproxy[1094]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:34 node-2 haproxy[1094]: proxy ceilometer has no server available!
<129>Jul 29 04:15:34 node-2 haproxy[1094]: 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 29 04:15:34 node-2 haproxy[1094]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:34 node-2 haproxy[1094]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:34 node-2 haproxy[1094]: proxy nova-novncproxy has no server available!
<27>Jul 29 04:15:35 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:35 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:35 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:35 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:35 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:37 node-2 haproxy[2504]: 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 29 04:15:37 node-2 haproxy[2504]: 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 29 04:15:37 node-2 haproxy[2504]: Server keystone-1/node-4 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 29 04:15:37 node-2 haproxy[2504]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:37 node-2 haproxy[2504]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Server keystone-2/node-4 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 29 04:15:38 node-2 haproxy[2513]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:38 node-2 haproxy[2513]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:38 node-2 haproxy[2513]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:38 node-2 haproxy[2513]: proxy nova-api has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:38 node-2 haproxy[2513]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:38 node-2 haproxy[2513]: proxy nova-metadata-api has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Backup Server cinder-api/node-4 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 29 04:15:38 node-2 haproxy[2513]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:38 node-2 haproxy[2513]: proxy cinder-api has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:38 node-2 haproxy[2513]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:38 node-2 haproxy[2513]: proxy glance-api has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:38 node-2 haproxy[2513]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:38 node-2 haproxy[2513]: proxy glance-glare has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:38 node-2 haproxy[2513]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:38 node-2 haproxy[2513]: proxy neutron has no server available!
<129>Jul 29 04:15:38 node-2 haproxy[2513]: 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 29 04:15:38 node-2 haproxy[2513]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:39 node-2 haproxy[2513]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:39 node-2 haproxy[2513]: proxy glance-registry has no server available!
<129>Jul 29 04:15:39 node-2 haproxy[2513]: 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 29 04:15:39 node-2 haproxy[2513]: Backup Server mysqld/node-4 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 29 04:15:39 node-2 haproxy[2513]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:39 node-2 haproxy[2513]: proxy mysqld has no server available!
<129>Jul 29 04:15:39 node-2 haproxy[2513]: 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 29 04:15:39 node-2 haproxy[2513]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:39 node-2 haproxy[2513]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:39 node-2 haproxy[2513]: proxy object-storage has no server available!
<129>Jul 29 04:15:39 node-2 haproxy[2513]: 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 29 04:15:39 node-2 haproxy[2513]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:39 node-2 haproxy[2513]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:39 node-2 haproxy[2513]: proxy aodh has no server available!
<129>Jul 29 04:15:39 node-2 haproxy[2513]: 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 29 04:15:39 node-2 haproxy[2513]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:39 node-2 haproxy[2513]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:39 node-2 haproxy[2513]: proxy ceilometer has no server available!
<129>Jul 29 04:15:39 node-2 haproxy[2513]: 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 29 04:15:39 node-2 haproxy[2513]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:39 node-2 haproxy[2513]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:39 node-2 haproxy[2513]: proxy nova-novncproxy has no server available!
<27>Jul 29 04:15:40 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:41 node-2 multipathd: uevent trigger error
<129>Jul 29 04:15:43 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 29 04:15:43 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 29 04:15:43 node-2 haproxy[4195]: Server keystone-1/node-4 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 29 04:15:44 node-2 haproxy[4200]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy keystone-1 has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Server keystone-2/node-4 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 29 04:15:44 node-2 haproxy[4200]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy keystone-2 has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:44 node-2 haproxy[4200]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy nova-api has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:44 node-2 haproxy[4200]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy nova-metadata-api has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Backup Server cinder-api/node-4 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 29 04:15:44 node-2 haproxy[4200]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy cinder-api has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:44 node-2 haproxy[4200]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy glance-api has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:44 node-2 haproxy[4200]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy glance-glare has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:44 node-2 haproxy[4200]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy neutron has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:44 node-2 haproxy[4200]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy glance-registry has no server available!
<129>Jul 29 04:15:44 node-2 haproxy[4200]: 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 29 04:15:44 node-2 haproxy[4200]: Backup Server mysqld/node-4 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 29 04:15:44 node-2 haproxy[4200]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:44 node-2 haproxy[4200]: proxy mysqld has no server available!
<129>Jul 29 04:15:45 node-2 haproxy[4200]: 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 29 04:15:45 node-2 haproxy[4200]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:45 node-2 haproxy[4200]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:45 node-2 haproxy[4200]: proxy object-storage has no server available!
<129>Jul 29 04:15:45 node-2 haproxy[4200]: 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 29 04:15:45 node-2 haproxy[4200]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:45 node-2 haproxy[4200]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:45 node-2 haproxy[4200]: proxy aodh has no server available!
<129>Jul 29 04:15:45 node-2 haproxy[4200]: 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 29 04:15:45 node-2 haproxy[4200]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:45 node-2 haproxy[4200]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:45 node-2 haproxy[4200]: proxy ceilometer has no server available!
<129>Jul 29 04:15:45 node-2 haproxy[4200]: 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 29 04:15:45 node-2 haproxy[4200]: Server heat-api/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:45 node-2 haproxy[4200]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:45 node-2 haproxy[4200]: proxy heat-api has no server available!
<129>Jul 29 04:15:45 node-2 haproxy[4200]: 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 29 04:15:45 node-2 haproxy[4200]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:45 node-2 haproxy[4200]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:45 node-2 haproxy[4200]: proxy heat-api-cfn has no server available!
<129>Jul 29 04:15:45 node-2 haproxy[4200]: 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 29 04:15:45 node-2 haproxy[4200]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:45 node-2 haproxy[4200]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:45 node-2 haproxy[4200]: proxy heat-api-cloudwatch has no server available!
<129>Jul 29 04:15:45 node-2 haproxy[4200]: 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 29 04:15:45 node-2 haproxy[4200]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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 29 04:15:45 node-2 haproxy[4200]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:45 node-2 haproxy[4200]: proxy nova-novncproxy has no server available!
<27>Jul 29 04:15:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:15:50 node-2 multipathd: uevent trigger error
<27>Jul 29 04:16:04 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 04:16:25 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:16:30 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 29 04:16:32 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 29 04:17:03 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 04:17:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:32 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:19:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:19:54 node-2 multipathd: uevent trigger error
<43>Jul 29 04:20:12 node-2 apache2_error [Fri Jul 29 04:20:08.601162 2016] [mpm_event:notice] [pid 16259:tid 139644379019136] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:20:12 node-2 apache2_error [Fri Jul 29 04:20:08.601242 2016] [core:notice] [pid 16259:tid 139644379019136] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:20:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:17 node-2 multipathd: uevent trigger error
<43>Jul 29 04:20:22 node-2 apache2_error [Fri Jul 29 04:20:12.055885 2016] [mpm_event:notice] [pid 16259:tid 139644379019136] AH00491: caught SIGTERM, shutting down
<43>Jul 29 04:20:22 node-2 apache2_error [Fri Jul 29 04:20:13.142260 2016] [mpm_worker:notice] [pid 16632:tid 140027328436096] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:20:22 node-2 apache2_error [Fri Jul 29 04:20:13.142306 2016] [core:notice] [pid 16632:tid 140027328436096] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:20:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:20:26 node-2 multipathd: uevent trigger error
<43>Jul 29 04:21:42 node-2 apache2_error [Fri Jul 29 04:21:42.046635 2016] [mpm_worker:notice] [pid 16632:tid 140027328436096] AH00295: caught SIGTERM, shutting down
<43>Jul 29 04:21:52 node-2 apache2_error [Fri Jul 29 04:21:42.811616 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:21:52 node-2 apache2_error [Fri Jul 29 04:21:42.811644 2016] [core:notice] [pid 32716:tid 140709946296192] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 04:22:32 node-2 apache2_error [Fri Jul 29 04:22:28.723720 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:22:32 node-2 apache2_error [Fri Jul 29 04:22:28.917817 2016] [mpm_worker:warn] [pid 32716:tid 140709946296192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:22:32 node-2 apache2_error [Fri Jul 29 04:22:28.921335 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:22:32 node-2 apache2_error [Fri Jul 29 04:22:28.921353 2016] [core:notice] [pid 32716:tid 140709946296192] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:22:36 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:23:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:23 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:38 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:59 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:59 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:59 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:59 node-2 multipathd: uevent trigger error
<27>Jul 29 04:23:59 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:52 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:52 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:52 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:52 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:52 node-2 multipathd: uevent trigger error
<27>Jul 29 04:24:52 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:08 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:08 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:08 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:08 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:08 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:08 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:08 node-2 multipathd: uevent trigger error
<27>Jul 29 04:25:37 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:26:02 node-2 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-2 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-2 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-2 multipathd: uevent trigger error
<27>Jul 29 04:26:02 node-2 multipathd: uevent trigger error
<27>Jul 29 04:27:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:27:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:27:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:27:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:27:17 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:47 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:28:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:47 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:53 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:53 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:53 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:53 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:53 node-2 multipathd: uevent trigger error
<27>Jul 29 04:28:53 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:48 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:31:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:31:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:01 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:32:26 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:33:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:11 node-2 multipathd: uevent trigger error
<27>Jul 29 04:34:50 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:36:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:36:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:36:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:36:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:36:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:36:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:36:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:14 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:14 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:37:51 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:38:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:18 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:22 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:38:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:39:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:39:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:39:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:39:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:39:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:14 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:32 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:32 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:32 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:32 node-2 multipathd: uevent trigger error
<27>Jul 29 04:40:33 node-2 multipathd: uevent trigger error
<11>Jul 29 04:40:46 node-2 liberasurecode[22194]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:46 node-2 liberasurecode[22194]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:46 node-2 liberasurecode[22194]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:46 node-2 liberasurecode[22194]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:46 node-2 liberasurecode[22232]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:46 node-2 liberasurecode[22232]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:46 node-2 liberasurecode[22232]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:46 node-2 liberasurecode[22232]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:48 node-2 liberasurecode[22695]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:48 node-2 liberasurecode[22695]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:48 node-2 liberasurecode[22695]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:48 node-2 liberasurecode[22695]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 04:40:54 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 29 04:40:54 node-2 liberasurecode[23337]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23337]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23337]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23337]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23390]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23390]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23390]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23390]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23452]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23452]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23452]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:54 node-2 liberasurecode[23452]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23515]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23515]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23515]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23515]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23529]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23529]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23529]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23529]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23541]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23541]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23553]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23553]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23553]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:40:55 node-2 liberasurecode[23553]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:03 node-2 liberasurecode[23992]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:03 node-2 liberasurecode[23992]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:03 node-2 liberasurecode[23992]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:03 node-2 liberasurecode[23992]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 04:41:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:41:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:41:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:41:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:41:13 node-2 multipathd: uevent trigger error
<27>Jul 29 04:41:13 node-2 multipathd: uevent trigger error
<43>Jul 29 04:42:03 node-2 apache2_error [Fri Jul 29 04:42:00.606704 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:42:03 node-2 apache2_error [Fri Jul 29 04:42:00.991837 2016] [mpm_worker:warn] [pid 32716:tid 140709946296192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:42:03 node-2 apache2_error [Fri Jul 29 04:42:00.998001 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:42:03 node-2 apache2_error [Fri Jul 29 04:42:00.998032 2016] [core:notice] [pid 32716:tid 140709946296192] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:42:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:41 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:41 node-2 multipathd: uevent trigger error
<43>Jul 29 04:42:43 node-2 apache2_error [Fri Jul 29 04:42:37.981556 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:42:43 node-2 apache2_error [Fri Jul 29 04:42:38.175276 2016] [mpm_worker:warn] [pid 32716:tid 140709946296192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:42:43 node-2 apache2_error [Fri Jul 29 04:42:38.184719 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:42:43 node-2 apache2_error [Fri Jul 29 04:42:38.186968 2016] [core:notice] [pid 32716:tid 140709946296192] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:42:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:42:49 node-2 multipathd: uevent trigger error
<43>Jul 29 04:43:23 node-2 apache2_error [Fri Jul 29 04:43:23.519551 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:43:23 node-2 apache2_error [Fri Jul 29 04:43:23.718372 2016] [mpm_worker:warn] [pid 32716:tid 140709946296192] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:43:23 node-2 apache2_error [Fri Jul 29 04:43:23.728055 2016] [mpm_worker:notice] [pid 32716:tid 140709946296192] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:43:23 node-2 apache2_error [Fri Jul 29 04:43:23.728086 2016] [core:notice] [pid 32716:tid 140709946296192] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:43:27 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:27 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:27 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:27 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:27 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:27 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:34 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:40 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:40 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:40 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:40 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:40 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:40 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:55 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:43:58 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:58 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:58 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:58 node-2 multipathd: uevent trigger error
<27>Jul 29 04:43:58 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:21 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:28 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:28 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:28 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:28 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:28 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:36 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 29 04:44:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:45 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:49 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:44:54 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:00 node-2 multipathd: uevent trigger error
<11>Jul 29 04:45:01 node-2 liberasurecode[12222]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-2 liberasurecode[12222]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-2 liberasurecode[12222]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-2 liberasurecode[12222]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 04:45:11 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 04:45:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:12 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:39 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:44 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:44 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:44 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:44 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:44 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:57 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:57 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:57 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:57 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:57 node-2 multipathd: uevent trigger error
<27>Jul 29 04:45:57 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:04 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:09 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:21 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:21 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:21 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:21 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:21 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:51 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:51 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:51 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:51 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:51 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:55 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:46:56 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:00 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:05 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:10 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:10 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:10 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:10 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:10 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:15 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:19 node-2 multipathd: uevent trigger error
<27>Jul 29 04:47:19 node-2 multipathd: uevent trigger error
