Jul 24 05:59:39 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8420" x-info="http://www.rsyslog.com"] start
Jul 24 05:59:39 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 24 05:59:39 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 24 05:59:39 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 24 05:59:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 24 05:59:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 24 05:59:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 24 05:59:39 node-2 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 24 05:59:39 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=799784c8-05d0-421c-ac6a-79bbb792333f nomdmonddf nomdmonisw
Jul 24 05:59:39 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 24 05:59:39 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 24 05:59:39 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 24 05:59:39 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 24 05:59:39 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 24 05:59:39 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 24 05:59:39 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 24 05:59:39 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 24 05:59:39 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 24 05:59:39 node-2 kernel: [    0.000000] No AGP bridge found
Jul 24 05:59:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 24 05:59:39 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 24 05:59:39 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 24 05:59:39 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 24 05:59:39 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 24 05:59:39 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 24 05:59:39 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 24 05:59:39 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 24 05:59:39 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 24 05:59:39 node-2 kernel: [    0.000000]   2 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000]   3 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000]   4 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000]   5 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000]   6 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000]   7 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000]   8 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000]   9 disabled
Jul 24 05:59:39 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 24 05:59:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 24 05:59:39 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 24 05:59:39 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 24 05:59:39 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 24 05:59:39 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 24 05:59:39 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 24 05:59:39 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 24 05:59:39 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 24 05:59:39 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 24 05:59:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 24 05:59:39 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35828000-0x36c0bfff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 24 05:59:39 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 24 05:59:39 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 24 05:59:39 node-2 kernel: [    0.000000] Zone ranges:
Jul 24 05:59:39 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 24 05:59:39 node-2 kernel: [    0.000000] Early memory node ranges
Jul 24 05:59:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 24 05:59:39 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 24 05:59:39 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 24 05:59:39 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 24 05:59:39 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 24 05:59:39 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 24 05:59:39 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 24 05:59:39 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 24 05:59:39 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 24 05:59:39 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 24 05:59:39 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 24 05:59:39 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 24 05:59:39 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 24 05:59:39 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 24 05:59:39 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 24 05:59:39 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 24 05:59:39 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 24 05:59:39 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 24 05:59:39 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 24 05:59:39 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 24 05:59:39 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 24 05:59:39 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 24 05:59:39 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 24 05:59:39 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 24 05:59:39 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 24 05:59:39 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 24 05:59:39 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=799784c8-05d0-421c-ac6a-79bbb792333f nomdmonddf nomdmonisw
Jul 24 05:59:39 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 24 05:59:39 node-2 kernel: [    0.000000] Checking aperture...
Jul 24 05:59:39 node-2 kernel: [    0.000000] No AGP bridge found
Jul 24 05:59:39 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 24 05:59:39 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 24 05:59:39 node-2 kernel: [    0.000000] Memory: 32653328K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627168K reserved)
Jul 24 05:59:39 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 24 05:59:39 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 24 05:59:39 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 24 05:59:39 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 24 05:59:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 24 05:59:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 24 05:59:39 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 24 05:59:39 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 24 05:59:39 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 24 05:59:39 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 24 05:59:39 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 24 05:59:39 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 24 05:59:39 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 24 05:59:39 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 24 05:59:39 node-2 kernel: [    0.004000] tsc: Detected 3492.184 MHz processor
Jul 24 05:59:39 node-2 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.36 BogoMIPS (lpj=13968736)
Jul 24 05:59:39 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 24 05:59:39 node-2 kernel: [    0.000044] Security Framework initialized
Jul 24 05:59:39 node-2 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 24 05:59:39 node-2 kernel: [    0.000063] Yama: becoming mindful.
Jul 24 05:59:39 node-2 kernel: [    0.001464] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.006378] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.008308] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.008336] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.008623] Initializing cgroup subsys memory
Jul 24 05:59:39 node-2 kernel: [    0.008630] Initializing cgroup subsys devices
Jul 24 05:59:39 node-2 kernel: [    0.008632] Initializing cgroup subsys freezer
Jul 24 05:59:39 node-2 kernel: [    0.008634] Initializing cgroup subsys blkio
Jul 24 05:59:39 node-2 kernel: [    0.008635] Initializing cgroup subsys perf_event
Jul 24 05:59:39 node-2 kernel: [    0.008638] Initializing cgroup subsys hugetlb
Jul 24 05:59:39 node-2 kernel: [    0.008657] CPU: Physical Processor ID: 0
Jul 24 05:59:39 node-2 kernel: [    0.008658] CPU: Processor Core ID: 0
Jul 24 05:59:39 node-2 kernel: [    0.008662] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 24 05:59:39 node-2 kernel: [    0.008662] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 24 05:59:39 node-2 kernel: [    0.009356] mce: CPU supports 22 MCE banks
Jul 24 05:59:39 node-2 kernel: [    0.009383] CPU0: Thermal monitoring enabled (TM1)
Jul 24 05:59:39 node-2 kernel: [    0.009404] process: using mwait in idle threads
Jul 24 05:59:39 node-2 kernel: [    0.009407] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 24 05:59:39 node-2 kernel: [    0.009407] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 24 05:59:39 node-2 kernel: [    0.009407] tlb_flushall_shift: 6
Jul 24 05:59:39 node-2 kernel: [    0.009496] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 24 05:59:39 node-2 kernel: [    0.010220] ACPI: Core revision 20131115
Jul 24 05:59:39 node-2 kernel: [    0.022908] ACPI: All ACPI Tables successfully acquired
Jul 24 05:59:39 node-2 kernel: [    0.023068] ftrace: allocating 28617 entries in 112 pages
Jul 24 05:59:39 node-2 kernel: [    0.031887] dmar: Host address width 46
Jul 24 05:59:39 node-2 kernel: [    0.031889] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 24 05:59:39 node-2 kernel: [    0.031895] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 05:59:39 node-2 kernel: [    0.031897] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 24 05:59:39 node-2 kernel: [    0.031901] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 05:59:39 node-2 kernel: [    0.031902] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 24 05:59:39 node-2 kernel: [    0.031904] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 24 05:59:39 node-2 kernel: [    0.031905] dmar: ATSR flags: 0x0
Jul 24 05:59:39 node-2 kernel: [    0.031906] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 24 05:59:39 node-2 kernel: [    0.031907] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 24 05:59:39 node-2 kernel: [    0.032022] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 24 05:59:39 node-2 kernel: [    0.032024] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 05:59:39 node-2 kernel: [    0.032025] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 05:59:39 node-2 kernel: [    0.032026] HPET id 0 under DRHD base 0xc7ffc000
Jul 24 05:59:39 node-2 kernel: [    0.032027] Your BIOS is broken and requested that x2apic be disabled.
Jul 24 05:59:39 node-2 kernel: [    0.032027] This will slightly decrease performance.
Jul 24 05:59:39 node-2 kernel: [    0.032027] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 24 05:59:39 node-2 kernel: [    0.032458] Enabled IRQ remapping in xapic mode
Jul 24 05:59:39 node-2 kernel: [    0.032459] x2apic not enabled, IRQ remapping is in xapic mode
Jul 24 05:59:39 node-2 kernel: [    0.032463] Switched APIC routing to physical flat.
Jul 24 05:59:39 node-2 kernel: [    0.033087] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 24 05:59:39 node-2 kernel: [    0.072740] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 24 05:59:39 node-2 kernel: [    0.072746] TSC deadline timer enabled
Jul 24 05:59:39 node-2 kernel: [    0.072753] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 24 05:59:39 node-2 kernel: [    0.072759] ... version:                3
Jul 24 05:59:39 node-2 kernel: [    0.072760] ... bit width:              48
Jul 24 05:59:39 node-2 kernel: [    0.072761] ... generic registers:      4
Jul 24 05:59:39 node-2 kernel: [    0.072762] ... value mask:             0000ffffffffffff
Jul 24 05:59:39 node-2 kernel: [    0.072763] ... max period:             0000ffffffffffff
Jul 24 05:59:39 node-2 kernel: [    0.072764] ... fixed-purpose events:   3
Jul 24 05:59:39 node-2 kernel: [    0.072765] ... event mask:             000000070000000f
Jul 24 05:59:39 node-2 kernel: [    0.074187] x86: Booting SMP configuration:
Jul 24 05:59:39 node-2 kernel: [    0.088289] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 24 05:59:39 node-2 kernel: [    0.074189] .... node  #0, CPUs:        #1  #2  #3
Jul 24 05:59:39 node-2 kernel: [    0.116197] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 24 05:59:39 node-2 kernel: [    0.270360] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 24 05:59:39 node-2 kernel: [    0.325978] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 24 05:59:39 node-2 kernel: [    0.383051] x86: Booted up 2 nodes, 16 CPUs
Jul 24 05:59:39 node-2 kernel: [    0.383054] smpboot: Total of 16 processors activated (111762.05 BogoMIPS)
Jul 24 05:59:39 node-2 kernel: [    0.407551] devtmpfs: initialized
Jul 24 05:59:39 node-2 kernel: [    0.410939] EVM: security.selinux
Jul 24 05:59:39 node-2 kernel: [    0.410940] EVM: security.SMACK64
Jul 24 05:59:39 node-2 kernel: [    0.410941] EVM: security.ima
Jul 24 05:59:39 node-2 kernel: [    0.410942] EVM: security.capability
Jul 24 05:59:39 node-2 kernel: [    0.410993] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.411676] pinctrl core: initialized pinctrl subsystem
Jul 24 05:59:39 node-2 kernel: [    0.411739] regulator-dummy: no parameters
Jul 24 05:59:39 node-2 kernel: [    0.411772] RTC time:  5:59:01, date: 07/24/16
Jul 24 05:59:39 node-2 kernel: [    0.411806] NET: Registered protocol family 16
Jul 24 05:59:39 node-2 kernel: [    0.411891] cpuidle: using governor ladder
Jul 24 05:59:39 node-2 kernel: [    0.411892] cpuidle: using governor menu
Jul 24 05:59:39 node-2 kernel: [    0.411927] ACPI: bus type PCI registered
Jul 24 05:59:39 node-2 kernel: [    0.411929] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 24 05:59:39 node-2 kernel: [    0.411977] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 24 05:59:39 node-2 kernel: [    0.411979] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 24 05:59:39 node-2 kernel: [    0.425716] PCI: Using configuration type 1 for base access
Jul 24 05:59:39 node-2 kernel: [    0.426730] bio: create slab <bio-0> at 0
Jul 24 05:59:39 node-2 kernel: [    0.427021] ACPI: Added _OSI(Module Device)
Jul 24 05:59:39 node-2 kernel: [    0.427023] ACPI: Added _OSI(Processor Device)
Jul 24 05:59:39 node-2 kernel: [    0.427024] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 24 05:59:39 node-2 kernel: [    0.427025] ACPI: Added _OSI(Processor Aggregator Device)
Jul 24 05:59:39 node-2 kernel: [    0.439698] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 24 05:59:39 node-2 kernel: [    0.450302] ACPI: Interpreter enabled
Jul 24 05:59:39 node-2 kernel: [    0.450308] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 24 05:59:39 node-2 kernel: [    0.450312] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 24 05:59:39 node-2 kernel: [    0.450314] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 24 05:59:39 node-2 kernel: [    0.450321] ACPI: (supports S0 S4 S5)
Jul 24 05:59:39 node-2 kernel: [    0.450322] ACPI: Using IOAPIC for interrupt routing
Jul 24 05:59:39 node-2 kernel: [    0.450365] HEST: Table parsing has been initialized.
Jul 24 05:59:39 node-2 kernel: [    0.450368] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 24 05:59:39 node-2 kernel: [    0.450918] ACPI: No dock devices found.
Jul 24 05:59:39 node-2 kernel: [    0.462529] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 24 05:59:39 node-2 kernel: [    0.462534] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 05:59:39 node-2 kernel: [    0.462538] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 05:59:39 node-2 kernel: [    0.462566] PCI host bridge to bus 0000:ff
Jul 24 05:59:39 node-2 kernel: [    0.462568] pci_bus 0000:ff: root bus resource [bus ff]
Jul 24 05:59:39 node-2 kernel: [    0.462577] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462616] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.462646] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462682] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462712] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.462742] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.462773] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462803] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462834] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462862] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462889] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462916] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462945] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462971] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.462998] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463026] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463055] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463083] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463110] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.463139] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463165] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.463191] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463217] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463248] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.463283] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463314] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463344] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463375] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463406] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463438] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463468] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463499] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463531] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463565] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463598] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463632] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463666] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463697] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463724] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463757] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463790] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463829] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463866] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463899] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463930] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463960] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.463990] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464019] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464054] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464086] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464117] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464147] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464177] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464207] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464238] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464270] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464302] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464360] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 24 05:59:39 node-2 kernel: [    0.464363] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 05:59:39 node-2 kernel: [    0.464366] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 05:59:39 node-2 kernel: [    0.464384] PCI host bridge to bus 0000:7f
Jul 24 05:59:39 node-2 kernel: [    0.464385] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 24 05:59:39 node-2 kernel: [    0.464390] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464418] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.464444] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464474] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464499] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.464524] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.464551] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464578] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464600] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464623] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464645] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464667] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464691] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464713] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464737] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464763] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464784] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464807] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464830] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.464853] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464875] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.464897] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464921] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.464948] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 05:59:39 node-2 kernel: [    0.464982] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465009] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465037] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465064] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465089] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465116] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465142] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465170] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465197] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465226] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465254] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465282] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465314] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465340] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465367] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465396] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465421] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465447] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465476] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465505] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465532] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465559] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465584] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465612] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465639] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465666] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465696] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465722] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465744] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465769] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465795] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465825] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.465852] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.467093] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 24 05:59:39 node-2 kernel: [    0.467097] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 05:59:39 node-2 kernel: [    0.468216] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 05:59:39 node-2 kernel: [    0.468727] PCI host bridge to bus 0000:00
Jul 24 05:59:39 node-2 kernel: [    0.468730] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 24 05:59:39 node-2 kernel: [    0.468731] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 24 05:59:39 node-2 kernel: [    0.468733] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 24 05:59:39 node-2 kernel: [    0.468734] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 24 05:59:39 node-2 kernel: [    0.468735] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 24 05:59:39 node-2 kernel: [    0.468737] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 24 05:59:39 node-2 kernel: [    0.468738] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 24 05:59:39 node-2 kernel: [    0.468744] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 24 05:59:39 node-2 kernel: [    0.468826] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.468857] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.468899] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 24 05:59:39 node-2 kernel: [    0.468918] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.468947] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.468987] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 24 05:59:39 node-2 kernel: [    0.469006] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.469035] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.469075] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 24 05:59:39 node-2 kernel: [    0.469092] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.469162] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.469239] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.469314] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 05:59:39 node-2 kernel: [    0.469319] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 24 05:59:39 node-2 kernel: [    0.469403] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 24 05:59:39 node-2 kernel: [    0.469551] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 24 05:59:39 node-2 kernel: [    0.469569] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 24 05:59:39 node-2 kernel: [    0.469646] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.469699] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 05:59:39 node-2 kernel: [    0.469721] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.469776] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.469819] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 24 05:59:39 node-2 kernel: [    0.469846] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.469902] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.469945] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 24 05:59:39 node-2 kernel: [    0.469969] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 24 05:59:39 node-2 kernel: [    0.469986] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 24 05:59:39 node-2 kernel: [    0.470063] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.470113] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 05:59:39 node-2 kernel: [    0.470139] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 24 05:59:39 node-2 kernel: [    0.470387] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 24 05:59:39 node-2 kernel: [    0.470393] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 24 05:59:39 node-2 kernel: [    0.470399] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.470405] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.470412] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 24 05:59:39 node-2 kernel: [    0.470443] pci 0000:01:00.0: supports D1 D2
Jul 24 05:59:39 node-2 kernel: [    0.480495] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 05:59:39 node-2 kernel: [    0.480501] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 05:59:39 node-2 kernel: [    0.480505] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 05:59:39 node-2 kernel: [    0.480713] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.480746] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 24 05:59:39 node-2 kernel: [    0.488504] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 05:59:39 node-2 kernel: [    0.488507] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.488508] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 05:59:39 node-2 kernel: [    0.488563] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.488635] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.488711] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.488756] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 05:59:39 node-2 kernel: [    0.488759] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.488761] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 05:59:39 node-2 kernel: [    0.488814] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.488936] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.488989] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 05:59:39 node-2 kernel: [    0.488991] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.488993] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.489060] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.489183] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.489223] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.489342] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.489378] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.489497] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.489535] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 24 05:59:39 node-2 kernel: [    0.489653] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 24 05:59:39 node-2 kernel: [    0.489697] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 05:59:39 node-2 kernel: [    0.489699] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.489701] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.489762] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 24 05:59:39 node-2 kernel: [    0.489824] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.489876] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.489918] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 24 05:59:39 node-2 kernel: [    0.489999] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 24 05:59:39 node-2 kernel: [    0.490126] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 05:59:39 node-2 kernel: [    0.490129] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.490131] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.490187] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 24 05:59:39 node-2 kernel: [    0.490244] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.490292] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.490503] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 05:59:39 node-2 kernel: [    0.490507] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 05:59:39 node-2 kernel: [    0.490572] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 24 05:59:39 node-2 kernel: [    0.490627] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.490676] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.490885] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 05:59:39 node-2 kernel: [    0.490889] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 05:59:39 node-2 kernel: [    0.490948] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 24 05:59:39 node-2 kernel: [    0.491008] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.491085] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 24 05:59:39 node-2 kernel: [    0.491309] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 05:59:39 node-2 kernel: [    0.491313] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 05:59:39 node-2 kernel: [    0.491487] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 05:59:39 node-2 kernel: [    0.491525] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 05:59:39 node-2 kernel: [    0.491604] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 24 05:59:39 node-2 kernel: [    0.491622] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 24 05:59:39 node-2 kernel: [    0.491636] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 24 05:59:39 node-2 kernel: [    0.491649] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 24 05:59:39 node-2 kernel: [    0.491699] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 24 05:59:39 node-2 kernel: [    0.496500] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 05:59:39 node-2 kernel: [    0.496509] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 05:59:39 node-2 kernel: [    0.496561] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 24 05:59:39 node-2 kernel: [    0.497114] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 24 05:59:39 node-2 kernel: [    0.497117] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 05:59:39 node-2 kernel: [    0.497237] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 05:59:39 node-2 kernel: [    0.497346] PCI host bridge to bus 0000:80
Jul 24 05:59:39 node-2 kernel: [    0.497348] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 24 05:59:39 node-2 kernel: [    0.497349] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 24 05:59:39 node-2 kernel: [    0.497351] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 24 05:59:39 node-2 kernel: [    0.497359] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.497423] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.497491] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 05:59:39 node-2 kernel: [    0.497553] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 05:59:39 node-2 kernel: [    0.497559] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 24 05:59:39 node-2 kernel: [    0.497629] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 24 05:59:39 node-2 kernel: [    0.497926] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 24 05:59:39 node-2 kernel: [    0.497958] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 24 05:59:39 node-2 kernel: [    0.497987] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 24 05:59:39 node-2 kernel: [    0.498016] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 24 05:59:39 node-2 kernel: [    0.498045] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 05:59:39 node-2 kernel: [    0.498075] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 05:59:39 node-2 kernel: [    0.498104] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 05:59:39 node-2 kernel: [    0.498134] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 05:59:39 node-2 kernel: [    0.498218] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 24 05:59:39 node-2 kernel: [    0.498223] ACPI: \_SB_.UNC1: notify handler is installed
Jul 24 05:59:39 node-2 kernel: [    0.498224] ACPI: \_SB_.UNC0: notify handler is installed
Jul 24 05:59:39 node-2 kernel: [    0.498239] ACPI: \_SB_.PCI0: notify handler is installed
Jul 24 05:59:39 node-2 kernel: [    0.498292] ACPI: \_SB_.PCI1: notify handler is installed
Jul 24 05:59:39 node-2 kernel: [    0.498371] Found 4 acpi root devices
Jul 24 05:59:39 node-2 kernel: [    0.498479] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 24 05:59:39 node-2 kernel: [    0.498481] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 24 05:59:39 node-2 kernel: [    0.498482] vgaarb: loaded
Jul 24 05:59:39 node-2 kernel: [    0.498483] vgaarb: bridge control possible 0000:0c:00.0
Jul 24 05:59:39 node-2 kernel: [    0.498600] SCSI subsystem initialized
Jul 24 05:59:39 node-2 kernel: [    0.498664] libata version 3.00 loaded.
Jul 24 05:59:39 node-2 kernel: [    0.498680] ACPI: bus type USB registered
Jul 24 05:59:39 node-2 kernel: [    0.498690] usbcore: registered new interface driver usbfs
Jul 24 05:59:39 node-2 kernel: [    0.498695] usbcore: registered new interface driver hub
Jul 24 05:59:39 node-2 kernel: [    0.498730] usbcore: registered new device driver usb
Jul 24 05:59:39 node-2 kernel: [    0.498895] PCI: Using ACPI for IRQ routing
Jul 24 05:59:39 node-2 kernel: [    0.502494] PCI: pci_cache_line_size set to 64 bytes
Jul 24 05:59:39 node-2 kernel: [    0.502698] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 24 05:59:39 node-2 kernel: [    0.502700] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 24 05:59:39 node-2 kernel: [    0.502700] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 24 05:59:39 node-2 kernel: [    0.502767] NetLabel: Initializing
Jul 24 05:59:39 node-2 kernel: [    0.502768] NetLabel:  domain hash size = 128
Jul 24 05:59:39 node-2 kernel: [    0.502769] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 24 05:59:39 node-2 kernel: [    0.502779] NetLabel:  unlabeled traffic allowed by default
Jul 24 05:59:39 node-2 kernel: [    0.502836] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 24 05:59:39 node-2 kernel: [    0.502840] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 24 05:59:39 node-2 kernel: [    0.504895] Switched to clocksource hpet
Jul 24 05:59:39 node-2 kernel: [    0.508979] AppArmor: AppArmor Filesystem Enabled
Jul 24 05:59:39 node-2 kernel: [    0.508994] pnp: PnP ACPI init
Jul 24 05:59:39 node-2 kernel: [    0.509001] ACPI: bus type PNP registered
Jul 24 05:59:39 node-2 kernel: [    0.509112] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509121] pnp 00:01: [dma 4]
Jul 24 05:59:39 node-2 kernel: [    0.509133] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509159] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509179] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509197] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509231] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509285] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509287] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 24 05:59:39 node-2 kernel: [    0.509288] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509290] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509291] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509296] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509299] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 24 05:59:39 node-2 kernel: [    0.509300] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509302] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509303] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509305] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509306] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509308] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 24 05:59:39 node-2 kernel: [    0.509310] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509394] pnp 00:07: [dma 0 disabled]
Jul 24 05:59:39 node-2 kernel: [    0.509423] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509497] pnp 00:08: [dma 0 disabled]
Jul 24 05:59:39 node-2 kernel: [    0.509530] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509581] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 24 05:59:39 node-2 kernel: [    0.509930] pnp: PnP ACPI: found 10 devices
Jul 24 05:59:39 node-2 kernel: [    0.509932] ACPI: bus type PNP unregistered
Jul 24 05:59:39 node-2 kernel: [    0.516261] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 05:59:39 node-2 kernel: [    0.516264] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 05:59:39 node-2 kernel: [    0.516266] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 05:59:39 node-2 kernel: [    0.516271] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 05:59:39 node-2 kernel: [    0.516272] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516287] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516316] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 05:59:39 node-2 kernel: [    0.516331] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516360] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 05:59:39 node-2 kernel: [    0.516374] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 05:59:39 node-2 kernel: [    0.516403] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 05:59:39 node-2 kernel: [    0.516418] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 05:59:39 node-2 kernel: [    0.516450] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 05:59:39 node-2 kernel: [    0.516452] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516467] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516495] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 05:59:39 node-2 kernel: [    0.516497] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516512] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516541] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 05:59:39 node-2 kernel: [    0.516542] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516545] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516549] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 05:59:39 node-2 kernel: [    0.516551] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516553] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516557] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 05:59:39 node-2 kernel: [    0.516562] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 05:59:39 node-2 kernel: [    0.516570] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 05:59:39 node-2 kernel: [    0.516573] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 05:59:39 node-2 kernel: [    0.516580] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 24 05:59:39 node-2 kernel: [    0.516581] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 24 05:59:39 node-2 kernel: [    0.516581] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 24 05:59:39 node-2 kernel: [    0.516582] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 24 05:59:39 node-2 kernel: [    0.516583] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 24 05:59:39 node-2 kernel: [    0.516584] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 24 05:59:39 node-2 kernel: [    0.516585] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 24 05:59:39 node-2 kernel: [    0.516586] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 24 05:59:39 node-2 kernel: [    0.516587] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516588] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516589] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516589] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516590] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516591] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516592] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516593] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516594] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 24 05:59:39 node-2 kernel: [    0.516595] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516596] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 24 05:59:39 node-2 kernel: [    0.516597] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 24 05:59:39 node-2 kernel: [    0.516598] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 24 05:59:39 node-2 kernel: [    0.516599] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 24 05:59:39 node-2 kernel: [    0.516601] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 24 05:59:39 node-2 kernel: [    0.516602] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 24 05:59:39 node-2 kernel: [    0.516640] NET: Registered protocol family 2
Jul 24 05:59:39 node-2 kernel: [    0.516904] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.517233] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.517379] TCP: Hash tables configured (established 262144 bind 65536)
Jul 24 05:59:39 node-2 kernel: [    0.517422] TCP: reno registered
Jul 24 05:59:39 node-2 kernel: [    0.517451] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.517545] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.517690] NET: Registered protocol family 1
Jul 24 05:59:39 node-2 kernel: [    0.552995] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 24 05:59:39 node-2 kernel: [    0.553009] PCI: CLS 64 bytes, default 64
Jul 24 05:59:39 node-2 kernel: [    0.553084] Trying to unpack rootfs image as initramfs...
Jul 24 05:59:39 node-2 kernel: [    0.772172] Freeing initrd memory: 20368K (ffff880035828000 - ffff880036c0c000)
Jul 24 05:59:39 node-2 kernel: [    0.772208] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 24 05:59:39 node-2 kernel: [    0.772210] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 24 05:59:39 node-2 kernel: [    0.772627] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772634] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772638] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772644] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772656] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772681] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772698] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772713] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772725] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772735] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772742] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772748] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772757] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772770] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772783] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772795] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 05:59:39 node-2 kernel: [    0.772901] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 24 05:59:39 node-2 kernel: [    0.772907] Scanning for low memory corruption every 60 seconds
Jul 24 05:59:39 node-2 kernel: [    0.773327] Initialise system trusted keyring
Jul 24 05:59:39 node-2 kernel: [    0.773380] audit: initializing netlink socket (disabled)
Jul 24 05:59:39 node-2 kernel: [    0.773397] type=2000 audit(1469339940.728:1): initialized
Jul 24 05:59:39 node-2 kernel: [    0.791306] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 24 05:59:39 node-2 kernel: [    0.792814] zbud: loaded
Jul 24 05:59:39 node-2 kernel: [    0.792940] VFS: Disk quotas dquot_6.5.2
Jul 24 05:59:39 node-2 kernel: [    0.792973] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 24 05:59:39 node-2 kernel: [    0.793347] fuse init (API version 7.22)
Jul 24 05:59:39 node-2 kernel: [    0.793408] msgmni has been set to 32768
Jul 24 05:59:39 node-2 kernel: [    0.793457] Key type big_key registered
Jul 24 05:59:39 node-2 kernel: [    0.793938] Key type asymmetric registered
Jul 24 05:59:39 node-2 kernel: [    0.793939] Asymmetric key parser 'x509' registered
Jul 24 05:59:39 node-2 kernel: [    0.793963] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 24 05:59:39 node-2 kernel: [    0.794032] io scheduler noop registered
Jul 24 05:59:39 node-2 kernel: [    0.794033] io scheduler deadline registered (default)
Jul 24 05:59:39 node-2 kernel: [    0.794052] io scheduler cfq registered
Jul 24 05:59:39 node-2 kernel: [    0.794565] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    0.794688] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    0.794804] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    0.794913] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    0.795028] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    0.795125] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    0.795511] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 24 05:59:39 node-2 kernel: [    0.795536] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 24 05:59:39 node-2 kernel: [    0.795555] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 24 05:59:39 node-2 kernel: [    0.795564] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795567] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795569] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 24 05:59:39 node-2 kernel: [    0.795574] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795576] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795577] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795579] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795580] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795582] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795583] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795585] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795586] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795587] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795589] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795590] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795593] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 24 05:59:39 node-2 kernel: [    0.795598] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795600] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 24 05:59:39 node-2 kernel: [    0.795614] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795618] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 24 05:59:39 node-2 kernel: [    0.795628] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795630] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 24 05:59:39 node-2 kernel: [    0.795633] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 24 05:59:39 node-2 kernel: [    0.795671] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 24 05:59:39 node-2 kernel: [    0.795677] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 24 05:59:39 node-2 kernel: [    0.795682] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 24 05:59:39 node-2 kernel: [    0.795691] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 24 05:59:39 node-2 kernel: [    0.795731] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 24 05:59:39 node-2 kernel: [    0.795733] vesafb: scrolling: redraw
Jul 24 05:59:39 node-2 kernel: [    0.795734] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 24 05:59:39 node-2 kernel: [    0.816456] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 24 05:59:39 node-2 kernel: [    0.824984] Console: switching to colour frame buffer device 80x30
Jul 24 05:59:39 node-2 kernel: [    0.833646] fb0: VESA VGA frame buffer device
Jul 24 05:59:39 node-2 kernel: [    0.833843] intel_idle: MWAIT substates: 0x2120
Jul 24 05:59:39 node-2 kernel: [    0.833844] intel_idle: v0.4 model 0x3F
Jul 24 05:59:39 node-2 kernel: [    0.833845] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 24 05:59:39 node-2 kernel: [    0.834070] ipmi message handler version 39.2
Jul 24 05:59:39 node-2 kernel: [    0.834340] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 24 05:59:39 node-2 kernel: [    0.834790] ACPI: AC Adapter [P111] (on-line)
Jul 24 05:59:39 node-2 kernel: [    0.840037] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 24 05:59:39 node-2 kernel: [    0.851044] ACPI: Power Button [PWRB]
Jul 24 05:59:39 node-2 kernel: [    0.856806] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 24 05:59:39 node-2 kernel: [    0.868443] ACPI: Power Button [PWRF]
Jul 24 05:59:39 node-2 kernel: [    0.886393] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 24 05:59:39 node-2 kernel: [    0.898048] pstore: Registered erst as persistent store backend
Jul 24 05:59:39 node-2 kernel: [    0.904230] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 24 05:59:39 node-2 kernel: [    0.916165] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 24 05:59:39 node-2 kernel: [    0.942923] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 24 05:59:39 node-2 kernel: [    0.976176] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 24 05:59:39 node-2 kernel: [    0.990188] Linux agpgart interface v0.103
Jul 24 05:59:39 node-2 kernel: [    0.997836] brd: module loaded
Jul 24 05:59:39 node-2 kernel: [    1.004862] loop: module loaded
Jul 24 05:59:39 node-2 kernel: [    1.011572] libphy: Fixed MDIO Bus: probed
Jul 24 05:59:39 node-2 kernel: [    1.018029] tun: Universal TUN/TAP device driver, 1.6
Jul 24 05:59:39 node-2 kernel: [    1.024494] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 24 05:59:39 node-2 kernel: [    1.030990] PPP generic driver version 2.4.2
Jul 24 05:59:39 node-2 kernel: [    1.037435] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 24 05:59:39 node-2 kernel: [    1.043893] ehci-pci: EHCI PCI platform driver
Jul 24 05:59:39 node-2 kernel: [    1.050416] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 24 05:59:39 node-2 kernel: [    1.056823] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 24 05:59:39 node-2 kernel: [    1.069353] ehci-pci 0000:00:1a.0: debug port 2
Jul 24 05:59:39 node-2 kernel: [    1.079541] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 24 05:59:39 node-2 kernel: [    1.079559] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 24 05:59:39 node-2 kernel: [    1.096399] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 24 05:59:39 node-2 kernel: [    1.102456] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 05:59:39 node-2 kernel: [    1.108616] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 05:59:39 node-2 kernel: [    1.120515] usb usb1: Product: EHCI Host Controller
Jul 24 05:59:39 node-2 kernel: [    1.126527] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 05:59:39 node-2 kernel: [    1.132567] usb usb1: SerialNumber: 0000:00:1a.0
Jul 24 05:59:39 node-2 kernel: [    1.138532] hub 1-0:1.0: USB hub found
Jul 24 05:59:39 node-2 kernel: [    1.144288] hub 1-0:1.0: 2 ports detected
Jul 24 05:59:39 node-2 kernel: [    1.150066] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 24 05:59:39 node-2 kernel: [    1.155632] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 24 05:59:39 node-2 kernel: [    1.166491] ehci-pci 0000:00:1d.0: debug port 2
Jul 24 05:59:39 node-2 kernel: [    1.175768] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 24 05:59:39 node-2 kernel: [    1.175771] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 24 05:59:39 node-2 kernel: [    1.192317] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 24 05:59:39 node-2 kernel: [    1.197487] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 05:59:39 node-2 kernel: [    1.202769] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 05:59:39 node-2 kernel: [    1.213303] usb usb2: Product: EHCI Host Controller
Jul 24 05:59:39 node-2 kernel: [    1.218758] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 05:59:39 node-2 kernel: [    1.224285] usb usb2: SerialNumber: 0000:00:1d.0
Jul 24 05:59:39 node-2 kernel: [    1.229813] hub 2-0:1.0: USB hub found
Jul 24 05:59:39 node-2 kernel: [    1.235147] hub 2-0:1.0: 2 ports detected
Jul 24 05:59:39 node-2 kernel: [    1.240428] ehci-platform: EHCI generic platform driver
Jul 24 05:59:39 node-2 kernel: [    1.245645] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 24 05:59:39 node-2 kernel: [    1.250932] ohci-pci: OHCI PCI platform driver
Jul 24 05:59:39 node-2 kernel: [    1.256214] ohci-platform: OHCI generic platform driver
Jul 24 05:59:39 node-2 kernel: [    1.261390] uhci_hcd: USB Universal Host Controller Interface driver
Jul 24 05:59:39 node-2 kernel: [    1.266722] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 24 05:59:39 node-2 kernel: [    1.460097] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 24 05:59:39 node-2 kernel: [    1.767890] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 24 05:59:39 node-2 kernel: [    1.784193] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 24 05:59:39 node-2 kernel: [    1.789871] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 05:59:39 node-2 kernel: [    1.795586] hub 1-1:1.0: USB hub found
Jul 24 05:59:39 node-2 kernel: [    1.801180] hub 1-1:1.0: 6 ports detected
Jul 24 05:59:39 node-2 kernel: [    1.915733] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 24 05:59:39 node-2 kernel: [    2.305377] i8042: No controller found
Jul 24 05:59:39 node-2 kernel: [    2.310980] mousedev: PS/2 mouse device common for all mice
Jul 24 05:59:39 node-2 kernel: [    2.316813] rtc_cmos 00:02: RTC can wake from S4
Jul 24 05:59:39 node-2 kernel: [    2.322600] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 24 05:59:39 node-2 kernel: [    2.324180] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 24 05:59:39 node-2 kernel: [    2.324181] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 05:59:39 node-2 kernel: [    2.324817] hub 2-1:1.0: USB hub found
Jul 24 05:59:39 node-2 kernel: [    2.325049] hub 2-1:1.0: 8 ports detected
Jul 24 05:59:39 node-2 kernel: [    2.351129] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 24 05:59:39 node-2 kernel: [    2.362555] device-mapper: uevent: version 1.0.3
Jul 24 05:59:39 node-2 kernel: [    2.368333] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 24 05:59:39 node-2 kernel: [    2.379796] ledtrig-cpu: registered to indicate activity on CPUs
Jul 24 05:59:39 node-2 kernel: [    2.385737] TCP: cubic registered
Jul 24 05:59:39 node-2 kernel: [    2.391633] NET: Registered protocol family 10
Jul 24 05:59:39 node-2 kernel: [    2.397690] NET: Registered protocol family 17
Jul 24 05:59:39 node-2 kernel: [    2.403458] Key type dns_resolver registered
Jul 24 05:59:39 node-2 kernel: [    2.409541] Loading compiled-in X.509 certificates
Jul 24 05:59:39 node-2 kernel: [    2.415755] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 24 05:59:39 node-2 kernel: [    2.427378] registered taskstats version 1
Jul 24 05:59:39 node-2 kernel: [    2.435452] Key type trusted registered
Jul 24 05:59:39 node-2 kernel: [    2.443087] Key type encrypted registered
Jul 24 05:59:39 node-2 kernel: [    2.448582] AppArmor: AppArmor sha1 policy hashing enabled
Jul 24 05:59:39 node-2 kernel: [    2.454105] IMA: No TPM chip found, activating TPM-bypass!
Jul 24 05:59:39 node-2 kernel: [    2.460186] regulator-dummy: disabling
Jul 24 05:59:39 node-2 kernel: [    2.465695]   Magic number: 8:779:972
Jul 24 05:59:39 node-2 kernel: [    2.471190] pci 0000:7f:14.1: hash matches
Jul 24 05:59:39 node-2 kernel: [    2.476835] rtc_cmos 00:02: setting system clock to 2016-07-24 05:59:03 UTC (1469339943)
Jul 24 05:59:39 node-2 kernel: [    2.489248] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 24 05:59:39 node-2 kernel: [    2.494881] EDD information not available.
Jul 24 05:59:39 node-2 kernel: [    2.500531] PM: Hibernation image not present or could not be loaded.
Jul 24 05:59:39 node-2 kernel: [    2.501392] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 24 05:59:39 node-2 kernel: [    2.512840] Write protecting the kernel read-only data: 12288k
Jul 24 05:59:39 node-2 kernel: [    2.519193] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 24 05:59:39 node-2 kernel: [    2.532162] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 24 05:59:39 node-2 kernel: [    2.564662] device-mapper: multipath: version 1.6.0 loaded
Jul 24 05:59:39 node-2 kernel: [    2.572467] systemd-udevd[216]: starting version 204
Jul 24 05:59:39 node-2 kernel: [    2.597003] md: linear personality registered for level -1
Jul 24 05:59:39 node-2 kernel: [    2.599300] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 24 05:59:39 node-2 kernel: [    2.617436] md: multipath personality registered for level -4
Jul 24 05:59:39 node-2 kernel: [    2.625692] md: raid0 personality registered for level 0
Jul 24 05:59:39 node-2 kernel: [    2.634342] md: raid1 personality registered for level 1
Jul 24 05:59:39 node-2 kernel: [    2.640735] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 24 05:59:39 node-2 kernel: [    2.646980] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 24 05:59:39 node-2 kernel: [    2.653259] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 24 05:59:39 node-2 kernel: [    2.654087] megasas: FW now in Ready state
Jul 24 05:59:39 node-2 kernel: [    2.654181] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654231] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654271] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654312] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654360] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654404] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654444] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654454] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654466] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654502] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654536] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654574] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654634] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654676] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654716] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654757] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.654955] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 24 05:59:39 node-2 kernel: [    2.686867] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 24 05:59:39 node-2 kernel: [    2.700108] 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 24 05:59:39 node-2 kernel: [    2.713930] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 05:59:39 node-2 kernel: [    2.720922] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.720927] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.720931] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.720934] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.720972] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.741192] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 24 05:59:39 node-2 kernel: [    2.747169] raid6: sse2x1    2142 MB/s
Jul 24 05:59:39 node-2 kernel: [    2.761319] 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 24 05:59:39 node-2 kernel: [    2.774743] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 05:59:39 node-2 kernel: [    2.781494] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.781500] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.781504] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.781508] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.781541] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.801336] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 24 05:59:39 node-2 kernel: [    2.814642] 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 24 05:59:39 node-2 kernel: [    2.815043] raid6: sse2x2    2244 MB/s
Jul 24 05:59:39 node-2 kernel: [    2.834933] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 05:59:39 node-2 kernel: [    2.841719] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.841723] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.841727] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.841731] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.841764] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.855663] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 24 05:59:39 node-2 kernel: [    2.862597] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 05:59:39 node-2 kernel: [    2.863431] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 24 05:59:39 node-2 kernel: [    2.863441] 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 24 05:59:39 node-2 kernel: [    2.863466] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 05:59:39 node-2 kernel: [    2.863795] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.863897] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.863976] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.864149] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.864426] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 05:59:39 node-2 kernel: [    2.883084] raid6: sse2x4    1355 MB/s
Jul 24 05:59:39 node-2 kernel: [    2.930576] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 24 05:59:39 node-2 kernel: [    2.937292] usb 2-1.4: Manufacturer: Avocent
Jul 24 05:59:39 node-2 kernel: [    2.943870] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 24 05:59:39 node-2 kernel: [    2.950819] raid6: avx2x1    1627 MB/s
Jul 24 05:59:39 node-2 kernel: [    2.958930] hidraw: raw HID events driver (C) Jiri Kosina
Jul 24 05:59:39 node-2 kernel: [    2.968109] usbcore: registered new interface driver usbhid
Jul 24 05:59:39 node-2 kernel: [    2.974490] usbhid: USB HID core driver
Jul 24 05:59:39 node-2 kernel: [    2.981681] 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 24 05:59:39 node-2 kernel: [    2.994622] 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 24 05:59:39 node-2 kernel: [    2.995171] megasas:IOC Init cmd success
Jul 24 05:59:39 node-2 kernel: [    3.014340] 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 24 05:59:39 node-2 kernel: [    3.022784] raid6: avx2x2   13643 MB/s
Jul 24 05:59:39 node-2 kernel: [    3.033896] 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 24 05:59:39 node-2 kernel: [    3.043190] megasas: INIT adapter done
Jul 24 05:59:39 node-2 kernel: [    3.054035] 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 24 05:59:39 node-2 kernel: [    3.067741] 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 24 05:59:39 node-2 kernel: [    3.094715] raid6: avx2x4   28541 MB/s
Jul 24 05:59:39 node-2 kernel: [    3.101533] raid6: using algorithm avx2x4 (28541 MB/s)
Jul 24 05:59:39 node-2 kernel: [    3.108293] raid6: using avx2x2 recovery algorithm
Jul 24 05:59:39 node-2 kernel: [    3.114847] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 24 05:59:39 node-2 kernel: [    3.115280] scsi0 : LSI SAS based MegaRAID driver
Jul 24 05:59:39 node-2 kernel: [    3.123582] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 05:59:39 node-2 kernel: [    3.141502] Switched to clocksource tsc
Jul 24 05:59:39 node-2 kernel: [    3.148180] xor: automatically using best checksumming function:
Jul 24 05:59:39 node-2 kernel: [    3.157568] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 05:59:39 node-2 kernel: [    3.173918] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 24 05:59:39 node-2 kernel: [    3.174352] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 24 05:59:39 node-2 kernel: [    3.175353] sd 0:2:0:0: [sda] Write Protect is off
Jul 24 05:59:39 node-2 kernel: [    3.175364] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 24 05:59:39 node-2 kernel: [    3.175687] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 24 05:59:39 node-2 kernel: [    3.207555]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 24 05:59:39 node-2 kernel: [    3.212247] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 24 05:59:39 node-2 kernel: [    3.234589]    avx       : 164763.000 MB/sec
Jul 24 05:59:39 node-2 kernel: [    3.241821] async_tx: api initialized (async)
Jul 24 05:59:39 node-2 kernel: [    3.251886] md: raid6 personality registered for level 6
Jul 24 05:59:39 node-2 kernel: [    3.258341] md: raid5 personality registered for level 5
Jul 24 05:59:39 node-2 kernel: [    3.264579] md: raid4 personality registered for level 4
Jul 24 05:59:39 node-2 kernel: [    3.273685] md: raid10 personality registered for level 10
Jul 24 05:59:39 node-2 kernel: [    3.322205] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Jul 24 05:59:39 node-2 kernel: [    3.353462] random: lvm urandom read with 31 bits of entropy available
Jul 24 05:59:39 node-2 kernel: [    3.505613] bio: create slab <bio-1> at 1
Jul 24 05:59:39 node-2 kernel: [    4.360326] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 05:59:39 node-2 kernel: [    4.810219] random: nonblocking pool is initialized
Jul 24 05:59:39 node-2 kernel: [    4.910031] init: plymouth-upstart-bridge main process (574) terminated with status 1
Jul 24 05:59:39 node-2 kernel: [    4.921784] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 05:59:39 node-2 kernel: [    4.929914] init: plymouth-upstart-bridge main process (586) terminated with status 1
Jul 24 05:59:39 node-2 kernel: [    4.941998] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 05:59:39 node-2 kernel: [    5.056299] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 24 05:59:39 node-2 kernel: [    5.084414] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 24 05:59:39 node-2 kernel: [    5.273851] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 24 05:59:39 node-2 kernel: [    5.309838] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 24 05:59:39 node-2 kernel: [    5.403341] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 05:59:39 node-2 kernel: [    5.653577] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 24 05:59:39 node-2 kernel: [    5.686971] XFS (dm-1): Mounting Filesystem
Jul 24 05:59:39 node-2 kernel: [    5.937643] XFS (dm-1): Ending clean mount
Jul 24 05:59:39 node-2 kernel: [    5.996160] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 05:59:39 node-2 kernel: [    6.026437] XFS (dm-2): Mounting Filesystem
Jul 24 05:59:39 node-2 kernel: [    6.125063] XFS (dm-2): Ending clean mount
Jul 24 05:59:39 node-2 kernel: [    6.232898] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 05:59:39 node-2 kernel: [    8.004958] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 05:59:39 node-2 kernel: [    8.020185] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 05:59:39 node-2 kernel: [    8.153527] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 05:59:39 node-2 kernel: [    8.153537] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 24 05:59:39 node-2 kernel: [    8.153545] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 24 05:59:39 node-2 kernel: [    8.153553] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 24 05:59:39 node-2 kernel: [    8.198094] systemd-udevd[807]: starting version 204
Jul 24 05:59:39 node-2 kernel: [    8.423921] power_meter ACPI000D:00: Found ACPI power meter.
Jul 24 05:59:39 node-2 kernel: [    8.423934] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 24 05:59:39 node-2 kernel: [    8.468310] wmi: Mapper loaded
Jul 24 05:59:39 node-2 kernel: [    8.473263] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 24 05:59:39 node-2 kernel: [    8.479627] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 24 05:59:39 node-2 kernel: [    8.479634] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 05:59:39 node-2 kernel: [    8.479636] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 24 05:59:39 node-2 kernel: [    8.479638] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 05:59:39 node-2 kernel: [    8.479677] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 24 05:59:39 node-2 kernel: [    8.489804] IPMI System Interface driver.
Jul 24 05:59:39 node-2 kernel: [    8.489840] ipmi_si: probing via ACPI
Jul 24 05:59:39 node-2 kernel: [    8.489855] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 24 05:59:39 node-2 kernel: [    8.489856] ipmi_si: Adding ACPI-specified kcs state machine
Jul 24 05:59:39 node-2 kernel: [    8.489864] ipmi_si: probing via SMBIOS
Jul 24 05:59:39 node-2 kernel: [    8.489865] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 05:59:39 node-2 kernel: [    8.489865] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 24 05:59:39 node-2 kernel: [    8.489867] ipmi_si: probing via SPMI
Jul 24 05:59:39 node-2 kernel: [    8.489868] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 05:59:39 node-2 kernel: [    8.489868] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 24 05:59:39 node-2 kernel: [    8.489870] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 24 05:59:39 node-2 kernel: [    8.526626] systemd-udevd[848]: renamed network interface eth1 to enp7s0
Jul 24 05:59:39 node-2 kernel: [    8.546450] systemd-udevd[856]: renamed network interface eth2 to enp8s0
Jul 24 05:59:39 node-2 kernel: [    8.570587] systemd-udevd[828]: renamed network interface eth0 to enp6s0
Jul 24 05:59:39 node-2 kernel: [    8.606457] systemd-udevd[848]: renamed network interface eth3 to enp9s0
Jul 24 05:59:39 node-2 kernel: [    8.624641] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 24 05:59:39 node-2 kernel: [    8.624646] ipmi_si 00:09: IPMI kcs interface initialized
Jul 24 05:59:39 node-2 kernel: [    8.934914] type=1400 audit(1469339949.961:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=987 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.935156] type=1400 audit(1469339949.961:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=987 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.935370] type=1400 audit(1469339949.961:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=987 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.940134] type=1400 audit(1469339949.965:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=990 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.940280] type=1400 audit(1469339949.965:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=990 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.940401] type=1400 audit(1469339949.965:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=990 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.941275] type=1400 audit(1469339949.965:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1014 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.941450] type=1400 audit(1469339949.965:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1014 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.941572] type=1400 audit(1469339949.965:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1014 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    8.942737] type=1400 audit(1469339949.969:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1029 comm="apparmor_parser"
Jul 24 05:59:39 node-2 kernel: [    9.558906] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 05:59:39 node-2 kernel: [    9.575228] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 05:59:39 node-2 kernel: [    9.749525] enic 0000:06:00.0 enp6s0: Link UP
Jul 24 05:59:39 node-2 kernel: [    9.749937] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 24 05:59:39 node-2 kernel: [    9.749946] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 24 05:59:39 node-2 kernel: [   20.329648] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 24 05:59:39 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 24 05:59:39 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 24 05:59:39 node-2 kernel: [   39.329803] init: failsafe main process (8448) killed by TERM signal
Jul 24 05:59:40 node-2 dbus[8555]: [system] AppArmor D-Bus mediation is enabled
Jul 24 05:59:40 node-2 kernel: [   39.588017] audit_printk_skb: 30 callbacks suppressed
Jul 24 05:59:40 node-2 kernel: [   39.588019] type=1400 audit(1469339980.230:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8566 comm="apparmor_parser"
Jul 24 05:59:40 node-2 kernel: [   39.588502] type=1400 audit(1469339980.230:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8565 comm="apparmor_parser"
Jul 24 05:59:40 node-2 kernel: [   39.588550] type=1400 audit(1469339980.230:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8565 comm="apparmor_parser"
Jul 24 05:59:40 node-2 kernel: [   39.588565] type=1400 audit(1469339980.230:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8565 comm="apparmor_parser"
Jul 24 05:59:40 node-2 kernel: [   39.589856] type=1400 audit(1469339980.230:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8565 comm="apparmor_parser"
Jul 24 05:59:40 node-2 kernel: [   39.589910] type=1400 audit(1469339980.230:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8565 comm="apparmor_parser"
Jul 24 05:59:40 node-2 kernel: [   39.590292] type=1400 audit(1469339980.230:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8565 comm="apparmor_parser"
Jul 24 05:59:40 node-2 kernel: [   39.679429] type=1400 audit(1469339980.318:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8568 comm="apparmor_parser"
Jul 24 05:59:40 node-2 cron[8606]: (CRON) INFO (pidfile fd = 3)
Jul 24 05:59:40 node-2 anacron[8624]: Anacron 2.3 started on 2016-07-24
Jul 24 05:59:40 node-2 anacron[8624]: Will run job `cron.daily' in 5 min.
Jul 24 05:59:40 node-2 anacron[8624]: Will run job `cron.weekly' in 10 min.
Jul 24 05:59:40 node-2 anacron[8624]: Will run job `cron.monthly' in 15 min.
Jul 24 05:59:40 node-2 anacron[8624]: Jobs will be executed sequentially
Jul 24 05:59:40 node-2 multipathd: path checkers start up
Jul 24 05:59:40 node-2 cron[8689]: (CRON) STARTUP (fork ok)
Jul 24 05:59:40 node-2 cron[8689]: (CRON) INFO (Running @reboot jobs)
Jul 24 05:59:40 node-2 postfix/master[8785]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 24 05:59:44 node-2 puppet-agent[8970]: Reopening log files
Jul 24 05:59:46 node-2 puppet-agent[8970]: Could not request certificate: Connection refused - connect(2)
Jul 24 05:59:58 node-2 puppet-user[9049]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 24 05:59:58 node-2 puppet-user[9049]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 24 05:59:59 node-2 puppet-user[9049]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 24 05:59:59 node-2 puppet-user[9049]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 24 05:59:59 node-2 puppet-user[9049]: Finished catalog run in 0.60 seconds
Jul 24 06:00:00 node-2 multipathd: uevent trigger error
Jul 24 06:00:00 node-2 puppet-user[9492]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 06:00:00 node-2 puppet-user[9492]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 24 06:00:00 node-2 puppet-user[9492]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 24 06:00:00 node-2 puppet-user[9492]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 24 06:00:00 node-2 puppet-user[9492]: (/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 24 06:00:00 node-2 puppet-user[9492]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 24 06:00:00 node-2 puppet-user[9492]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 24 06:00:00 node-2 puppet-user[9492]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 24 06:00:00 node-2 puppet-user[9492]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 24 06:00:00 node-2 puppet-user[9492]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 24 06:00:00 node-2 puppet-user[9492]: Finished catalog run in 0.08 seconds
Jul 24 06:00:01 node-2 CRON[10254]: (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 24 06:00:01 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 06:00:01 node-2 nailgun-agent: D, [2016-07-24T06:00:01.798562 #10257] DEBUG -- : Sleep for 0 seconds before sending request
Jul 24 06:00:01 node-2 nailgun-agent: I, [2016-07-24T06:00:01.813492 #10257]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 06:00:01 node-2 puppet-user[10061]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 24 06:00:02 node-2 puppet-user[10061]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 24 06:00:02 node-2 puppet-user[10061]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 24 06:00:02 node-2 puppet-user[10061]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 24 06:00:02 node-2 puppet-user[10061]: Finished catalog run in 0.03 seconds
Jul 24 06:00:02 node-2 nailgun-agent: D, [2016-07-24T06:00:02.210929 #10257] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 24 06:00:03 node-2 puppet-user[10661]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 24 06:00:03 node-2 puppet-user[10661]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 24 06:00:03 node-2 puppet-user[10661]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 24 06:00:03 node-2 puppet-user[10661]: Finished catalog run in 0.04 seconds
Jul 24 06:00:05 node-2 puppet-user[11110]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 24 06:00:05 node-2 puppet-user[11110]: Compiled catalog for node-2.domain.tld in environment production in 0.25 seconds
Jul 24 06:00:05 node-2 puppet-user[11110]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 24 06:00:07 node-2 puppet-user[11110]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Jul 24 06:00:08 node-2 puppet-user[11110]: Finished catalog run in 2.52 seconds
Jul 24 06:00:09 node-2 puppet-user[11670]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 24 06:00:09 node-2 puppet-user[11670]: Compiled catalog for node-2.domain.tld in environment production in 0.25 seconds
Jul 24 06:00:09 node-2 puppet-user[11670]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 24 06:00:09 node-2 puppet-user[11670]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Jul 24 06:00:09 node-2 puppet-user[11670]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 24 06:00:10 node-2 puppet-user[11670]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 24 06:00:10 node-2 puppet-user[11670]: Finished catalog run in 0.30 seconds
Jul 24 06:00:11 node-2 puppet-user[12155]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 24 06:00:11 node-2 puppet-user[12155]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Jul 24 06:00:11 node-2 puppet-user[12155]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 24 06:00:11 node-2 kernel: [   71.263173] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 24 06:00:11 node-2 kernel: [   71.263224] 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 24 06:00:11 node-2 puppet-user[12155]: (/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 24 06:00:11 node-2 puppet-user[12155]: Finished catalog run in 0.05 seconds
Jul 24 06:00:14 node-2 puppet-user[12805]: (Scope(Class[main])) MODULAR: sync_time
Jul 24 06:00:14 node-2 puppet-user[12805]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.136947 #10257] DEBUG -- : Trying to find block devices
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.137026 #10257] DEBUG -- : Found block device: sda
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.137066 #10257] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.137095 #10257] DEBUG -- : Trying to get list of physical devices
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.137245 #10257] DEBUG -- : Getting udev properties for device: sda
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.139101 #10257] 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 24 06:00:14 node-2 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"68463", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.139129 #10257] DEBUG -- : Trying to find out if device sda is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.139179 #10257] DEBUG -- : Device sda removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.139206 #10257] DEBUG -- : Device sda seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.139696 #10257] DEBUG -- : Getting udev properties for device: dm-0
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.141386 #10257] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-w2DZHSqHrdRPJmP5IE76f2np5dpPuQ30kNPIhX5F7CW2YEeNbSEmVPKnEgOcOSkP /dev/disk/by-uuid/8d498fc2-38d4-4db7-b87f-2687c63d13cd /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-w2DZHSqHrdRPJmP5IE76f2np5dpPuQ30kNPIhX5F7CW2YEeNbSEmVPKnEgOcOSkP", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8d498fc2-38d4-4db7-b87f-2687c63d13cd", "ID_FS_UUID_ENC"=>"8d498fc2-38d4-4db7-b87f-2687c63d13cd", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6
Jul 24 06:00:14 node-2 nailgun-agent: 3171", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.141417 #10257] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.141479 #10257] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.141494 #10257] DEBUG -- : Device dm-0 seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.141510 #10257] DEBUG -- : Getting udev properties for device: dm-1
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.143172 #10257] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-pUbXboQWICdeHediUhHfO3cq5pbJ1G0PhCEqD1LwKDdetg8vP96ISvjJOKEsW0ds /dev/disk/by-uuid/08cd767c-f133-4a1b-8bda-54528dd1c13a /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-pUbXboQWICdeHediUhHfO3cq5pbJ1G0PhCEqD1LwKDdetg8vP96ISvjJOKEsW0ds", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"08cd767c-f133-4a1b-8bda-54528dd1c13a", "ID_FS_UUID_ENC"=>"08cd767c-f133-4a1b-8bda-54528dd1c13a", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84207", "nomdmonddf"=>"1", "nom
Jul 24 06:00:14 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.143208 #10257] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.143255 #10257] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.143288 #10257] DEBUG -- : Device dm-1 seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.143313 #10257] DEBUG -- : Getting udev properties for device: dm-2
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.144868 #10257] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-Tvk11QpwDBqD8eEFa7MhDSOW1lCh200tJLxgfw0X1qvj2J4Ox0ad12Gab0Q0utY9 /dev/disk/by-uuid/828bb62f-5d5a-4ad7-a68d-88220826456e /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-Tvk11QpwDBqD8eEFa7MhDSOW1lCh200tJLxgfw0X1qvj2J4Ox0ad12Gab0Q0utY9", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"828bb62f-5d5a-4ad7-a68d-88220826456e", "ID_FS_UUID_ENC"=>"828bb62f-5d5a-4ad7-a68d-88220826456e", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9
Jul 24 06:00:14 node-2 nailgun-agent: 3123", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.144907 #10257] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.144948 #10257] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.144985 #10257] DEBUG -- : Device dm-2 seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.145000 #10257] DEBUG -- : Getting udev properties for device: dm-3
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.146659 #10257] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-uMM4DeyI57SvQKbmc1R8BWwymT0cWesHSry73cavFeHN1ZJRD3O14VZdsfgFSaH8 /dev/disk/by-uuid/e9a0249e-ea78-4449-acb2-fccd4b9d5c55 /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-uMM4DeyI57SvQKbmc1R8BWwymT0cWesHSry73cavFeHN1ZJRD3O14VZdsfgFSaH8", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e9a0249e-ea78-4449-acb2-fccd4b9d5c55", "ID_FS_UUID_ENC"=>"e9a0249e-ea78-4449-acb2-fccd4b9d5c55", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89976", "nomdmon
Jul 24 06:00:14 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.146685 #10257] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.146726 #10257] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.146742 #10257] DEBUG -- : Device dm-3 seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.146759 #10257] DEBUG -- : Getting udev properties for device: dm-4
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.148370 #10257] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-S8HY3QVVVJioLltcdlMSpbLDQ3K5o1IfBLCHMSMAmLS1QGzI42ejJAbke2zAhtAk /dev/disk/by-uuid/c6c9e2cf-0471-410f-848b-bcff9b29b3eb /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-S8HY3QVVVJioLltcdlMSpbLDQ3K5o1IfBLCHMSMAmLS1QGzI42ejJAbke2zAhtAk", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c6c9e2cf-0471-410f-848b-bcff9b29b3eb", "ID_FS_UUID_ENC"=>"c6c9e2cf-0471-410f-848b-bcff9b29b3eb", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94190", "nomdmonddf"=>"1",
Jul 24 06:00:14 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.148396 #10257] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.148438 #10257] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.148464 #10257] DEBUG -- : Device dm-4 seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.148481 #10257] DEBUG -- : Getting udev properties for device: dm-5
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.150041 #10257] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-Aw08Yd8fOkR0yIfQzUAMzk0sSOdW38ac90Re2XfGds25M6wVJm0zMWqqqL5FKGQj /dev/disk/by-uuid/799784c8-05d0-421c-ac6a-79bbb792333f /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-Aw08Yd8fOkR0yIfQzUAMzk0sSOdW38ac90Re2XfGds25M6wVJm0zMWqqqL5FKGQj", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"799784c8-05d0-421c-ac6a-79bbb792333f", "ID_FS_UUID_ENC"=>"799784c8-05d0-421c-ac6a-79bbb792333f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90658", "nomdmonddf"=>"1", "nom
Jul 24 06:00:14 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.150067 #10257] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.150142 #10257] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.150180 #10257] DEBUG -- : Device dm-5 seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.150204 #10257] DEBUG -- : Getting udev properties for device: dm-6
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.152250 #10257] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-Aw08Yd8fOkR0yIfQzUAMzk0sSOdW38acZnGVmeGs8YDKf8UUjjsX0bZbms7hdtTE /dev/disk/by-uuid/a28dd236-fad7-4c69-91bf-4dfcb876d7f4 /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-Aw08Yd8fOkR0yIfQzUAMzk0sSOdW38acZnGVmeGs8YDKf8UUjjsX0bZbms7hdtTE", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"a28dd236-fad7-4c69-91bf-4dfcb876d7f4", "ID_FS_UUID_ENC"=>"a28dd236-fad7-4c69-91bf-4dfcb876d7f4", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"91114", "nomdmonddf"=>"1", "nomdmonisw
Jul 24 06:00:14 node-2 nailgun-agent: "=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.152313 #10257] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.152354 #10257] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.152379 #10257] DEBUG -- : Device dm-6 seems to be appropriate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.152408 #10257] DEBUG -- : Getting udev properties for device: ram0
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.154073 #10257] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52488", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.154107 #10257] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.154192 #10257] DEBUG -- : Device ram0 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.154217 #10257] DEBUG -- : Getting udev properties for device: ram1
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.155983 #10257] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52611", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.156009 #10257] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.156052 #10257] DEBUG -- : Device ram1 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.156079 #10257] DEBUG -- : Getting udev properties for device: ram2
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.157686 #10257] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53354", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.157726 #10257] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.157761 #10257] DEBUG -- : Device ram2 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.157782 #10257] DEBUG -- : Getting udev properties for device: ram3
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.159589 #10257] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53451", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.159629 #10257] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.159678 #10257] DEBUG -- : Device ram3 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.159698 #10257] DEBUG -- : Getting udev properties for device: ram4
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.161196 #10257] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53546", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.161223 #10257] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.161257 #10257] DEBUG -- : Device ram4 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.161290 #10257] DEBUG -- : Getting udev properties for device: ram5
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.162931 #10257] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53625", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.162973 #10257] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.163010 #10257] DEBUG -- : Device ram5 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.163043 #10257] DEBUG -- : Getting udev properties for device: ram6
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.164948 #10257] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53729", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.165020 #10257] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.165072 #10257] DEBUG -- : Device ram6 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.165098 #10257] DEBUG -- : Getting udev properties for device: ram7
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.167193 #10257] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53820", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.167244 #10257] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.167295 #10257] DEBUG -- : Device ram7 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.172820 #10257] DEBUG -- : Getting udev properties for device: ram8
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.174743 #10257] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53895", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.174774 #10257] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.174811 #10257] DEBUG -- : Device ram8 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.174835 #10257] DEBUG -- : Getting udev properties for device: ram9
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.176748 #10257] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54112", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.176776 #10257] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.176821 #10257] DEBUG -- : Device ram9 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.176842 #10257] DEBUG -- : Getting udev properties for device: loop0
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.179356 #10257] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47276", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.179383 #10257] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.179422 #10257] DEBUG -- : Device loop0 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.179443 #10257] DEBUG -- : Getting udev properties for device: loop1
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.180915 #10257] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47747", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.180940 #10257] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.180981 #10257] DEBUG -- : Device loop1 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.181002 #10257] DEBUG -- : Getting udev properties for device: loop2
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.182440 #10257] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48869", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.182495 #10257] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.182536 #10257] DEBUG -- : Device loop2 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.182556 #10257] DEBUG -- : Getting udev properties for device: loop3
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.184014 #10257] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49276", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.184041 #10257] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.184109 #10257] DEBUG -- : Device loop3 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.184130 #10257] DEBUG -- : Getting udev properties for device: loop4
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.185556 #10257] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49573", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.185583 #10257] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.185616 #10257] DEBUG -- : Device loop4 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.185637 #10257] DEBUG -- : Getting udev properties for device: loop5
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.187108 #10257] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49991", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.187134 #10257] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.187169 #10257] DEBUG -- : Device loop5 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.187190 #10257] DEBUG -- : Getting udev properties for device: loop6
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.188641 #10257] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50466", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.188667 #10257] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.188704 #10257] DEBUG -- : Device loop6 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.188725 #10257] DEBUG -- : Getting udev properties for device: loop7
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.190679 #10257] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52362", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.190705 #10257] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.190745 #10257] DEBUG -- : Device loop7 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.190766 #10257] DEBUG -- : Getting udev properties for device: ram10
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.192184 #10257] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52689", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.192211 #10257] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.192248 #10257] DEBUG -- : Device ram10 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.192269 #10257] DEBUG -- : Getting udev properties for device: ram11
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.193687 #10257] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52811", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.193713 #10257] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.193748 #10257] DEBUG -- : Device ram11 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.193769 #10257] DEBUG -- : Getting udev properties for device: ram12
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.195174 #10257] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52984", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.195200 #10257] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.195275 #10257] DEBUG -- : Device ram12 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.195295 #10257] DEBUG -- : Getting udev properties for device: ram13
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.196695 #10257] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53077", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.196722 #10257] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.196755 #10257] DEBUG -- : Device ram13 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.196802 #10257] DEBUG -- : Getting udev properties for device: ram14
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.198163 #10257] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53181", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.198191 #10257] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.198223 #10257] DEBUG -- : Device ram14 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.198243 #10257] DEBUG -- : Getting udev properties for device: ram15
Jul 24 06:00:14 node-2 ntpdate[13399]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 24 06:00:14 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199685 #10257] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53272", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199711 #10257] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199742 #10257] DEBUG -- : Device ram15 removable parameter: "0"
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199781 #10257] 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 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199797 #10257] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199870 #10257] DEBUG -- : Found block device: dm-0
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199887 #10257] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199913 #10257] DEBUG -- : Found block device: dm-1
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199925 #10257] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199935 #10257] DEBUG -- : Found block device: dm-2
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199946 #10257] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199956 #10257] DEBUG -- : Found block device: dm-3
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199966 #10257] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199976 #10257] DEBUG -- : Found block device: dm-4
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.199987 #10257] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200025 #10257] DEBUG -- : Found block device: dm-5
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200037 #10257] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200046 #10257] DEBUG -- : Found block device: dm-6
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200056 #10257] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200065 #10257] DEBUG -- : Found block device: ram0
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200077 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200086 #10257] DEBUG -- : Found block device: ram1
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200097 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200106 #10257] DEBUG -- : Found block device: ram2
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200118 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200152 #10257] DEBUG -- : Found block device: ram3
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200164 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200174 #10257] DEBUG -- : Found block device: ram4
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200185 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200194 #10257] DEBUG -- : Found block device: ram5
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200205 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200214 #10257] DEBUG -- : Found block device: ram6
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200226 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200235 #10257] DEBUG -- : Found block device: ram7
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200245 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200283 #10257] DEBUG -- : Found block device: ram8
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200295 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200304 #10257] DEBUG -- : Found block device: ram9
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200315 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200324 #10257] DEBUG -- : Found block device: loop0
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200335 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200345 #10257] DEBUG -- : Found block device: loop1
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200356 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200365 #10257] DEBUG -- : Found block device: loop2
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200375 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200384 #10257] DEBUG -- : Found block device: loop3
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200426 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200436 #10257] DEBUG -- : Found block device: loop4
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200447 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200456 #10257] DEBUG -- : Found block device: loop5
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200467 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200476 #10257] DEBUG -- : Found block device: loop6
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200488 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200497 #10257] DEBUG -- : Found block device: loop7
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200508 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200562 #10257] DEBUG -- : Found block device: ram10
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200574 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200583 #10257] DEBUG -- : Found block device: ram11
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200593 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200603 #10257] DEBUG -- : Found block device: ram12
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200613 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200623 #10257] DEBUG -- : Found block device: ram13
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200633 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200642 #10257] DEBUG -- : Found block device: ram14
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200699 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200709 #10257] DEBUG -- : Found block device: ram15
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200720 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.200752 #10257] 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 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.295199 #10257] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 24 06:00:14 node-2 nailgun-agent: D, [2016-07-24T06:00:14.295269 #10257] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 24 06:00:20 node-2 ntpdate[13399]: adjust time server 10.20.0.2 offset 0.002206 sec
Jul 24 06:00:20 node-2 puppet-user[12805]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 24 06:00:20 node-2 puppet-user[12805]: Finished catalog run in 6.17 seconds
Jul 24 06:00:24 node-2 kernel: [   83.722680] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 06:00:24 node-2 puppet-agent[8970]: Could not run: SIGTERM
Jul 24 06:00:24 node-2 kernel: [   84.030890] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 24 06:00:24 node-2 ec2: 
Jul 24 06:00:24 node-2 ec2: #############################################################
Jul 24 06:00:24 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 24 06:00:24 node-2 ec2: 1024 00:25:8a:93:57:3e:9b:29:27:d6:17:49:85:ad:76:55  root@node-2.domain.tld (DSA)
Jul 24 06:00:24 node-2 ec2: 256 26:23:1c:48:dc:09:34:cb:df:6f:0f:6f:d9:0d:66:b8  root@node-2.domain.tld (ECDSA)
Jul 24 06:00:24 node-2 ec2: 256 f7:79:a6:10:b4:5c:11:8b:bd:1f:87:53:05:fd:3d:b0  root@node-2.domain.tld (ED25519)
Jul 24 06:00:24 node-2 ec2: 2048 79:06:40:e7:66:dd:7d:78:e4:97:fe:d3:64:23:00:37  root@node-2.domain.tld (RSA)
Jul 24 06:00:24 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 24 06:00:24 node-2 ec2: #############################################################
Jul 24 06:00:25 node-2 puppet-user[13728]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 06:00:25 node-2 puppet-user[13728]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Jul 24 06:00:25 node-2 puppet-user[13728]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 24 06:00:25 node-2 puppet-user[13728]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 24 06:00:25 node-2 puppet-user[13728]: Finished catalog run in 0.07 seconds
Jul 24 06:00:26 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.173813 #10257] DEBUG -- : Trying to find block devices
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.173907 #10257] DEBUG -- : Found block device: sda
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.173935 #10257] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.173953 #10257] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.173991 #10257] DEBUG -- : Found block device: dm-0
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174003 #10257] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174014 #10257] DEBUG -- : Found block device: dm-1
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174025 #10257] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174034 #10257] DEBUG -- : Found block device: dm-2
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174044 #10257] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174054 #10257] DEBUG -- : Found block device: dm-3
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174063 #10257] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174073 #10257] DEBUG -- : Found block device: dm-4
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174102 #10257] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174112 #10257] DEBUG -- : Found block device: dm-5
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174132 #10257] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174146 #10257] DEBUG -- : Found block device: dm-6
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174156 #10257] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174166 #10257] DEBUG -- : Found block device: ram0
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174176 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174184 #10257] DEBUG -- : Found block device: ram1
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174209 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174219 #10257] DEBUG -- : Found block device: ram2
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174230 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174238 #10257] DEBUG -- : Found block device: ram3
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174248 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174257 #10257] DEBUG -- : Found block device: ram4
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174267 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174276 #10257] DEBUG -- : Found block device: ram5
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174302 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174312 #10257] DEBUG -- : Found block device: ram6
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174321 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174330 #10257] DEBUG -- : Found block device: ram7
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174339 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174348 #10257] DEBUG -- : Found block device: ram8
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174357 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174366 #10257] DEBUG -- : Found block device: ram9
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174375 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174384 #10257] DEBUG -- : Found block device: loop0
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174409 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174418 #10257] DEBUG -- : Found block device: loop1
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174427 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174436 #10257] DEBUG -- : Found block device: loop2
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174445 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174454 #10257] DEBUG -- : Found block device: loop3
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174464 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174473 #10257] DEBUG -- : Found block device: loop4
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174483 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174491 #10257] DEBUG -- : Found block device: loop5
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174525 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174535 #10257] DEBUG -- : Found block device: loop6
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174545 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174553 #10257] DEBUG -- : Found block device: loop7
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174562 #10257] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174571 #10257] DEBUG -- : Found block device: ram10
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174581 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174589 #10257] DEBUG -- : Found block device: ram11
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174598 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174627 #10257] DEBUG -- : Found block device: ram12
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174638 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174646 #10257] DEBUG -- : Found block device: ram13
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174656 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174665 #10257] DEBUG -- : Found block device: ram14
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174675 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174683 #10257] DEBUG -- : Found block device: ram15
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174692 #10257] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.174719 #10257] 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 24 06:00:26 node-2 nailgun-agent: D, [2016-07-24T06:00:26.380958 #10257] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 24 06:00:26 node-2 nailgun-agent: I, [2016-07-24T06:00:26.381126 #10257]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 24 06:00:27 node-2 puppet-user[14347]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 24 06:00:28 node-2 puppet-user[14347]: Compiled catalog for node-2.domain.tld in environment production in 0.68 seconds
Jul 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:28 node-2 puppet-user[14347]: (/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 24 06:00:42 node-2 puppet-user[14347]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 24 06:00:42 node-2 puppet-user[14347]: Finished catalog run in 14.69 seconds
Jul 24 06:00:44 node-2 puppet-user[15278]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 24 06:00:45 node-2 puppet-user[15278]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Jul 24 06:00:50 node-2 puppet-user[15278]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 24 06:01:01 node-2 CRON[16709]: (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 24 06:01:15 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 06:01:15 node-2 nailgun-agent: I, [2016-07-24T06:01:15.577854 #16713]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 06:01:25 node-2 puppet-user[15278]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 24 06:01:25 node-2 puppet-user[15278]: Finished catalog run in 40.08 seconds
Jul 24 06:01:27 node-2 puppet-user[17954]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 24 06:01:27 node-2 puppet-user[17954]: Compiled catalog for node-2.domain.tld in environment production in 0.52 seconds
Jul 24 06:01:27 node-2 puppet-user[17954]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 24 06:01:27 node-2 puppet-user[17954]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 24 06:01:27 node-2 puppet-user[17954]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 24 06:01:27 node-2 puppet-user[17954]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 24 06:01:27 node-2 puppet-user[17954]: Finished catalog run in 0.12 seconds
Jul 24 06:01:28 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 06:01:28 node-2 nailgun-agent: I, [2016-07-24T06:01:28.623000 #16713]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 24 06:01:29 node-2 puppet-user[18440]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 24 06:01:30 node-2 puppet-user[18440]: Compiled catalog for node-2.domain.tld in environment production in 0.96 seconds
Jul 24 06:01:30 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 24 06:01:30 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 24 06:01:31 node-2 crontab[19035]: (root) LIST (root)
Jul 24 06:01:31 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 24 06:01:31 node-2 crontab[19036]: (root) REPLACE (root)
Jul 24 06:01:33 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 24 06:01:34 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 24 06:01:35 node-2 puppet-user[18440]: (/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 24 06:01:36 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 24 06:01:36 node-2 puppet-user[18440]: (/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 24 06:01:36 node-2 puppet-user[18440]: (/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 24 06:01:36 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 24 06:01:36 node-2 puppet-user[18440]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 24 06:01:36 node-2 puppet-user[18440]: (/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 24 06:01:36 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8420" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 06:01:36 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 24 06:01:38 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:38 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:38 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:38 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:38 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:38 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:01:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:02:50 node-2 multipathd: uevent trigger error
<27>Jul 24 06:02:50 node-2 multipathd: uevent trigger error
<27>Jul 24 06:02:50 node-2 multipathd: uevent trigger error
<27>Jul 24 06:02:50 node-2 multipathd: uevent trigger error
<27>Jul 24 06:02:50 node-2 multipathd: uevent trigger error
<27>Jul 24 06:03:33 node-2 ntpdate[2562]: no servers can be used, exiting
<27>Jul 24 06:03:34 node-2 ntpdate[2771]: no servers can be used, exiting
<27>Jul 24 06:04:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:04:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:05:39 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 06:05:39 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 06:05:45 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 06:05:45 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 06:05:51 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 06:05:56 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 06:05:56 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 06:06:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:16 node-2 multipathd: uevent trigger error
<129>Jul 24 06:06:19 node-2 haproxy[23063]: 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 24 06:06:19 node-2 haproxy[23063]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:20 node-2 haproxy[23075]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:20 node-2 haproxy[23075]: proxy mysqld has no server available!
<27>Jul 24 06:06:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:26 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:26 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:26 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:26 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:26 node-2 multipathd: uevent trigger error
<129>Jul 24 06:06:28 node-2 haproxy[25815]: 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 24 06:06:28 node-2 haproxy[25815]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:29 node-2 haproxy[25824]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:29 node-2 haproxy[25824]: proxy mysqld has no server available!
<129>Jul 24 06:06:29 node-2 haproxy[25824]: 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 24 06:06:29 node-2 haproxy[25824]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:30 node-2 haproxy[25824]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:30 node-2 haproxy[25824]: proxy object-storage has no server available!
<27>Jul 24 06:06:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:31 node-2 multipathd: uevent trigger error
<129>Jul 24 06:06:33 node-2 haproxy[27393]: 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 24 06:06:34 node-2 haproxy[27397]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:34 node-2 haproxy[27397]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:34 node-2 haproxy[27397]: proxy neutron has no server available!
<129>Jul 24 06:06:34 node-2 haproxy[27397]: 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 24 06:06:34 node-2 haproxy[27397]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:34 node-2 haproxy[27397]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:34 node-2 haproxy[27397]: proxy mysqld has no server available!
<129>Jul 24 06:06:35 node-2 haproxy[27397]: 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 24 06:06:35 node-2 haproxy[27397]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:35 node-2 haproxy[27397]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:35 node-2 haproxy[27397]: proxy object-storage has no server available!
<27>Jul 24 06:06:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:37 node-2 multipathd: uevent trigger error
<129>Jul 24 06:06:39 node-2 haproxy[28841]: 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 24 06:06:40 node-2 haproxy[28845]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:40 node-2 haproxy[28845]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:40 node-2 haproxy[28845]: proxy keystone-1 has no server available!
<129>Jul 24 06:06:40 node-2 haproxy[28845]: 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 24 06:06:40 node-2 haproxy[28845]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:40 node-2 haproxy[28845]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:40 node-2 haproxy[28845]: proxy keystone-2 has no server available!
<129>Jul 24 06:06:40 node-2 haproxy[28845]: 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 24 06:06:40 node-2 haproxy[28845]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:41 node-2 haproxy[28845]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:41 node-2 haproxy[28845]: proxy neutron has no server available!
<129>Jul 24 06:06:41 node-2 haproxy[28845]: 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 24 06:06:41 node-2 haproxy[28845]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:41 node-2 haproxy[28845]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:41 node-2 haproxy[28845]: proxy mysqld has no server available!
<129>Jul 24 06:06:41 node-2 haproxy[28845]: 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 24 06:06:41 node-2 haproxy[28845]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:41 node-2 haproxy[28845]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:41 node-2 haproxy[28845]: proxy object-storage has no server available!
<27>Jul 24 06:06:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:43 node-2 multipathd: uevent trigger error
<129>Jul 24 06:06:45 node-2 haproxy[30207]: 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 24 06:06:45 node-2 haproxy[30207]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:45 node-2 haproxy[30207]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:45 node-2 haproxy[30207]: proxy keystone-1 has no server available!
<129>Jul 24 06:06:45 node-2 haproxy[30207]: 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 24 06:06:45 node-2 haproxy[30207]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:45 node-2 haproxy[30207]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:45 node-2 haproxy[30207]: proxy keystone-2 has no server available!
<129>Jul 24 06:06:45 node-2 haproxy[30207]: 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 24 06:06:46 node-2 haproxy[30212]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:46 node-2 haproxy[30212]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:46 node-2 haproxy[30212]: proxy neutron has no server available!
<129>Jul 24 06:06:46 node-2 haproxy[30212]: 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 24 06:06:46 node-2 haproxy[30212]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:46 node-2 haproxy[30212]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:46 node-2 haproxy[30212]: proxy mysqld has no server available!
<129>Jul 24 06:06:46 node-2 haproxy[30212]: 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 24 06:06:46 node-2 haproxy[30212]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:46 node-2 haproxy[30212]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:46 node-2 haproxy[30212]: proxy object-storage has no server available!
<129>Jul 24 06:06:46 node-2 haproxy[30212]: 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 24 06:06:47 node-2 haproxy[30212]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:47 node-2 haproxy[30212]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:47 node-2 haproxy[30212]: proxy aodh has no server available!
<27>Jul 24 06:06:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:48 node-2 multipathd: uevent trigger error
<129>Jul 24 06:06:50 node-2 haproxy[31541]: 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 24 06:06:50 node-2 haproxy[31541]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:51 node-2 haproxy[31552]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:51 node-2 haproxy[31552]: proxy keystone-1 has no server available!
<129>Jul 24 06:06:51 node-2 haproxy[31552]: 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 24 06:06:51 node-2 haproxy[31552]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:51 node-2 haproxy[31552]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:51 node-2 haproxy[31552]: proxy keystone-2 has no server available!
<129>Jul 24 06:06:51 node-2 haproxy[31552]: 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 24 06:06:51 node-2 haproxy[31552]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:51 node-2 haproxy[31552]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:51 node-2 haproxy[31552]: proxy neutron has no server available!
<129>Jul 24 06:06:51 node-2 haproxy[31552]: 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 24 06:06:51 node-2 haproxy[31552]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:51 node-2 haproxy[31552]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:51 node-2 haproxy[31552]: proxy mysqld has no server available!
<129>Jul 24 06:06:51 node-2 haproxy[31552]: 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 24 06:06:52 node-2 haproxy[31552]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:52 node-2 haproxy[31552]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:52 node-2 haproxy[31552]: proxy object-storage has no server available!
<129>Jul 24 06:06:52 node-2 haproxy[31552]: 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 24 06:06:52 node-2 haproxy[31552]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:52 node-2 haproxy[31552]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:52 node-2 haproxy[31552]: proxy aodh has no server available!
<129>Jul 24 06:06:52 node-2 haproxy[31552]: 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 24 06:06:52 node-2 haproxy[31552]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:52 node-2 haproxy[31552]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:52 node-2 haproxy[31552]: proxy ceilometer has no server available!
<27>Jul 24 06:06:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:54 node-2 multipathd: uevent trigger error
<129>Jul 24 06:06:56 node-2 haproxy[449]: 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 24 06:06:56 node-2 haproxy[449]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:56 node-2 haproxy[449]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:56 node-2 haproxy[449]: proxy keystone-1 has no server available!
<129>Jul 24 06:06:56 node-2 haproxy[449]: 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 24 06:06:56 node-2 haproxy[449]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:56 node-2 haproxy[449]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:56 node-2 haproxy[449]: proxy keystone-2 has no server available!
<129>Jul 24 06:06:56 node-2 haproxy[449]: 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 24 06:06:57 node-2 haproxy[453]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:57 node-2 haproxy[453]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:57 node-2 haproxy[453]: proxy neutron has no server available!
<129>Jul 24 06:06:57 node-2 haproxy[453]: 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 24 06:06:57 node-2 haproxy[453]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:57 node-2 haproxy[453]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:57 node-2 haproxy[453]: proxy mysqld has no server available!
<129>Jul 24 06:06:57 node-2 haproxy[453]: 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 24 06:06:57 node-2 haproxy[453]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:57 node-2 haproxy[453]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:57 node-2 haproxy[453]: proxy object-storage has no server available!
<129>Jul 24 06:06:57 node-2 haproxy[453]: 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 24 06:06:57 node-2 haproxy[453]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:58 node-2 haproxy[453]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:58 node-2 haproxy[453]: proxy aodh has no server available!
<129>Jul 24 06:06:58 node-2 haproxy[453]: 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 24 06:06:58 node-2 haproxy[453]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:06:58 node-2 haproxy[453]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:06:58 node-2 haproxy[453]: proxy ceilometer has no server available!
<27>Jul 24 06:06:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:06:59 node-2 multipathd: uevent trigger error
<129>Jul 24 06:07:01 node-2 haproxy[1867]: 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 24 06:07:02 node-2 haproxy[1871]: 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 24 06:07:02 node-2 haproxy[1871]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:02 node-2 haproxy[1871]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:02 node-2 haproxy[1871]: proxy keystone-1 has no server available!
<129>Jul 24 06:07:02 node-2 haproxy[1871]: 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 24 06:07:02 node-2 haproxy[1871]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:02 node-2 haproxy[1871]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:02 node-2 haproxy[1871]: proxy keystone-2 has no server available!
<129>Jul 24 06:07:02 node-2 haproxy[1871]: 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 24 06:07:02 node-2 haproxy[1871]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:02 node-2 haproxy[1871]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:02 node-2 haproxy[1871]: proxy neutron has no server available!
<129>Jul 24 06:07:02 node-2 haproxy[1871]: 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 24 06:07:02 node-2 haproxy[1871]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:03 node-2 haproxy[1871]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:03 node-2 haproxy[1871]: proxy mysqld has no server available!
<129>Jul 24 06:07:03 node-2 haproxy[1871]: 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 24 06:07:03 node-2 haproxy[1871]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:03 node-2 haproxy[1871]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:03 node-2 haproxy[1871]: proxy object-storage has no server available!
<129>Jul 24 06:07:03 node-2 haproxy[1871]: 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 24 06:07:03 node-2 haproxy[1871]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:03 node-2 haproxy[1871]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:03 node-2 haproxy[1871]: proxy aodh has no server available!
<129>Jul 24 06:07:03 node-2 haproxy[1871]: 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 24 06:07:03 node-2 haproxy[1871]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:03 node-2 haproxy[1871]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:03 node-2 haproxy[1871]: proxy ceilometer has no server available!
<27>Jul 24 06:07:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:05 node-2 multipathd: uevent trigger error
<129>Jul 24 06:07:07 node-2 haproxy[3363]: 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 24 06:07:07 node-2 haproxy[3363]: 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 24 06:07:08 node-2 haproxy[3367]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:08 node-2 haproxy[3367]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:08 node-2 haproxy[3367]: proxy keystone-1 has no server available!
<129>Jul 24 06:07:08 node-2 haproxy[3367]: 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 24 06:07:08 node-2 haproxy[3367]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:08 node-2 haproxy[3367]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:08 node-2 haproxy[3367]: proxy keystone-2 has no server available!
<129>Jul 24 06:07:08 node-2 haproxy[3367]: 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 24 06:07:08 node-2 haproxy[3367]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:08 node-2 haproxy[3367]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:08 node-2 haproxy[3367]: proxy glance-api has no server available!
<129>Jul 24 06:07:08 node-2 haproxy[3367]: 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 24 06:07:08 node-2 haproxy[3367]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:08 node-2 haproxy[3367]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:08 node-2 haproxy[3367]: proxy glance-glare has no server available!
<129>Jul 24 06:07:08 node-2 haproxy[3367]: 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 24 06:07:08 node-2 haproxy[3367]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:08 node-2 haproxy[3367]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:08 node-2 haproxy[3367]: proxy neutron has no server available!
<129>Jul 24 06:07:08 node-2 haproxy[3367]: 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 24 06:07:08 node-2 haproxy[3367]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:08 node-2 haproxy[3367]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:08 node-2 haproxy[3367]: proxy glance-registry has no server available!
<129>Jul 24 06:07:09 node-2 haproxy[3367]: 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 24 06:07:09 node-2 haproxy[3367]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:09 node-2 haproxy[3367]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:09 node-2 haproxy[3367]: proxy mysqld has no server available!
<129>Jul 24 06:07:09 node-2 haproxy[3367]: 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 24 06:07:09 node-2 haproxy[3367]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:09 node-2 haproxy[3367]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:09 node-2 haproxy[3367]: proxy object-storage has no server available!
<129>Jul 24 06:07:09 node-2 haproxy[3367]: 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 24 06:07:09 node-2 haproxy[3367]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:09 node-2 haproxy[3367]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:09 node-2 haproxy[3367]: proxy aodh has no server available!
<129>Jul 24 06:07:09 node-2 haproxy[3367]: 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 24 06:07:09 node-2 haproxy[3367]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:09 node-2 haproxy[3367]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:09 node-2 haproxy[3367]: proxy ceilometer has no server available!
<27>Jul 24 06:07:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:10 node-2 multipathd: uevent trigger error
<129>Jul 24 06:07:13 node-2 haproxy[4765]: 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 24 06:07:13 node-2 haproxy[4765]: 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 24 06:07:13 node-2 haproxy[4765]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:13 node-2 haproxy[4765]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:13 node-2 haproxy[4765]: proxy keystone-1 has no server available!
<129>Jul 24 06:07:13 node-2 haproxy[4765]: 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 24 06:07:13 node-2 haproxy[4765]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:13 node-2 haproxy[4765]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:13 node-2 haproxy[4765]: proxy keystone-2 has no server available!
<129>Jul 24 06:07:13 node-2 haproxy[4765]: 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 24 06:07:13 node-2 haproxy[4765]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:13 node-2 haproxy[4765]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:13 node-2 haproxy[4765]: proxy nova-api has no server available!
<129>Jul 24 06:07:14 node-2 haproxy[4771]: 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 24 06:07:14 node-2 haproxy[4771]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:14 node-2 haproxy[4771]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:14 node-2 haproxy[4771]: proxy nova-metadata-api has no server available!
<129>Jul 24 06:07:14 node-2 haproxy[4771]: 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 24 06:07:14 node-2 haproxy[4771]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:14 node-2 haproxy[4771]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:14 node-2 haproxy[4771]: proxy glance-api has no server available!
<129>Jul 24 06:07:14 node-2 haproxy[4771]: 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 24 06:07:14 node-2 haproxy[4771]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:14 node-2 haproxy[4771]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:14 node-2 haproxy[4771]: proxy glance-glare has no server available!
<129>Jul 24 06:07:14 node-2 haproxy[4771]: 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 24 06:07:14 node-2 haproxy[4771]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:14 node-2 haproxy[4771]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:14 node-2 haproxy[4771]: proxy neutron has no server available!
<129>Jul 24 06:07:14 node-2 haproxy[4771]: 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 24 06:07:14 node-2 haproxy[4771]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:14 node-2 haproxy[4771]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:14 node-2 haproxy[4771]: proxy glance-registry has no server available!
<129>Jul 24 06:07:14 node-2 haproxy[4771]: 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 24 06:07:14 node-2 haproxy[4771]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:14 node-2 haproxy[4771]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:14 node-2 haproxy[4771]: proxy mysqld has no server available!
<129>Jul 24 06:07:14 node-2 haproxy[4771]: 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 24 06:07:14 node-2 haproxy[4771]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:14 node-2 haproxy[4771]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:14 node-2 haproxy[4771]: proxy object-storage has no server available!
<129>Jul 24 06:07:15 node-2 haproxy[4771]: 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 24 06:07:15 node-2 haproxy[4771]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:15 node-2 haproxy[4771]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:15 node-2 haproxy[4771]: proxy aodh has no server available!
<129>Jul 24 06:07:15 node-2 haproxy[4771]: 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 24 06:07:15 node-2 haproxy[4771]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:15 node-2 haproxy[4771]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:15 node-2 haproxy[4771]: proxy ceilometer has no server available!
<129>Jul 24 06:07:15 node-2 haproxy[4771]: 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 24 06:07:15 node-2 haproxy[4771]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:15 node-2 haproxy[4771]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:15 node-2 haproxy[4771]: proxy nova-novncproxy has no server available!
<27>Jul 24 06:07:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:16 node-2 multipathd: uevent trigger error
<129>Jul 24 06:07:18 node-2 haproxy[6254]: 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 24 06:07:19 node-2 haproxy[6258]: 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 24 06:07:19 node-2 haproxy[6258]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:19 node-2 haproxy[6258]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:19 node-2 haproxy[6258]: proxy keystone-1 has no server available!
<129>Jul 24 06:07:19 node-2 haproxy[6258]: 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 24 06:07:19 node-2 haproxy[6258]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:19 node-2 haproxy[6258]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:19 node-2 haproxy[6258]: proxy keystone-2 has no server available!
<129>Jul 24 06:07:19 node-2 haproxy[6258]: 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 24 06:07:19 node-2 haproxy[6258]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:19 node-2 haproxy[6258]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:19 node-2 haproxy[6258]: proxy nova-api has no server available!
<129>Jul 24 06:07:19 node-2 haproxy[6258]: 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 24 06:07:19 node-2 haproxy[6258]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:19 node-2 haproxy[6258]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:19 node-2 haproxy[6258]: proxy nova-metadata-api has no server available!
<129>Jul 24 06:07:19 node-2 haproxy[6258]: 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 24 06:07:19 node-2 haproxy[6258]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:19 node-2 haproxy[6258]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:19 node-2 haproxy[6258]: proxy cinder-api has no server available!
<129>Jul 24 06:07:19 node-2 haproxy[6258]: 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 24 06:07:19 node-2 haproxy[6258]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:19 node-2 haproxy[6258]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:19 node-2 haproxy[6258]: proxy glance-api has no server available!
<129>Jul 24 06:07:19 node-2 haproxy[6258]: 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 24 06:07:19 node-2 haproxy[6258]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy glance-glare has no server available!
<129>Jul 24 06:07:20 node-2 haproxy[6258]: 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 24 06:07:20 node-2 haproxy[6258]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy neutron has no server available!
<129>Jul 24 06:07:20 node-2 haproxy[6258]: 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 24 06:07:20 node-2 haproxy[6258]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy glance-registry has no server available!
<129>Jul 24 06:07:20 node-2 haproxy[6258]: 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 24 06:07:20 node-2 haproxy[6258]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy mysqld has no server available!
<129>Jul 24 06:07:20 node-2 haproxy[6258]: 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 24 06:07:20 node-2 haproxy[6258]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy object-storage has no server available!
<129>Jul 24 06:07:20 node-2 haproxy[6258]: 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 24 06:07:20 node-2 haproxy[6258]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy aodh has no server available!
<129>Jul 24 06:07:20 node-2 haproxy[6258]: 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 24 06:07:20 node-2 haproxy[6258]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy ceilometer has no server available!
<129>Jul 24 06:07:20 node-2 haproxy[6258]: 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 24 06:07:20 node-2 haproxy[6258]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:20 node-2 haproxy[6258]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:20 node-2 haproxy[6258]: proxy nova-novncproxy has no server available!
<27>Jul 24 06:07:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:22 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:22 node-2 multipathd: uevent trigger error
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy keystone-1 has no server available!
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy keystone-2 has no server available!
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy nova-api has no server available!
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy nova-metadata-api has no server available!
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy cinder-api has no server available!
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy glance-api has no server available!
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy glance-glare has no server available!
<129>Jul 24 06:07:25 node-2 haproxy[7644]: 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 24 06:07:25 node-2 haproxy[7644]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:25 node-2 haproxy[7644]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:25 node-2 haproxy[7644]: proxy neutron has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy glance-registry has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy mysqld has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy object-storage has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy aodh has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy ceilometer has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy heat-api has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy heat-api-cfn has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy heat-api-cloudwatch has no server available!
<129>Jul 24 06:07:26 node-2 haproxy[7648]: 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 24 06:07:26 node-2 haproxy[7648]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 06:07:26 node-2 haproxy[7648]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 06:07:26 node-2 haproxy[7648]: proxy nova-novncproxy has no server available!
<27>Jul 24 06:07:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:07:44 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 06:08:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:08:10 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 24 06:08:12 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 24 06:08:44 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 06:09:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:09:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:09:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:09:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:09:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:09:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:12 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:11:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:39 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:39 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:39 node-2 multipathd: uevent trigger error
<27>Jul 24 06:11:39 node-2 multipathd: uevent trigger error
<43>Jul 24 06:11:57 node-2 apache2_error [Sun Jul 24 06:11:54.018139 2016] [mpm_event:notice] [pid 19902:tid 139690525120384] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 06:11:57 node-2 apache2_error [Sun Jul 24 06:11:54.018287 2016] [core:notice] [pid 19902:tid 139690525120384] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 06:12:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:06 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:06 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:06 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:06 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:06 node-2 multipathd: uevent trigger error
<27>Jul 24 06:12:06 node-2 multipathd: uevent trigger error
<43>Jul 24 06:12:07 node-2 apache2_error [Sun Jul 24 06:11:57.435159 2016] [mpm_event:notice] [pid 19902:tid 139690525120384] AH00491: caught SIGTERM, shutting down
<43>Jul 24 06:12:07 node-2 apache2_error [Sun Jul 24 06:11:58.525556 2016] [mpm_worker:notice] [pid 20270:tid 139716234475392] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 06:12:07 node-2 apache2_error [Sun Jul 24 06:11:58.525593 2016] [core:notice] [pid 20270:tid 139716234475392] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 06:13:27 node-2 apache2_error [Sun Jul 24 06:13:23.017047 2016] [mpm_worker:notice] [pid 20270:tid 139716234475392] AH00295: caught SIGTERM, shutting down
<43>Jul 24 06:13:27 node-2 apache2_error [Sun Jul 24 06:13:23.759653 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 06:13:27 node-2 apache2_error [Sun Jul 24 06:13:23.759694 2016] [core:notice] [pid 2714:tid 140063329748864] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 06:14:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 24 06:14:17 node-2 apache2_error [Sun Jul 24 06:14:09.767046 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 06:14:17 node-2 apache2_error [Sun Jul 24 06:14:09.961040 2016] [mpm_worker:warn] [pid 2714:tid 140063329748864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 06:14:17 node-2 apache2_error [Sun Jul 24 06:14:09.965400 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 06:14:17 node-2 apache2_error [Sun Jul 24 06:14:09.965413 2016] [core:notice] [pid 2714:tid 140063329748864] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 06:14:55 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:55 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:55 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:55 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:55 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:14:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:15:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:16:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:17:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:17:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:17:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:17:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:17:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:17:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:18:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:18:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:18:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:18:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:18:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:18:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:18:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:01 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:01 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:01 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:01 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:01 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:01 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:18 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:20:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:29 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:29 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:29 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:29 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:29 node-2 multipathd: uevent trigger error
<27>Jul 24 06:20:29 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:28 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:23:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:23:31 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:20 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:20 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:20 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:20 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:20 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:24:41 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:25 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:32 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 24 06:25:32 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 24 06:25:32 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 24 06:25:33 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 24 06:25:34 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 24 06:25:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:34 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:25:48 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:02 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:21 node-2 multipathd: uevent trigger error
<27>Jul 24 06:26:30 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:28:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:28:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:28:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:28:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:28:43 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:18 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:18 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:18 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:18 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:24 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:31 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:29:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:51 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:51 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:51 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:51 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:51 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:29:56 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:08 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:15 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:30:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:10 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:28 node-2 multipathd: uevent trigger error
<27>Jul 24 06:32:33 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 24 06:32:42 node-2 liberasurecode[1804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:42 node-2 liberasurecode[1804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:42 node-2 liberasurecode[1804]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:42 node-2 liberasurecode[1804]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:42 node-2 liberasurecode[1835]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:42 node-2 liberasurecode[1835]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:42 node-2 liberasurecode[1835]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:42 node-2 liberasurecode[1835]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:44 node-2 liberasurecode[2271]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:44 node-2 liberasurecode[2271]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:44 node-2 liberasurecode[2271]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:44 node-2 liberasurecode[2271]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3745]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3745]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3745]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3745]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3906]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3906]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3906]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[3906]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4001]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4001]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4001]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4001]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4190]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4190]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4190]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4190]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4202]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4202]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4202]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:50 node-2 liberasurecode[4202]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4237]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4237]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4237]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4237]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4266]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4266]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4266]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:32:51 node-2 liberasurecode[4266]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 06:33:00 node-2 liberasurecode[5082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:33:00 node-2 liberasurecode[5082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:33:00 node-2 liberasurecode[5082]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:33:00 node-2 liberasurecode[5082]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 06:33:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:33:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:33:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:33:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:33:09 node-2 multipathd: uevent trigger error
<43>Jul 24 06:33:59 node-2 apache2_error [Sun Jul 24 06:33:55.882485 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 06:33:59 node-2 apache2_error [Sun Jul 24 06:33:56.267906 2016] [mpm_worker:warn] [pid 2714:tid 140063329748864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 06:33:59 node-2 apache2_error [Sun Jul 24 06:33:56.272419 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 06:33:59 node-2 apache2_error [Sun Jul 24 06:33:56.272442 2016] [core:notice] [pid 2714:tid 140063329748864] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 06:34:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:37 node-2 multipathd: uevent trigger error
<43>Jul 24 06:34:39 node-2 apache2_error [Sun Jul 24 06:34:33.461490 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 06:34:39 node-2 apache2_error [Sun Jul 24 06:34:33.659036 2016] [mpm_worker:warn] [pid 2714:tid 140063329748864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 06:34:39 node-2 apache2_error [Sun Jul 24 06:34:33.668106 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 06:34:39 node-2 apache2_error [Sun Jul 24 06:34:33.668125 2016] [core:notice] [pid 2714:tid 140063329748864] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 06:34:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:34:45 node-2 multipathd: uevent trigger error
<11>Jul 24 06:35:01 node-2 liberasurecode[24844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:35:01 node-2 liberasurecode[24844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:35:01 node-2 liberasurecode[24844]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:35:01 node-2 liberasurecode[24844]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Jul 24 06:35:19 node-2 apache2_error [Sun Jul 24 06:35:19.537157 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 06:35:19 node-2 apache2_error [Sun Jul 24 06:35:19.735248 2016] [mpm_worker:warn] [pid 2714:tid 140063329748864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 06:35:19 node-2 apache2_error [Sun Jul 24 06:35:19.743922 2016] [mpm_worker:notice] [pid 2714:tid 140063329748864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 06:35:19 node-2 apache2_error [Sun Jul 24 06:35:19.743950 2016] [core:notice] [pid 2714:tid 140063329748864] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 06:35:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:23 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:30 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:30 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:30 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:30 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:34 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 06:35:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:36 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:35:45 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:03 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:26 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:33 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 24 06:36:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:42 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:47 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:52 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:52 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:52 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:52 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:52 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:36:58 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:14 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:27 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:30 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 06:37:39 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:40 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:40 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:40 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:40 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:44 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:44 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:44 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:44 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:49 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:49 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:49 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:49 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:49 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:37:59 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:04 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:04 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:04 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:04 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:38:09 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:37 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:46 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:46 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:46 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:46 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:46 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:57 node-2 multipathd: uevent trigger error
<27>Jul 24 06:39:57 node-2 multipathd: uevent trigger error
<11>Jul 24 06:40:02 node-2 liberasurecode[30785]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:40:02 node-2 liberasurecode[30785]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:40:02 node-2 liberasurecode[30785]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 06:40:02 node-2 liberasurecode[30785]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<129>Jul 24 06:40:06 node-2 haproxy[25463]: 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 24 06:40:07 node-2 haproxy[25463]: 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.
<27>Jul 24 06:40:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:40:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:40:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:40:54 node-2 multipathd: uevent trigger error
<27>Jul 24 06:40:54 node-2 multipathd: uevent trigger error
<129>Jul 24 06:40:57 node-2 haproxy[25463]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 06:41:00 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:00 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:00 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:00 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:00 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:05 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:16 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:17 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:17 node-2 multipathd: uevent trigger error
<27>Jul 24 06:41:17 node-2 multipathd: uevent trigger error
