Jul 26 12:17:46 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8398" x-info="http://www.rsyslog.com"] start
Jul 26 12:17:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 26 12:17:46 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 26 12:17:46 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 26 12:17:46 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 26 12:17:46 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 26 12:17:46 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 26 12:17:46 node-1 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 26 12:17:46 node-1 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=d7b34137-b2da-4234-b36c-097e4706fd76 nomdmonddf nomdmonisw
Jul 26 12:17:46 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 26 12:17:46 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 26 12:17:46 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 26 12:17:46 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 26 12:17:46 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 26 12:17:46 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 26 12:17:46 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 26 12:17:46 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 26 12:17:46 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 26 12:17:46 node-1 kernel: [    0.000000] No AGP bridge found
Jul 26 12:17:46 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 26 12:17:46 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 26 12:17:46 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 26 12:17:46 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 26 12:17:46 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 26 12:17:46 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 26 12:17:46 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 26 12:17:46 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 26 12:17:46 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 26 12:17:46 node-1 kernel: [    0.000000]   2 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000]   3 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000]   4 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000]   5 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000]   6 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000]   7 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000]   8 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000]   9 disabled
Jul 26 12:17:46 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 26 12:17:46 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 26 12:17:46 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 26 12:17:46 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 26 12:17:46 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 26 12:17:46 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 26 12:17:46 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 26 12:17:46 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 26 12:17:46 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 26 12:17:46 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 26 12:17:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 26 12:17:46 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 26 12:17:46 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 26 12:17:46 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 26 12:17:46 node-1 kernel: [    0.000000] Zone ranges:
Jul 26 12:17:46 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 26 12:17:46 node-1 kernel: [    0.000000] Early memory node ranges
Jul 26 12:17:46 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 26 12:17:46 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 26 12:17:46 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 26 12:17:46 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 26 12:17:46 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 26 12:17:46 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 26 12:17:46 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 26 12:17:46 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 26 12:17:46 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 26 12:17:46 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 26 12:17:46 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 26 12:17:46 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 26 12:17:46 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 26 12:17:46 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 26 12:17:46 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 26 12:17:46 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 26 12:17:46 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 26 12:17:46 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 26 12:17:46 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 26 12:17:46 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 26 12:17:46 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 26 12:17:46 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 26 12:17:46 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 26 12:17:46 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 26 12:17:46 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 26 12:17:46 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 26 12:17:46 node-1 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=d7b34137-b2da-4234-b36c-097e4706fd76 nomdmonddf nomdmonisw
Jul 26 12:17:46 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 26 12:17:46 node-1 kernel: [    0.000000] Checking aperture...
Jul 26 12:17:46 node-1 kernel: [    0.000000] No AGP bridge found
Jul 26 12:17:46 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 26 12:17:46 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 26 12:17:46 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 26 12:17:46 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 26 12:17:46 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 26 12:17:46 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 26 12:17:46 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 26 12:17:46 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 26 12:17:46 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 26 12:17:46 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 26 12:17:46 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 26 12:17:46 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 26 12:17:46 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 26 12:17:46 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 26 12:17:46 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 26 12:17:46 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 26 12:17:46 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 26 12:17:46 node-1 kernel: [    0.004000] tsc: Detected 3492.203 MHz processor
Jul 26 12:17:46 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.40 BogoMIPS (lpj=13968812)
Jul 26 12:17:46 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 26 12:17:46 node-1 kernel: [    0.000044] Security Framework initialized
Jul 26 12:17:46 node-1 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 26 12:17:46 node-1 kernel: [    0.000063] Yama: becoming mindful.
Jul 26 12:17:46 node-1 kernel: [    0.001461] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.006348] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.008280] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.008308] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.008601] Initializing cgroup subsys memory
Jul 26 12:17:46 node-1 kernel: [    0.008609] Initializing cgroup subsys devices
Jul 26 12:17:46 node-1 kernel: [    0.008611] Initializing cgroup subsys freezer
Jul 26 12:17:46 node-1 kernel: [    0.008613] Initializing cgroup subsys blkio
Jul 26 12:17:46 node-1 kernel: [    0.008614] Initializing cgroup subsys perf_event
Jul 26 12:17:46 node-1 kernel: [    0.008616] Initializing cgroup subsys hugetlb
Jul 26 12:17:46 node-1 kernel: [    0.008636] CPU: Physical Processor ID: 0
Jul 26 12:17:46 node-1 kernel: [    0.008637] CPU: Processor Core ID: 0
Jul 26 12:17:46 node-1 kernel: [    0.008641] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 26 12:17:46 node-1 kernel: [    0.008641] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 26 12:17:46 node-1 kernel: [    0.009334] mce: CPU supports 22 MCE banks
Jul 26 12:17:46 node-1 kernel: [    0.009362] CPU0: Thermal monitoring enabled (TM1)
Jul 26 12:17:46 node-1 kernel: [    0.009382] process: using mwait in idle threads
Jul 26 12:17:46 node-1 kernel: [    0.009386] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 26 12:17:46 node-1 kernel: [    0.009386] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 26 12:17:46 node-1 kernel: [    0.009386] tlb_flushall_shift: 6
Jul 26 12:17:46 node-1 kernel: [    0.009472] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 26 12:17:46 node-1 kernel: [    0.010196] ACPI: Core revision 20131115
Jul 26 12:17:46 node-1 kernel: [    0.022847] ACPI: All ACPI Tables successfully acquired
Jul 26 12:17:46 node-1 kernel: [    0.022998] ftrace: allocating 28617 entries in 112 pages
Jul 26 12:17:46 node-1 kernel: [    0.031797] dmar: Host address width 46
Jul 26 12:17:46 node-1 kernel: [    0.031799] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 26 12:17:46 node-1 kernel: [    0.031805] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 12:17:46 node-1 kernel: [    0.031807] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 26 12:17:46 node-1 kernel: [    0.031811] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 12:17:46 node-1 kernel: [    0.031813] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 26 12:17:46 node-1 kernel: [    0.031814] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 26 12:17:46 node-1 kernel: [    0.031815] dmar: ATSR flags: 0x0
Jul 26 12:17:46 node-1 kernel: [    0.031816] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 26 12:17:46 node-1 kernel: [    0.031817] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 26 12:17:46 node-1 kernel: [    0.031933] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 26 12:17:46 node-1 kernel: [    0.031934] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 12:17:46 node-1 kernel: [    0.031935] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 12:17:46 node-1 kernel: [    0.031936] HPET id 0 under DRHD base 0xc7ffc000
Jul 26 12:17:46 node-1 kernel: [    0.031938] Your BIOS is broken and requested that x2apic be disabled.
Jul 26 12:17:46 node-1 kernel: [    0.031938] This will slightly decrease performance.
Jul 26 12:17:46 node-1 kernel: [    0.031938] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 26 12:17:46 node-1 kernel: [    0.032369] Enabled IRQ remapping in xapic mode
Jul 26 12:17:46 node-1 kernel: [    0.032370] x2apic not enabled, IRQ remapping is in xapic mode
Jul 26 12:17:46 node-1 kernel: [    0.032374] Switched APIC routing to physical flat.
Jul 26 12:17:46 node-1 kernel: [    0.032996] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 26 12:17:46 node-1 kernel: [    0.072650] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 26 12:17:46 node-1 kernel: [    0.072655] TSC deadline timer enabled
Jul 26 12:17:46 node-1 kernel: [    0.072663] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 26 12:17:46 node-1 kernel: [    0.072669] ... version:                3
Jul 26 12:17:46 node-1 kernel: [    0.072670] ... bit width:              48
Jul 26 12:17:46 node-1 kernel: [    0.072670] ... generic registers:      4
Jul 26 12:17:46 node-1 kernel: [    0.072671] ... value mask:             0000ffffffffffff
Jul 26 12:17:46 node-1 kernel: [    0.072672] ... max period:             0000ffffffffffff
Jul 26 12:17:46 node-1 kernel: [    0.072673] ... fixed-purpose events:   3
Jul 26 12:17:46 node-1 kernel: [    0.072674] ... event mask:             000000070000000f
Jul 26 12:17:46 node-1 kernel: [    0.074097] x86: Booting SMP configuration:
Jul 26 12:17:46 node-1 kernel: [    0.088203] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 26 12:17:46 node-1 kernel: [    0.074099] .... node  #0, CPUs:        #1  #2  #3
Jul 26 12:17:46 node-1 kernel: [    0.116119] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 26 12:17:46 node-1 kernel: [    0.270080] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 26 12:17:46 node-1 kernel: [    0.325700] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 26 12:17:46 node-1 kernel: [    0.382561] x86: Booted up 2 nodes, 16 CPUs
Jul 26 12:17:46 node-1 kernel: [    0.382565] smpboot: Total of 16 processors activated (111762.42 BogoMIPS)
Jul 26 12:17:46 node-1 kernel: [    0.406908] devtmpfs: initialized
Jul 26 12:17:46 node-1 kernel: [    0.410278] EVM: security.selinux
Jul 26 12:17:46 node-1 kernel: [    0.410279] EVM: security.SMACK64
Jul 26 12:17:46 node-1 kernel: [    0.410280] EVM: security.ima
Jul 26 12:17:46 node-1 kernel: [    0.410281] EVM: security.capability
Jul 26 12:17:46 node-1 kernel: [    0.410330] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.411022] pinctrl core: initialized pinctrl subsystem
Jul 26 12:17:46 node-1 kernel: [    0.411084] regulator-dummy: no parameters
Jul 26 12:17:46 node-1 kernel: [    0.411116] RTC time: 12:17:10, date: 07/26/16
Jul 26 12:17:46 node-1 kernel: [    0.411150] NET: Registered protocol family 16
Jul 26 12:17:46 node-1 kernel: [    0.411235] cpuidle: using governor ladder
Jul 26 12:17:46 node-1 kernel: [    0.411236] cpuidle: using governor menu
Jul 26 12:17:46 node-1 kernel: [    0.411269] ACPI: bus type PCI registered
Jul 26 12:17:46 node-1 kernel: [    0.411271] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 26 12:17:46 node-1 kernel: [    0.411318] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 26 12:17:46 node-1 kernel: [    0.411321] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 26 12:17:46 node-1 kernel: [    0.425060] PCI: Using configuration type 1 for base access
Jul 26 12:17:46 node-1 kernel: [    0.426057] bio: create slab <bio-0> at 0
Jul 26 12:17:46 node-1 kernel: [    0.426331] ACPI: Added _OSI(Module Device)
Jul 26 12:17:46 node-1 kernel: [    0.426332] ACPI: Added _OSI(Processor Device)
Jul 26 12:17:46 node-1 kernel: [    0.426334] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 26 12:17:46 node-1 kernel: [    0.426335] ACPI: Added _OSI(Processor Aggregator Device)
Jul 26 12:17:46 node-1 kernel: [    0.439010] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 26 12:17:46 node-1 kernel: [    0.449522] ACPI: Interpreter enabled
Jul 26 12:17:46 node-1 kernel: [    0.449527] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 26 12:17:46 node-1 kernel: [    0.449531] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 26 12:17:46 node-1 kernel: [    0.449534] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 26 12:17:46 node-1 kernel: [    0.449541] ACPI: (supports S0 S4 S5)
Jul 26 12:17:46 node-1 kernel: [    0.449542] ACPI: Using IOAPIC for interrupt routing
Jul 26 12:17:46 node-1 kernel: [    0.449582] HEST: Table parsing has been initialized.
Jul 26 12:17:46 node-1 kernel: [    0.449585] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 26 12:17:46 node-1 kernel: [    0.450136] ACPI: No dock devices found.
Jul 26 12:17:46 node-1 kernel: [    0.461653] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 26 12:17:46 node-1 kernel: [    0.461658] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 12:17:46 node-1 kernel: [    0.461662] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 12:17:46 node-1 kernel: [    0.461688] PCI host bridge to bus 0000:ff
Jul 26 12:17:46 node-1 kernel: [    0.461690] pci_bus 0000:ff: root bus resource [bus ff]
Jul 26 12:17:46 node-1 kernel: [    0.461698] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.461737] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.461767] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.461802] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.461831] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.461860] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.461890] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.461918] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.461947] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.461975] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462001] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462027] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462055] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462081] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462107] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462133] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462162] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462189] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462216] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.462244] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462269] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.462295] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462321] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462351] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.462386] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462417] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462447] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462477] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462508] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462539] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462571] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462604] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462635] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462668] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462701] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462734] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462768] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462797] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462824] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462855] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462887] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462926] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462959] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.462992] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463021] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463050] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463079] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463108] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463141] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463172] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463204] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463233] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463262] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463291] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463320] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463350] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463381] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463437] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 26 12:17:46 node-1 kernel: [    0.463440] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 12:17:46 node-1 kernel: [    0.463443] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 12:17:46 node-1 kernel: [    0.463460] PCI host bridge to bus 0000:7f
Jul 26 12:17:46 node-1 kernel: [    0.463461] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 26 12:17:46 node-1 kernel: [    0.463466] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463493] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.463521] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463550] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463571] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.463595] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.463621] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463646] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463670] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463693] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463715] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463737] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463761] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463782] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463813] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463844] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463866] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463891] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463916] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.463941] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.463963] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.463985] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464008] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464034] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 12:17:46 node-1 kernel: [    0.464067] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464093] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464120] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464146] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464171] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464197] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464223] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464251] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464276] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464304] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464332] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464360] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464390] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464416] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464443] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464471] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464496] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464522] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464551] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464577] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464604] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464631] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464657] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464686] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464713] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464740] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464770] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464795] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464818] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464844] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464869] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464898] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.464924] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.466163] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 26 12:17:46 node-1 kernel: [    0.466167] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 12:17:46 node-1 kernel: [    0.467283] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 12:17:46 node-1 kernel: [    0.467789] PCI host bridge to bus 0000:00
Jul 26 12:17:46 node-1 kernel: [    0.467792] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 26 12:17:46 node-1 kernel: [    0.467796] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 26 12:17:46 node-1 kernel: [    0.467797] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 26 12:17:46 node-1 kernel: [    0.467799] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 26 12:17:46 node-1 kernel: [    0.467800] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 26 12:17:46 node-1 kernel: [    0.467801] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 26 12:17:46 node-1 kernel: [    0.467803] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 26 12:17:46 node-1 kernel: [    0.467809] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 26 12:17:46 node-1 kernel: [    0.467892] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.467923] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.467964] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 26 12:17:46 node-1 kernel: [    0.467983] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.468012] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.468052] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 26 12:17:46 node-1 kernel: [    0.468070] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.468100] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.468140] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 26 12:17:46 node-1 kernel: [    0.468156] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.468226] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.468303] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.468378] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 12:17:46 node-1 kernel: [    0.468382] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 26 12:17:46 node-1 kernel: [    0.468467] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 26 12:17:46 node-1 kernel: [    0.468615] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 26 12:17:46 node-1 kernel: [    0.468633] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 26 12:17:46 node-1 kernel: [    0.468710] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.468765] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 26 12:17:46 node-1 kernel: [    0.468786] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.468842] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.468885] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 26 12:17:46 node-1 kernel: [    0.468911] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.468967] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.469010] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 26 12:17:46 node-1 kernel: [    0.469034] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 26 12:17:46 node-1 kernel: [    0.469052] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 26 12:17:46 node-1 kernel: [    0.469130] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.469179] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 26 12:17:46 node-1 kernel: [    0.469207] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 26 12:17:46 node-1 kernel: [    0.469453] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 26 12:17:46 node-1 kernel: [    0.469459] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 26 12:17:46 node-1 kernel: [    0.469465] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.469471] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.469478] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 26 12:17:46 node-1 kernel: [    0.469509] pci 0000:01:00.0: supports D1 D2
Jul 26 12:17:46 node-1 kernel: [    0.479810] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 12:17:46 node-1 kernel: [    0.479813] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 12:17:46 node-1 kernel: [    0.479815] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 12:17:46 node-1 kernel: [    0.479922] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.479955] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 26 12:17:46 node-1 kernel: [    0.487816] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 12:17:46 node-1 kernel: [    0.487822] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.487826] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 12:17:46 node-1 kernel: [    0.487909] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.487982] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.488077] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.488158] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 12:17:46 node-1 kernel: [    0.488166] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.488170] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 12:17:46 node-1 kernel: [    0.488249] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.488384] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.488437] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 12:17:46 node-1 kernel: [    0.488439] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.488441] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.488490] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.488613] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.488653] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.488772] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.488808] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.488946] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.488982] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 26 12:17:46 node-1 kernel: [    0.489100] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 26 12:17:46 node-1 kernel: [    0.489141] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 12:17:46 node-1 kernel: [    0.489143] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.489145] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.489205] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 26 12:17:46 node-1 kernel: [    0.489268] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.489320] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.489377] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 26 12:17:46 node-1 kernel: [    0.489458] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 26 12:17:46 node-1 kernel: [    0.489564] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 12:17:46 node-1 kernel: [    0.489566] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.489568] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.489624] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 26 12:17:46 node-1 kernel: [    0.489677] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.489726] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.489960] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 12:17:46 node-1 kernel: [    0.489964] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 12:17:46 node-1 kernel: [    0.490025] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 26 12:17:46 node-1 kernel: [    0.490084] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.490133] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.490342] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 12:17:46 node-1 kernel: [    0.490345] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 12:17:46 node-1 kernel: [    0.490404] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 26 12:17:46 node-1 kernel: [    0.490464] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.490517] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 26 12:17:46 node-1 kernel: [    0.490740] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 12:17:46 node-1 kernel: [    0.490744] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 12:17:46 node-1 kernel: [    0.490917] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 12:17:46 node-1 kernel: [    0.490956] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 12:17:46 node-1 kernel: [    0.491030] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 26 12:17:46 node-1 kernel: [    0.491049] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 26 12:17:46 node-1 kernel: [    0.491062] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 26 12:17:46 node-1 kernel: [    0.491075] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 26 12:17:46 node-1 kernel: [    0.491125] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 26 12:17:46 node-1 kernel: [    0.495823] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 12:17:46 node-1 kernel: [    0.495832] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 12:17:46 node-1 kernel: [    0.495885] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 26 12:17:46 node-1 kernel: [    0.496431] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 26 12:17:46 node-1 kernel: [    0.496434] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 12:17:46 node-1 kernel: [    0.496554] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 12:17:46 node-1 kernel: [    0.496660] PCI host bridge to bus 0000:80
Jul 26 12:17:46 node-1 kernel: [    0.496662] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 26 12:17:46 node-1 kernel: [    0.496663] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 26 12:17:46 node-1 kernel: [    0.496665] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 26 12:17:46 node-1 kernel: [    0.496673] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.496736] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.496806] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 12:17:46 node-1 kernel: [    0.496867] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 12:17:46 node-1 kernel: [    0.496872] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 26 12:17:46 node-1 kernel: [    0.496942] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 26 12:17:46 node-1 kernel: [    0.497240] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 26 12:17:46 node-1 kernel: [    0.497271] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 26 12:17:46 node-1 kernel: [    0.497301] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 26 12:17:46 node-1 kernel: [    0.497330] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 26 12:17:46 node-1 kernel: [    0.497359] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 12:17:46 node-1 kernel: [    0.497389] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 12:17:46 node-1 kernel: [    0.497419] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 12:17:46 node-1 kernel: [    0.497449] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 12:17:46 node-1 kernel: [    0.497533] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 26 12:17:46 node-1 kernel: [    0.497538] ACPI: \_SB_.UNC1: notify handler is installed
Jul 26 12:17:46 node-1 kernel: [    0.497539] ACPI: \_SB_.UNC0: notify handler is installed
Jul 26 12:17:46 node-1 kernel: [    0.497554] ACPI: \_SB_.PCI0: notify handler is installed
Jul 26 12:17:46 node-1 kernel: [    0.497607] ACPI: \_SB_.PCI1: notify handler is installed
Jul 26 12:17:46 node-1 kernel: [    0.497686] Found 4 acpi root devices
Jul 26 12:17:46 node-1 kernel: [    0.497803] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 26 12:17:46 node-1 kernel: [    0.497805] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 26 12:17:46 node-1 kernel: [    0.497806] vgaarb: loaded
Jul 26 12:17:46 node-1 kernel: [    0.497807] vgaarb: bridge control possible 0000:0c:00.0
Jul 26 12:17:46 node-1 kernel: [    0.497921] SCSI subsystem initialized
Jul 26 12:17:46 node-1 kernel: [    0.497981] libata version 3.00 loaded.
Jul 26 12:17:46 node-1 kernel: [    0.497996] ACPI: bus type USB registered
Jul 26 12:17:46 node-1 kernel: [    0.498006] usbcore: registered new interface driver usbfs
Jul 26 12:17:46 node-1 kernel: [    0.498011] usbcore: registered new interface driver hub
Jul 26 12:17:46 node-1 kernel: [    0.498033] usbcore: registered new device driver usb
Jul 26 12:17:46 node-1 kernel: [    0.498194] PCI: Using ACPI for IRQ routing
Jul 26 12:17:46 node-1 kernel: [    0.501808] PCI: pci_cache_line_size set to 64 bytes
Jul 26 12:17:46 node-1 kernel: [    0.502019] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 26 12:17:46 node-1 kernel: [    0.502020] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 26 12:17:46 node-1 kernel: [    0.502021] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 26 12:17:46 node-1 kernel: [    0.502085] NetLabel: Initializing
Jul 26 12:17:46 node-1 kernel: [    0.502087] NetLabel:  domain hash size = 128
Jul 26 12:17:46 node-1 kernel: [    0.502088] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 26 12:17:46 node-1 kernel: [    0.502098] NetLabel:  unlabeled traffic allowed by default
Jul 26 12:17:46 node-1 kernel: [    0.502154] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 26 12:17:46 node-1 kernel: [    0.502158] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 26 12:17:46 node-1 kernel: [    0.504214] Switched to clocksource hpet
Jul 26 12:17:46 node-1 kernel: [    0.508179] AppArmor: AppArmor Filesystem Enabled
Jul 26 12:17:46 node-1 kernel: [    0.508193] pnp: PnP ACPI init
Jul 26 12:17:46 node-1 kernel: [    0.508199] ACPI: bus type PNP registered
Jul 26 12:17:46 node-1 kernel: [    0.508313] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508321] pnp 00:01: [dma 4]
Jul 26 12:17:46 node-1 kernel: [    0.508333] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508360] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508380] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508398] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508430] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508484] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508486] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 26 12:17:46 node-1 kernel: [    0.508487] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508489] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508491] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508496] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508498] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 26 12:17:46 node-1 kernel: [    0.508500] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508501] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508503] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508504] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508506] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508507] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 26 12:17:46 node-1 kernel: [    0.508509] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508593] pnp 00:07: [dma 0 disabled]
Jul 26 12:17:46 node-1 kernel: [    0.508622] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508696] pnp 00:08: [dma 0 disabled]
Jul 26 12:17:46 node-1 kernel: [    0.508729] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 12:17:46 node-1 kernel: [    0.508780] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 26 12:17:46 node-1 kernel: [    0.509124] pnp: PnP ACPI: found 10 devices
Jul 26 12:17:46 node-1 kernel: [    0.509126] ACPI: bus type PNP unregistered
Jul 26 12:17:46 node-1 kernel: [    0.515392] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 12:17:46 node-1 kernel: [    0.515396] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 12:17:46 node-1 kernel: [    0.515398] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 12:17:46 node-1 kernel: [    0.515402] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 12:17:46 node-1 kernel: [    0.515404] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515419] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515448] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 12:17:46 node-1 kernel: [    0.515462] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515491] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 12:17:46 node-1 kernel: [    0.515506] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 12:17:46 node-1 kernel: [    0.515534] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 12:17:46 node-1 kernel: [    0.515549] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 12:17:46 node-1 kernel: [    0.515581] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 12:17:46 node-1 kernel: [    0.515582] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515597] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515626] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 12:17:46 node-1 kernel: [    0.515628] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515642] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515671] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 12:17:46 node-1 kernel: [    0.515673] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515675] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515680] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 12:17:46 node-1 kernel: [    0.515681] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515684] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515687] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 12:17:46 node-1 kernel: [    0.515692] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 12:17:46 node-1 kernel: [    0.515700] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 12:17:46 node-1 kernel: [    0.515704] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 12:17:46 node-1 kernel: [    0.515710] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 26 12:17:46 node-1 kernel: [    0.515711] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 26 12:17:46 node-1 kernel: [    0.515712] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 26 12:17:46 node-1 kernel: [    0.515713] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 26 12:17:46 node-1 kernel: [    0.515714] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 26 12:17:46 node-1 kernel: [    0.515714] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 26 12:17:46 node-1 kernel: [    0.515715] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 26 12:17:46 node-1 kernel: [    0.515716] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 26 12:17:46 node-1 kernel: [    0.515717] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515718] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515719] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515720] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515721] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515722] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515722] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515723] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515724] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 26 12:17:46 node-1 kernel: [    0.515725] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515726] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 26 12:17:46 node-1 kernel: [    0.515727] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 26 12:17:46 node-1 kernel: [    0.515728] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 26 12:17:46 node-1 kernel: [    0.515729] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 26 12:17:46 node-1 kernel: [    0.515731] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 26 12:17:46 node-1 kernel: [    0.515732] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 26 12:17:46 node-1 kernel: [    0.515773] NET: Registered protocol family 2
Jul 26 12:17:46 node-1 kernel: [    0.516030] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.516367] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.516512] TCP: Hash tables configured (established 262144 bind 65536)
Jul 26 12:17:46 node-1 kernel: [    0.516555] TCP: reno registered
Jul 26 12:17:46 node-1 kernel: [    0.516583] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.516676] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.516820] NET: Registered protocol family 1
Jul 26 12:17:46 node-1 kernel: [    0.556272] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 26 12:17:46 node-1 kernel: [    0.556279] PCI: CLS 64 bytes, default 64
Jul 26 12:17:46 node-1 kernel: [    0.556321] Trying to unpack rootfs image as initramfs...
Jul 26 12:17:46 node-1 kernel: [    0.775619] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 26 12:17:46 node-1 kernel: [    0.775663] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 26 12:17:46 node-1 kernel: [    0.775665] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 26 12:17:46 node-1 kernel: [    0.776090] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776096] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776101] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776106] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776116] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776127] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776136] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776145] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776153] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776162] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776176] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776182] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776191] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 26 12:17:46 node-1 kernel: [    0.776214] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776221] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776229] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 12:17:46 node-1 kernel: [    0.776305] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 26 12:17:46 node-1 kernel: [    0.776308] Scanning for low memory corruption every 60 seconds
Jul 26 12:17:46 node-1 kernel: [    0.776684] Initialise system trusted keyring
Jul 26 12:17:46 node-1 kernel: [    0.776739] audit: initializing netlink socket (disabled)
Jul 26 12:17:46 node-1 kernel: [    0.776755] type=2000 audit(1469535430.732:1): initialized
Jul 26 12:17:46 node-1 kernel: [    0.794669] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 26 12:17:46 node-1 kernel: [    0.796199] zbud: loaded
Jul 26 12:17:46 node-1 kernel: [    0.796355] VFS: Disk quotas dquot_6.5.2
Jul 26 12:17:46 node-1 kernel: [    0.796392] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 26 12:17:46 node-1 kernel: [    0.796764] fuse init (API version 7.22)
Jul 26 12:17:46 node-1 kernel: [    0.796827] msgmni has been set to 32768
Jul 26 12:17:46 node-1 kernel: [    0.796877] Key type big_key registered
Jul 26 12:17:46 node-1 kernel: [    0.797377] Key type asymmetric registered
Jul 26 12:17:46 node-1 kernel: [    0.797378] Asymmetric key parser 'x509' registered
Jul 26 12:17:46 node-1 kernel: [    0.797400] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 26 12:17:46 node-1 kernel: [    0.797473] io scheduler noop registered
Jul 26 12:17:46 node-1 kernel: [    0.797474] io scheduler deadline registered (default)
Jul 26 12:17:46 node-1 kernel: [    0.797495] io scheduler cfq registered
Jul 26 12:17:46 node-1 kernel: [    0.798004] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    0.798163] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    0.798284] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    0.798394] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    0.798508] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    0.798605] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    0.799003] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 26 12:17:46 node-1 kernel: [    0.799028] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 26 12:17:46 node-1 kernel: [    0.799047] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 26 12:17:46 node-1 kernel: [    0.799056] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799058] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799061] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 26 12:17:46 node-1 kernel: [    0.799066] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799067] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799069] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799070] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799072] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799073] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799075] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799076] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799078] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799079] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799081] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799082] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799084] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 26 12:17:46 node-1 kernel: [    0.799089] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799092] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 26 12:17:46 node-1 kernel: [    0.799107] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799110] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 26 12:17:46 node-1 kernel: [    0.799121] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799122] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 26 12:17:46 node-1 kernel: [    0.799126] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 26 12:17:46 node-1 kernel: [    0.799164] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 26 12:17:46 node-1 kernel: [    0.799170] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 26 12:17:46 node-1 kernel: [    0.799174] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 26 12:17:46 node-1 kernel: [    0.799184] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 26 12:17:46 node-1 kernel: [    0.799224] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 26 12:17:46 node-1 kernel: [    0.799226] vesafb: scrolling: redraw
Jul 26 12:17:46 node-1 kernel: [    0.799227] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 26 12:17:46 node-1 kernel: [    0.819799] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 26 12:17:46 node-1 kernel: [    0.828351] Console: switching to colour frame buffer device 80x30
Jul 26 12:17:46 node-1 kernel: [    0.837048] fb0: VESA VGA frame buffer device
Jul 26 12:17:46 node-1 kernel: [    0.837247] intel_idle: MWAIT substates: 0x2120
Jul 26 12:17:46 node-1 kernel: [    0.837248] intel_idle: v0.4 model 0x3F
Jul 26 12:17:46 node-1 kernel: [    0.837248] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 26 12:17:46 node-1 kernel: [    0.837483] ipmi message handler version 39.2
Jul 26 12:17:46 node-1 kernel: [    0.837759] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 26 12:17:46 node-1 kernel: [    0.838196] ACPI: AC Adapter [P111] (on-line)
Jul 26 12:17:46 node-1 kernel: [    0.843427] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 26 12:17:46 node-1 kernel: [    0.854418] ACPI: Power Button [PWRB]
Jul 26 12:17:46 node-1 kernel: [    0.860161] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 26 12:17:46 node-1 kernel: [    0.871775] ACPI: Power Button [PWRF]
Jul 26 12:17:46 node-1 kernel: [    0.885699] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 26 12:17:46 node-1 kernel: [    0.897348] pstore: Registered erst as persistent store backend
Jul 26 12:17:46 node-1 kernel: [    0.903525] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 26 12:17:46 node-1 kernel: [    0.915459] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 26 12:17:46 node-1 kernel: [    0.942207] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 26 12:17:46 node-1 kernel: [    0.975481] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 26 12:17:46 node-1 kernel: [    0.989553] Linux agpgart interface v0.103
Jul 26 12:17:46 node-1 kernel: [    0.997238] brd: module loaded
Jul 26 12:17:46 node-1 kernel: [    1.004315] loop: module loaded
Jul 26 12:17:46 node-1 kernel: [    1.011083] libphy: Fixed MDIO Bus: probed
Jul 26 12:17:46 node-1 kernel: [    1.017597] tun: Universal TUN/TAP device driver, 1.6
Jul 26 12:17:46 node-1 kernel: [    1.024121] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 26 12:17:46 node-1 kernel: [    1.030681] PPP generic driver version 2.4.2
Jul 26 12:17:46 node-1 kernel: [    1.037124] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 26 12:17:46 node-1 kernel: [    1.043619] ehci-pci: EHCI PCI platform driver
Jul 26 12:17:46 node-1 kernel: [    1.050253] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 26 12:17:46 node-1 kernel: [    1.056769] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 26 12:17:46 node-1 kernel: [    1.069426] ehci-pci 0000:00:1a.0: debug port 2
Jul 26 12:17:46 node-1 kernel: [    1.079683] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 26 12:17:46 node-1 kernel: [    1.079701] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 26 12:17:46 node-1 kernel: [    1.095717] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 26 12:17:46 node-1 kernel: [    1.101856] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 12:17:46 node-1 kernel: [    1.108075] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 12:17:46 node-1 kernel: [    1.120006] usb usb1: Product: EHCI Host Controller
Jul 26 12:17:46 node-1 kernel: [    1.126044] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 12:17:46 node-1 kernel: [    1.132111] usb usb1: SerialNumber: 0000:00:1a.0
Jul 26 12:17:46 node-1 kernel: [    1.138078] hub 1-0:1.0: USB hub found
Jul 26 12:17:46 node-1 kernel: [    1.143850] hub 1-0:1.0: 2 ports detected
Jul 26 12:17:46 node-1 kernel: [    1.149646] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 26 12:17:46 node-1 kernel: [    1.155264] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 26 12:17:46 node-1 kernel: [    1.166250] ehci-pci 0000:00:1d.0: debug port 2
Jul 26 12:17:46 node-1 kernel: [    1.175574] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 26 12:17:46 node-1 kernel: [    1.175577] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 26 12:17:46 node-1 kernel: [    1.191635] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 26 12:17:46 node-1 kernel: [    1.196847] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 12:17:46 node-1 kernel: [    1.202162] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 12:17:46 node-1 kernel: [    1.212760] usb usb2: Product: EHCI Host Controller
Jul 26 12:17:46 node-1 kernel: [    1.218235] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 12:17:46 node-1 kernel: [    1.223794] usb usb2: SerialNumber: 0000:00:1d.0
Jul 26 12:17:46 node-1 kernel: [    1.229317] hub 2-0:1.0: USB hub found
Jul 26 12:17:46 node-1 kernel: [    1.234667] hub 2-0:1.0: 2 ports detected
Jul 26 12:17:46 node-1 kernel: [    1.239973] ehci-platform: EHCI generic platform driver
Jul 26 12:17:46 node-1 kernel: [    1.245205] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 26 12:17:46 node-1 kernel: [    1.250522] ohci-pci: OHCI PCI platform driver
Jul 26 12:17:46 node-1 kernel: [    1.255827] ohci-platform: OHCI generic platform driver
Jul 26 12:17:46 node-1 kernel: [    1.261027] uhci_hcd: USB Universal Host Controller Interface driver
Jul 26 12:17:46 node-1 kernel: [    1.266460] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 26 12:17:46 node-1 kernel: [    1.459416] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 26 12:17:46 node-1 kernel: [    1.771211] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 26 12:17:46 node-1 kernel: [    1.787432] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 26 12:17:46 node-1 kernel: [    1.793043] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 12:17:46 node-1 kernel: [    1.798819] hub 1-1:1.0: USB hub found
Jul 26 12:17:46 node-1 kernel: [    1.804414] hub 1-1:1.0: 6 ports detected
Jul 26 12:17:46 node-1 kernel: [    1.919047] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 26 12:17:46 node-1 kernel: [    2.305371] i8042: No controller found
Jul 26 12:17:46 node-1 kernel: [    2.310911] mousedev: PS/2 mouse device common for all mice
Jul 26 12:17:46 node-1 kernel: [    2.316652] rtc_cmos 00:02: RTC can wake from S4
Jul 26 12:17:46 node-1 kernel: [    2.319535] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 26 12:17:46 node-1 kernel: [    2.319536] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 12:17:46 node-1 kernel: [    2.320184] hub 2-1:1.0: USB hub found
Jul 26 12:17:46 node-1 kernel: [    2.320416] hub 2-1:1.0: 8 ports detected
Jul 26 12:17:46 node-1 kernel: [    2.344950] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 26 12:17:46 node-1 kernel: [    2.350709] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 26 12:17:46 node-1 kernel: [    2.362035] device-mapper: uevent: version 1.0.3
Jul 26 12:17:46 node-1 kernel: [    2.367739] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 26 12:17:46 node-1 kernel: [    2.379115] ledtrig-cpu: registered to indicate activity on CPUs
Jul 26 12:17:46 node-1 kernel: [    2.385084] TCP: cubic registered
Jul 26 12:17:46 node-1 kernel: [    2.390947] NET: Registered protocol family 10
Jul 26 12:17:46 node-1 kernel: [    2.397013] NET: Registered protocol family 17
Jul 26 12:17:46 node-1 kernel: [    2.402786] Key type dns_resolver registered
Jul 26 12:17:46 node-1 kernel: [    2.408875] Loading compiled-in X.509 certificates
Jul 26 12:17:46 node-1 kernel: [    2.415082] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 26 12:17:46 node-1 kernel: [    2.426740] registered taskstats version 1
Jul 26 12:17:46 node-1 kernel: [    2.434835] Key type trusted registered
Jul 26 12:17:46 node-1 kernel: [    2.442464] Key type encrypted registered
Jul 26 12:17:46 node-1 kernel: [    2.447977] AppArmor: AppArmor sha1 policy hashing enabled
Jul 26 12:17:46 node-1 kernel: [    2.453496] IMA: No TPM chip found, activating TPM-bypass!
Jul 26 12:17:46 node-1 kernel: [    2.459589] regulator-dummy: disabling
Jul 26 12:17:46 node-1 kernel: [    2.465102]   Magic number: 8:950:279
Jul 26 12:17:46 node-1 kernel: [    2.470594] event_source tracepoint: hash matches
Jul 26 12:17:46 node-1 kernel: [    2.476058] tty tty16: hash matches
Jul 26 12:17:46 node-1 kernel: [    2.481567] memory memory145: hash matches
Jul 26 12:17:46 node-1 kernel: [    2.486975] rtc_cmos 00:02: setting system clock to 2016-07-26 12:17:12 UTC (1469535432)
Jul 26 12:17:46 node-1 kernel: [    2.499205] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 26 12:17:46 node-1 kernel: [    2.504746] EDD information not available.
Jul 26 12:17:46 node-1 kernel: [    2.510233] PM: Hibernation image not present or could not be loaded.
Jul 26 12:17:46 node-1 kernel: [    2.511111] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 26 12:17:46 node-1 kernel: [    2.522423] Write protecting the kernel read-only data: 12288k
Jul 26 12:17:46 node-1 kernel: [    2.528734] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 26 12:17:46 node-1 kernel: [    2.541441] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 26 12:17:46 node-1 kernel: [    2.573301] device-mapper: multipath: version 1.6.0 loaded
Jul 26 12:17:46 node-1 kernel: [    2.580969] systemd-udevd[216]: starting version 204
Jul 26 12:17:46 node-1 kernel: [    2.598497] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 26 12:17:46 node-1 kernel: [    2.606641] md: linear personality registered for level -1
Jul 26 12:17:46 node-1 kernel: [    2.621531] md: multipath personality registered for level -4
Jul 26 12:17:46 node-1 kernel: [    2.629604] md: raid0 personality registered for level 0
Jul 26 12:17:46 node-1 kernel: [    2.637682] md: raid1 personality registered for level 1
Jul 26 12:17:46 node-1 kernel: [    2.647518] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 26 12:17:46 node-1 kernel: [    2.653738] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 26 12:17:46 node-1 kernel: [    2.660014] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 26 12:17:46 node-1 kernel: [    2.661231] megasas: FW now in Ready state
Jul 26 12:17:46 node-1 kernel: [    2.661628] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.661725] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.661818] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.661933] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.662092] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.662241] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.662364] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.662590] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.662684] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.662783] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.662894] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.663021] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.663144] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.663226] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.663352] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.663451] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.663993] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 26 12:17:46 node-1 kernel: [    2.693070] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 26 12:17:46 node-1 kernel: [    2.706239] 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 26 12:17:46 node-1 kernel: [    2.710414] raid6: sse2x1   10902 MB/s
Jul 26 12:17:46 node-1 kernel: [    2.726720] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 12:17:46 node-1 kernel: [    2.733636] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.733640] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.733644] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.733648] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.733691] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.747114] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 26 12:17:46 node-1 kernel: [    2.753819] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 26 12:17:46 node-1 kernel: [    2.761485] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 26 12:17:46 node-1 kernel: [    2.761499] 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 26 12:17:46 node-1 kernel: [    2.761514] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 12:17:46 node-1 kernel: [    2.761937] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.762066] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.762207] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.762575] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.762865] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 12:17:46 node-1 kernel: [    2.778502] raid6: sse2x2   13309 MB/s
Jul 26 12:17:46 node-1 kernel: [    2.780191] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 26 12:17:46 node-1 kernel: [    2.780193] 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 26 12:17:46 node-1 kernel: [    2.780194] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 12:17:46 node-1 kernel: [    2.846473] raid6: sse2x4    9570 MB/s
Jul 26 12:17:46 node-1 kernel: [    2.860447] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 26 12:17:46 node-1 kernel: [    2.867423] usb 2-1.4: Manufacturer: Avocent
Jul 26 12:17:46 node-1 kernel: [    2.874315] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 26 12:17:46 node-1 kernel: [    2.914183] raid6: avx2x1   14564 MB/s
Jul 26 12:17:46 node-1 kernel: [    2.986130] raid6: avx2x2   18871 MB/s
Jul 26 12:17:46 node-1 kernel: [    3.058060] raid6: avx2x4   21302 MB/s
Jul 26 12:17:46 node-1 kernel: [    3.064272] raid6: using algorithm avx2x4 (21302 MB/s)
Jul 26 12:17:46 node-1 kernel: [    3.070419] raid6: using avx2x2 recovery algorithm
Jul 26 12:17:46 node-1 kernel: [    3.076416] megasas:IOC Init cmd success
Jul 26 12:17:46 node-1 kernel: [    3.076418] Switched to clocksource tsc
Jul 26 12:17:46 node-1 kernel: [    3.078257] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.078294] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.078336] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.078372] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.078459] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.086232] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 26 12:17:46 node-1 kernel: [    3.086235] 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 26 12:17:46 node-1 kernel: [    3.086236] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 12:17:46 node-1 kernel: [    3.086306] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.086339] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.086371] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.086400] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.086470] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 12:17:46 node-1 kernel: [    3.142901] xor: automatically using best checksumming function:
Jul 26 12:17:46 node-1 kernel: [    3.148853] hidraw: raw HID events driver (C) Jiri Kosina
Jul 26 12:17:46 node-1 kernel: [    3.157432] usbcore: registered new interface driver usbhid
Jul 26 12:17:46 node-1 kernel: [    3.163378] usbhid: USB HID core driver
Jul 26 12:17:46 node-1 kernel: [    3.165980] megasas: INIT adapter done
Jul 26 12:17:46 node-1 kernel: [    3.175974] 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 26 12:17:46 node-1 kernel: [    3.185932]    avx       : 35729.000 MB/sec
Jul 26 12:17:46 node-1 kernel: [    3.193486] 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 26 12:17:46 node-1 kernel: [    3.205223] async_tx: api initialized (async)
Jul 26 12:17:46 node-1 kernel: [    3.205259] 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 26 12:17:46 node-1 kernel: [    3.205653] 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 26 12:17:46 node-1 kernel: [    3.205706] 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 26 12:17:46 node-1 kernel: [    3.206008] 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 26 12:17:46 node-1 kernel: [    3.238173] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 26 12:17:46 node-1 kernel: [    3.239680] scsi0 : LSI SAS based MegaRAID driver
Jul 26 12:17:46 node-1 kernel: [    3.247642] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 12:17:46 node-1 kernel: [    3.296269] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 12:17:46 node-1 kernel: [    3.310473] md: raid6 personality registered for level 6
Jul 26 12:17:46 node-1 kernel: [    3.317520] md: raid5 personality registered for level 5
Jul 26 12:17:46 node-1 kernel: [    3.324275] md: raid4 personality registered for level 4
Jul 26 12:17:46 node-1 kernel: [    3.332482] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 26 12:17:46 node-1 kernel: [    3.332693] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 26 12:17:46 node-1 kernel: [    3.333483] sd 0:2:0:0: [sda] Write Protect is off
Jul 26 12:17:46 node-1 kernel: [    3.333487] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 26 12:17:46 node-1 kernel: [    3.333938] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 26 12:17:46 node-1 kernel: [    3.367707]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 26 12:17:46 node-1 kernel: [    3.373383] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 26 12:17:46 node-1 kernel: [    3.386066] md: raid10 personality registered for level 10
Jul 26 12:17:46 node-1 kernel: [    3.440986] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Jul 26 12:17:46 node-1 kernel: [    3.516725] random: lvm urandom read with 27 bits of entropy available
Jul 26 12:17:46 node-1 kernel: [    3.660762] bio: create slab <bio-1> at 1
Jul 26 12:17:46 node-1 kernel: [    4.452386] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 12:17:46 node-1 kernel: [    4.989144] init: plymouth-upstart-bridge main process (571) terminated with status 1
Jul 26 12:17:46 node-1 kernel: [    5.002201] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 12:17:46 node-1 kernel: [    5.144959] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 26 12:17:46 node-1 kernel: [    5.196672] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 26 12:17:46 node-1 kernel: [    5.380593] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 26 12:17:46 node-1 kernel: [    5.417751] random: nonblocking pool is initialized
Jul 26 12:17:46 node-1 kernel: [    5.452386] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 26 12:17:46 node-1 kernel: [    5.522242] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 12:17:46 node-1 kernel: [    5.728829] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 26 12:17:46 node-1 kernel: [    5.757253] XFS (dm-1): Mounting Filesystem
Jul 26 12:17:46 node-1 kernel: [    6.038431] XFS (dm-1): Ending clean mount
Jul 26 12:17:46 node-1 kernel: [    6.115041] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 12:17:46 node-1 kernel: [    6.144553] XFS (dm-2): Mounting Filesystem
Jul 26 12:17:46 node-1 kernel: [    6.266694] XFS (dm-2): Ending clean mount
Jul 26 12:17:46 node-1 kernel: [    6.369547] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 12:17:46 node-1 kernel: [    8.056269] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 26 12:17:46 node-1 kernel: [    8.084412] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 26 12:17:46 node-1 kernel: [    8.301096] systemd-udevd[798]: starting version 204
Jul 26 12:17:46 node-1 kernel: [    8.301200] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 26 12:17:46 node-1 kernel: [    8.301210] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 26 12:17:46 node-1 kernel: [    8.301214] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 26 12:17:46 node-1 kernel: [    8.301218] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 26 12:17:46 node-1 kernel: [    8.492365] power_meter ACPI000D:00: Found ACPI power meter.
Jul 26 12:17:46 node-1 kernel: [    8.492390] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 26 12:17:46 node-1 kernel: [    8.513697] IPMI System Interface driver.
Jul 26 12:17:46 node-1 kernel: [    8.513756] ipmi_si: probing via ACPI
Jul 26 12:17:46 node-1 kernel: [    8.513780] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 26 12:17:46 node-1 kernel: [    8.513781] ipmi_si: Adding ACPI-specified kcs state machine
Jul 26 12:17:46 node-1 kernel: [    8.513796] ipmi_si: probing via SMBIOS
Jul 26 12:17:46 node-1 kernel: [    8.513798] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 12:17:46 node-1 kernel: [    8.513799] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 26 12:17:46 node-1 kernel: [    8.513801] ipmi_si: probing via SPMI
Jul 26 12:17:46 node-1 kernel: [    8.513802] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 12:17:46 node-1 kernel: [    8.513803] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 26 12:17:46 node-1 kernel: [    8.513804] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 26 12:17:46 node-1 kernel: [    8.521352] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 26 12:17:46 node-1 kernel: [    8.521358] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 12:17:46 node-1 kernel: [    8.521361] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 26 12:17:46 node-1 kernel: [    8.521364] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 12:17:46 node-1 kernel: [    8.521442] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 26 12:17:46 node-1 kernel: [    8.540126] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 26 12:17:46 node-1 kernel: [    8.550377] wmi: Mapper loaded
Jul 26 12:17:46 node-1 kernel: [    8.623236] systemd-udevd[818]: renamed network interface eth0 to enp6s0
Jul 26 12:17:46 node-1 kernel: [    8.653706] systemd-udevd[828]: renamed network interface eth2 to enp8s0
Jul 26 12:17:46 node-1 kernel: [    8.654071] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 26 12:17:46 node-1 kernel: [    8.654078] ipmi_si 00:09: IPMI kcs interface initialized
Jul 26 12:17:46 node-1 kernel: [    8.673693] systemd-udevd[819]: renamed network interface eth1 to enp7s0
Jul 26 12:17:46 node-1 kernel: [    8.701749] systemd-udevd[843]: renamed network interface eth3 to enp9s0
Jul 26 12:17:46 node-1 kernel: [    9.052350] type=1400 audit(1469535439.066:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1075 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.052506] type=1400 audit(1469535439.066:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1075 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.052638] type=1400 audit(1469535439.066:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1075 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.062033] type=1400 audit(1469535439.078:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.062180] type=1400 audit(1469535439.078:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1072 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.062306] type=1400 audit(1469535439.078:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1072 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.066857] type=1400 audit(1469535439.082:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1074 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.067004] type=1400 audit(1469535439.082:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1074 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.067128] type=1400 audit(1469535439.082:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1074 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.068391] type=1400 audit(1469535439.082:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1078 comm="apparmor_parser"
Jul 26 12:17:46 node-1 kernel: [    9.615676] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 26 12:17:46 node-1 kernel: [    9.622785] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 26 12:17:46 node-1 kernel: [    9.919517] enic 0000:06:00.0 enp6s0: Link UP
Jul 26 12:17:46 node-1 kernel: [    9.920758] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 26 12:17:46 node-1 kernel: [    9.920764] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 26 12:17:46 node-1 kernel: [   19.507064] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 26 12:17:47 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 26 12:17:48 node-1 kernel: [   37.550064] init: failsafe main process (8425) killed by TERM signal
Jul 26 12:17:48 node-1 dbus[8474]: [system] AppArmor D-Bus mediation is enabled
Jul 26 12:17:48 node-1 kernel: [   37.737197] audit_printk_skb: 30 callbacks suppressed
Jul 26 12:17:48 node-1 kernel: [   37.737199] type=1400 audit(1469535468.244:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8553 comm="apparmor_parser"
Jul 26 12:17:48 node-1 kernel: [   37.737470] type=1400 audit(1469535468.244:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8552 comm="apparmor_parser"
Jul 26 12:17:48 node-1 kernel: [   37.737476] type=1400 audit(1469535468.244:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8552 comm="apparmor_parser"
Jul 26 12:17:48 node-1 kernel: [   37.737478] type=1400 audit(1469535468.244:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8552 comm="apparmor_parser"
Jul 26 12:17:48 node-1 kernel: [   37.737713] type=1400 audit(1469535468.244:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8552 comm="apparmor_parser"
Jul 26 12:17:48 node-1 kernel: [   37.737715] type=1400 audit(1469535468.244:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8552 comm="apparmor_parser"
Jul 26 12:17:48 node-1 kernel: [   37.737828] type=1400 audit(1469535468.244:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8552 comm="apparmor_parser"
Jul 26 12:17:48 node-1 kernel: [   37.833611] type=1400 audit(1469535468.340:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8555 comm="apparmor_parser"
Jul 26 12:17:48 node-1 anacron[8619]: Anacron 2.3 started on 2016-07-26
Jul 26 12:17:48 node-1 cron[8583]: (CRON) INFO (pidfile fd = 3)
Jul 26 12:17:48 node-1 cron[8627]: (CRON) STARTUP (fork ok)
Jul 26 12:17:48 node-1 anacron[8619]: Will run job `cron.daily' in 5 min.
Jul 26 12:17:48 node-1 anacron[8619]: Will run job `cron.weekly' in 10 min.
Jul 26 12:17:48 node-1 anacron[8619]: Will run job `cron.monthly' in 15 min.
Jul 26 12:17:48 node-1 anacron[8619]: Jobs will be executed sequentially
Jul 26 12:17:48 node-1 cron[8627]: (CRON) INFO (Running @reboot jobs)
Jul 26 12:17:48 node-1 multipathd: path checkers start up
Jul 26 12:17:49 node-1 postfix/master[8762]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 26 12:17:52 node-1 puppet-agent[9076]: Reopening log files
Jul 26 12:17:52 node-1 puppet-agent[9076]: Could not request certificate: Connection refused - connect(2)
Jul 26 12:18:01 node-1 CRON[9107]: (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 26 12:18:07 node-1 puppet-user[9348]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 26 12:18:07 node-1 puppet-user[9348]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Jul 26 12:18:08 node-1 puppet-user[9348]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 26 12:18:08 node-1 puppet-user[9348]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 26 12:18:08 node-1 puppet-user[9348]: Finished catalog run in 1.09 seconds
Jul 26 12:18:10 node-1 multipathd: uevent trigger error
Jul 26 12:18:10 node-1 puppet-user[9783]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 12:18:10 node-1 puppet-user[9783]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 26 12:18:10 node-1 puppet-user[9783]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 26 12:18:10 node-1 puppet-user[9783]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 26 12:18:10 node-1 puppet-user[9783]: (/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 26 12:18:10 node-1 puppet-user[9783]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 26 12:18:10 node-1 puppet-user[9783]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 26 12:18:10 node-1 puppet-user[9783]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 26 12:18:10 node-1 puppet-user[9783]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 26 12:18:10 node-1 puppet-user[9783]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 26 12:18:10 node-1 puppet-user[9783]: Finished catalog run in 0.05 seconds
Jul 26 12:18:11 node-1 puppet-user[10251]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 26 12:18:11 node-1 puppet-user[10251]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 26 12:18:12 node-1 puppet-user[10251]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 26 12:18:12 node-1 puppet-user[10251]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 26 12:18:12 node-1 puppet-user[10251]: Finished catalog run in 0.03 seconds
Jul 26 12:18:13 node-1 puppet-user[10721]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 26 12:18:13 node-1 puppet-user[10721]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 26 12:18:14 node-1 puppet-user[10721]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 26 12:18:14 node-1 puppet-user[10721]: Finished catalog run in 0.04 seconds
Jul 26 12:18:15 node-1 puppet-user[11175]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 26 12:18:15 node-1 puppet-user[11175]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Jul 26 12:18:15 node-1 puppet-user[11175]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 26 12:18:15 node-1 puppet-user[11175]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 26 12:18:16 node-1 puppet-user[11175]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 26 12:18:16 node-1 puppet-user[11175]: Finished catalog run in 0.85 seconds
Jul 26 12:18:16 node-1 kernel: [   66.271641] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 12:18:17 node-1 puppet-agent[9076]: Could not run: SIGTERM
Jul 26 12:18:17 node-1 kernel: [   66.665127] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 26 12:18:17 node-1 ec2: 
Jul 26 12:18:17 node-1 ec2: #############################################################
Jul 26 12:18:17 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 26 12:18:17 node-1 ec2: 1024 39:e0:3a:0c:39:cc:94:2b:b3:1d:b1:af:66:b6:10:f4  root@node-1.domain.tld (DSA)
Jul 26 12:18:17 node-1 ec2: 256 4c:15:7f:6f:49:c3:37:3d:c7:06:c4:f6:64:1e:cf:c9  root@node-1.domain.tld (ECDSA)
Jul 26 12:18:17 node-1 ec2: 256 ba:8e:2a:d9:9e:3a:cd:f4:cb:99:86:5c:88:38:9e:7f  root@node-1.domain.tld (ED25519)
Jul 26 12:18:17 node-1 ec2: 2048 18:ff:60:51:4b:b9:b5:d3:95:0a:1c:f7:42:15:d3:f8  root@node-1.domain.tld (RSA)
Jul 26 12:18:17 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 26 12:18:17 node-1 ec2: #############################################################
Jul 26 12:18:17 node-1 puppet-user[11789]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 26 12:18:17 node-1 puppet-user[11789]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Jul 26 12:18:18 node-1 puppet-user[11789]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 26 12:18:18 node-1 puppet-user[11789]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 26 12:18:18 node-1 puppet-user[11789]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 26 12:18:18 node-1 puppet-user[11789]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 26 12:18:18 node-1 puppet-user[11789]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 26 12:18:18 node-1 puppet-user[11789]: Finished catalog run in 0.34 seconds
Jul 26 12:18:19 node-1 puppet-user[12329]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 26 12:18:20 node-1 puppet-user[12329]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Jul 26 12:18:20 node-1 puppet-user[12329]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 26 12:18:20 node-1 kernel: [   69.670671] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 26 12:18:20 node-1 kernel: [   69.670726] 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 26 12:18:20 node-1 puppet-user[12329]: (/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 26 12:18:20 node-1 puppet-user[12329]: Finished catalog run in 0.06 seconds
Jul 26 12:18:21 node-1 puppet-user[12792]: (Scope(Class[main])) MODULAR: sync_time
Jul 26 12:18:21 node-1 puppet-user[12792]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 26 12:18:22 node-1 ntpdate[13215]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 26 12:18:28 node-1 ntpdate[13215]: adjust time server 10.20.0.2 offset -0.234259 sec
Jul 26 12:18:28 node-1 puppet-user[12792]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 26 12:18:28 node-1 puppet-user[12792]: Finished catalog run in 6.18 seconds
Jul 26 12:18:29 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 12:18:29 node-1 nailgun-agent: D, [2016-07-26T12:18:01.762992 #9110] DEBUG -- : Sleep for 28 seconds before sending request
Jul 26 12:18:29 node-1 nailgun-agent: I, [2016-07-26T12:18:29.777490 #9110]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 12:18:30 node-1 nailgun-agent: D, [2016-07-26T12:18:30.211169 #9110] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.284924 #9110] DEBUG -- : Trying to find block devices
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.285067 #9110] DEBUG -- : Found block device: sda
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.285122 #9110] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.285143 #9110] DEBUG -- : Trying to get list of physical devices
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.285287 #9110] DEBUG -- : Getting udev properties for device: sda
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.287396 #9110] 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"=>"0x618e72837273a8901cc7884
Jul 26 12:18:42 node-1 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30305", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.287444 #9110] DEBUG -- : Trying to find out if device sda is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.287484 #9110] DEBUG -- : Device sda removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.287499 #9110] DEBUG -- : Device sda seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.287967 #9110] DEBUG -- : Getting udev properties for device: dm-0
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.289908 #9110] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-dSaCIMmWNBIZNa1gQZZdBlBdoQ3nHYE3F3Equ8Uctg9WIzSv5S5sndY7mMIzr99c /dev/disk/by-uuid/693ea93a-f833-4854-9005-c52b38c29d5e /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-dSaCIMmWNBIZNa1gQZZdBlBdoQ3nHYE3F3Equ8Uctg9WIzSv5S5sndY7mMIzr99c", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"693ea93a-f833-4854-9005-c52b38c29d5e", "ID_FS_UUID_ENC"=>"693ea93a-f833-4854-9005-c52b38c29d5e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19
Jul 26 12:18:42 node-1 nailgun-agent: 224", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.289933 #9110] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.289973 #9110] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.289985 #9110] DEBUG -- : Device dm-0 seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.290016 #9110] DEBUG -- : Getting udev properties for device: dm-1
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.291741 #9110] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-pQGp5afGh80ymCaNOn09nff3Ja4ag85eoVn6UbyyWNYu6dSOh11SobzR460X9n2b /dev/disk/by-uuid/f6233418-07a0-41ef-a9b4-25cc89bb79f2 /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-pQGp5afGh80ymCaNOn09nff3Ja4ag85eoVn6UbyyWNYu6dSOh11SobzR460X9n2b", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f6233418-07a0-41ef-a9b4-25cc89bb79f2", "ID_FS_UUID_ENC"=>"f6233418-07a0-41ef-a9b4-25cc89bb79f2", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36178", "nomdmonddf"=>"1", "nomd
Jul 26 12:18:42 node-1 nailgun-agent: monisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.291775 #9110] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.291801 #9110] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.291813 #9110] DEBUG -- : Device dm-1 seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.291827 #9110] DEBUG -- : Getting udev properties for device: dm-2
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.293435 #9110] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-2MlrquLEudUp6vDvsND2rmHc0RvQxif60WZaM0u7XnRaADoVSfYG2djaHtDA8GaP /dev/disk/by-uuid/cd7fb660-3bd4-4dd9-93aa-34f22eeb2ebf /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-2MlrquLEudUp6vDvsND2rmHc0RvQxif60WZaM0u7XnRaADoVSfYG2djaHtDA8GaP", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cd7fb660-3bd4-4dd9-93aa-34f22eeb2ebf", "ID_FS_UUID_ENC"=>"cd7fb660-3bd4-4dd9-93aa-34f22eeb2ebf", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43
Jul 26 12:18:42 node-1 nailgun-agent: 691", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.293458 #9110] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.293486 #9110] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.293521 #9110] DEBUG -- : Device dm-2 seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.293552 #9110] DEBUG -- : Getting udev properties for device: dm-3
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.295428 #9110] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-FmqZdae7FzFXv0iiluhXmGVrJZXcT5UlHQq7VK8lrb9PNk82f0EJKmQEkToG9ZUW /dev/disk/by-uuid/14bac75e-2a07-4fba-9b55-ae02679ff588 /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-FmqZdae7FzFXv0iiluhXmGVrJZXcT5UlHQq7VK8lrb9PNk82f0EJKmQEkToG9ZUW", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"14bac75e-2a07-4fba-9b55-ae02679ff588", "ID_FS_UUID_ENC"=>"14bac75e-2a07-4fba-9b55-ae02679ff588", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51291", "nomdmond
Jul 26 12:18:42 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.295452 #9110] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.295501 #9110] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.295513 #9110] DEBUG -- : Device dm-3 seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.295527 #9110] DEBUG -- : Getting udev properties for device: dm-4
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.297623 #9110] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-VFFqcx6WBpx8HChxYpV7vxoL4M9yJo4aNhJ9eWit7Faijm6AlxDIOmgehQLCMKLp /dev/disk/by-uuid/56b8dc7e-60ed-468c-96d4-3efac96ec840 /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-VFFqcx6WBpx8HChxYpV7vxoL4M9yJo4aNhJ9eWit7Faijm6AlxDIOmgehQLCMKLp", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"56b8dc7e-60ed-468c-96d4-3efac96ec840", "ID_FS_UUID_ENC"=>"56b8dc7e-60ed-468c-96d4-3efac96ec840", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50533", "nomdmonddf"=>"1", 
Jul 26 12:18:42 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.297670 #9110] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.297698 #9110] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.297711 #9110] DEBUG -- : Device dm-4 seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.297727 #9110] DEBUG -- : Getting udev properties for device: dm-5
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.299514 #9110] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-M5ulxfeVgCMAMoqRrW3kIwo6dXcd2URIWD6t8KeoJhvU39Hcl8BM2bfPbwkrvYhw /dev/disk/by-uuid/d7b34137-b2da-4234-b36c-097e4706fd76 /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-M5ulxfeVgCMAMoqRrW3kIwo6dXcd2URIWD6t8KeoJhvU39Hcl8BM2bfPbwkrvYhw", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d7b34137-b2da-4234-b36c-097e4706fd76", "ID_FS_UUID_ENC"=>"d7b34137-b2da-4234-b36c-097e4706fd76", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52713", "nomdmonddf"=>"1", "nomd
Jul 26 12:18:42 node-1 nailgun-agent: monisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.299577 #9110] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.299611 #9110] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.299624 #9110] DEBUG -- : Device dm-5 seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.299638 #9110] DEBUG -- : Getting udev properties for device: dm-6
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.301597 #9110] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-M5ulxfeVgCMAMoqRrW3kIwo6dXcd2URIb02L3vX3pAHTl3opYhmnNT3ZIS8z6o0o /dev/disk/by-uuid/7cb5a13f-2316-4805-93a3-377a5cb9f64d /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-M5ulxfeVgCMAMoqRrW3kIwo6dXcd2URIb02L3vX3pAHTl3opYhmnNT3ZIS8z6o0o", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"7cb5a13f-2316-4805-93a3-377a5cb9f64d", "ID_FS_UUID_ENC"=>"7cb5a13f-2316-4805-93a3-377a5cb9f64d", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53474", "nomdmonddf"=>"1", "nomdmonisw"
Jul 26 12:18:42 node-1 nailgun-agent: =>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.301641 #9110] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.301680 #9110] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.301694 #9110] DEBUG -- : Device dm-6 seems to be appropriate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.301724 #9110] DEBUG -- : Getting udev properties for device: ram0
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.303345 #9110] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16874", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.303385 #9110] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.303426 #9110] DEBUG -- : Device ram0 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.303445 #9110] DEBUG -- : Getting udev properties for device: ram1
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.305033 #9110] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17436", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.305054 #9110] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.305087 #9110] DEBUG -- : Device ram1 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.305104 #9110] DEBUG -- : Getting udev properties for device: ram2
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.306669 #9110] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"20560", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.306689 #9110] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.306722 #9110] DEBUG -- : Device ram2 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.306740 #9110] DEBUG -- : Getting udev properties for device: ram3
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.308214 #9110] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21191", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.308235 #9110] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.308290 #9110] DEBUG -- : Device ram3 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.308308 #9110] DEBUG -- : Getting udev properties for device: ram4
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.309806 #9110] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21615", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.309840 #9110] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.309870 #9110] DEBUG -- : Device ram4 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.309889 #9110] DEBUG -- : Getting udev properties for device: ram5
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.311430 #9110] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21986", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.311450 #9110] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.311487 #9110] DEBUG -- : Device ram5 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.311506 #9110] DEBUG -- : Getting udev properties for device: ram6
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.313084 #9110] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22349", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.313131 #9110] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.313167 #9110] DEBUG -- : Device ram6 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.313185 #9110] DEBUG -- : Getting udev properties for device: ram7
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.314680 #9110] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22754", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.314704 #9110] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.314741 #9110] DEBUG -- : Device ram7 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.314767 #9110] DEBUG -- : Getting udev properties for device: ram8
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.316303 #9110] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23147", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.316340 #9110] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.316370 #9110] DEBUG -- : Device ram8 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.316387 #9110] DEBUG -- : Getting udev properties for device: ram9
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.317927 #9110] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23429", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.317947 #9110] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.317992 #9110] DEBUG -- : Device ram9 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.318010 #9110] DEBUG -- : Getting udev properties for device: loop0
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.319566 #9110] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14957", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.319588 #9110] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.319619 #9110] DEBUG -- : Device loop0 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.319644 #9110] DEBUG -- : Getting udev properties for device: loop1
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.321196 #9110] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15130", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.321230 #9110] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.321262 #9110] DEBUG -- : Device loop1 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.321279 #9110] DEBUG -- : Getting udev properties for device: loop2
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.323435 #9110] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15235", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.323456 #9110] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.323516 #9110] DEBUG -- : Device loop2 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.323534 #9110] DEBUG -- : Getting udev properties for device: loop3
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.325353 #9110] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15387", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.325377 #9110] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.325420 #9110] DEBUG -- : Device loop3 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.325437 #9110] DEBUG -- : Getting udev properties for device: loop4
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.326994 #9110] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15579", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.327027 #9110] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.327059 #9110] DEBUG -- : Device loop4 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.327077 #9110] DEBUG -- : Getting udev properties for device: loop5
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.328585 #9110] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15832", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.328616 #9110] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.328648 #9110] DEBUG -- : Device loop5 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.328666 #9110] DEBUG -- : Getting udev properties for device: loop6
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.330247 #9110] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15986", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.330269 #9110] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.330317 #9110] DEBUG -- : Device loop6 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.330334 #9110] DEBUG -- : Getting udev properties for device: loop7
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.331881 #9110] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16394", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.331901 #9110] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.331931 #9110] DEBUG -- : Device loop7 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.331958 #9110] DEBUG -- : Getting udev properties for device: ram10
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.337621 #9110] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17825", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.337647 #9110] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.337685 #9110] DEBUG -- : Device ram10 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.337702 #9110] DEBUG -- : Getting udev properties for device: ram11
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.339682 #9110] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18360", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.339703 #9110] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.339731 #9110] DEBUG -- : Device ram11 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.339749 #9110] DEBUG -- : Getting udev properties for device: ram12
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.341388 #9110] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18873", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.341409 #9110] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.341441 #9110] DEBUG -- : Device ram12 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.341459 #9110] DEBUG -- : Getting udev properties for device: ram13
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.342986 #9110] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19251", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.343041 #9110] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.343076 #9110] DEBUG -- : Device ram13 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.343093 #9110] DEBUG -- : Getting udev properties for device: ram14
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.344592 #9110] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19655", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.344614 #9110] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.344695 #9110] DEBUG -- : Device ram14 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.344713 #9110] DEBUG -- : Getting udev properties for device: ram15
Jul 26 12:18:42 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346250 #9110] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19989", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346271 #9110] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346297 #9110] DEBUG -- : Device ram15 removable parameter: "0"
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346388 #9110] 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 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346402 #9110] DEBUG -- : Block device seems to be physical data storage: sda
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346437 #9110] DEBUG -- : Found block device: dm-0
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346464 #9110] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346475 #9110] DEBUG -- : Found block device: dm-1
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346486 #9110] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346497 #9110] DEBUG -- : Found block device: dm-2
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346507 #9110] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346515 #9110] DEBUG -- : Found block device: dm-3
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346566 #9110] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346575 #9110] DEBUG -- : Found block device: dm-4
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346585 #9110] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346594 #9110] DEBUG -- : Found block device: dm-5
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346604 #9110] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346612 #9110] DEBUG -- : Found block device: dm-6
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346621 #9110] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346629 #9110] DEBUG -- : Found block device: ram0
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346639 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346647 #9110] DEBUG -- : Found block device: ram1
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346705 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346714 #9110] DEBUG -- : Found block device: ram2
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346724 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346733 #9110] DEBUG -- : Found block device: ram3
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346742 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346750 #9110] DEBUG -- : Found block device: ram4
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346760 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346768 #9110] DEBUG -- : Found block device: ram5
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346777 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346836 #9110] DEBUG -- : Found block device: ram6
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346846 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346854 #9110] DEBUG -- : Found block device: ram7
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346864 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346872 #9110] DEBUG -- : Found block device: ram8
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346881 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346889 #9110] DEBUG -- : Found block device: ram9
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346899 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346907 #9110] DEBUG -- : Found block device: loop0
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346956 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346966 #9110] DEBUG -- : Found block device: loop1
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346976 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346985 #9110] DEBUG -- : Found block device: loop2
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.346995 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347003 #9110] DEBUG -- : Found block device: loop3
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347013 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347021 #9110] DEBUG -- : Found block device: loop4
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347030 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347038 #9110] DEBUG -- : Found block device: loop5
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347095 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347104 #9110] DEBUG -- : Found block device: loop6
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347114 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347122 #9110] DEBUG -- : Found block device: loop7
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347131 #9110] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347139 #9110] DEBUG -- : Found block device: ram10
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347150 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347157 #9110] DEBUG -- : Found block device: ram11
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347167 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347216 #9110] DEBUG -- : Found block device: ram12
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347226 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347234 #9110] DEBUG -- : Found block device: ram13
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347243 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347251 #9110] DEBUG -- : Found block device: ram14
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347260 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347268 #9110] DEBUG -- : Found block device: ram15
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347277 #9110] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.347304 #9110] 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 26 12:18:42 node-1 nailgun-agent: D, [2016-07-26T12:18:42.510634 #9110] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 26 12:18:42 node-1 nailgun-agent: I, [2016-07-26T12:18:42.510845 #9110]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 26 12:19:01 node-1 CRON[13697]: (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 26 12:19:18 node-1 puppet-user[13727]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 12:19:18 node-1 puppet-user[13727]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Jul 26 12:19:18 node-1 puppet-user[13727]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 26 12:19:18 node-1 puppet-user[13727]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 26 12:19:18 node-1 puppet-user[13727]: Finished catalog run in 0.09 seconds
Jul 26 12:19:20 node-1 puppet-user[14186]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 26 12:19:21 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 12:19:21 node-1 nailgun-agent: I, [2016-07-26T12:19:21.688395 #13700]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 12:19:21 node-1 puppet-user[14186]: Compiled catalog for node-1.domain.tld in environment production in 1.36 seconds
Jul 26 12:19:21 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:22 node-1 puppet-user[14186]: (/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 26 12:19:34 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 12:19:34 node-1 nailgun-agent: I, [2016-07-26T12:19:34.655158 #13700]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 26 12:19:36 node-1 puppet-user[14186]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 26 12:19:36 node-1 puppet-user[14186]: Finished catalog run in 14.78 seconds
Jul 26 12:19:38 node-1 puppet-user[15334]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 26 12:19:38 node-1 puppet-user[15334]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 26 12:19:43 node-1 puppet-user[15334]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 26 12:20:01 node-1 CRON[16957]: (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 26 12:20:15 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 12:20:15 node-1 nailgun-agent: I, [2016-07-26T12:20:15.833315 #16960]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 12:20:17 node-1 puppet-user[15334]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 26 12:20:17 node-1 puppet-user[15334]: Finished catalog run in 38.06 seconds
Jul 26 12:20:18 node-1 puppet-user[17967]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 26 12:20:19 node-1 puppet-user[17967]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Jul 26 12:20:19 node-1 puppet-user[17967]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 26 12:20:19 node-1 puppet-user[17967]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 26 12:20:19 node-1 puppet-user[17967]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 26 12:20:19 node-1 puppet-user[17967]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 26 12:20:19 node-1 puppet-user[17967]: Finished catalog run in 0.11 seconds
Jul 26 12:20:21 node-1 puppet-user[18431]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 26 12:20:22 node-1 puppet-user[18431]: Compiled catalog for node-1.domain.tld in environment production in 0.82 seconds
Jul 26 12:20:22 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 26 12:20:22 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 26 12:20:22 node-1 crontab[18879]: (root) LIST (root)
Jul 26 12:20:22 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 26 12:20:22 node-1 crontab[18880]: (root) REPLACE (root)
Jul 26 12:20:24 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:26 node-1 puppet-user[18431]: (/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 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 26 12:20:27 node-1 puppet-user[18431]: (/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 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 26 12:20:27 node-1 puppet-user[18431]: (/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 26 12:20:27 node-1 puppet-user[18431]: (/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 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 26 12:20:27 node-1 puppet-user[18431]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 26 12:20:27 node-1 puppet-user[18431]: (/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 26 12:20:27 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8398" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 12:20:27 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 26 12:20:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:20:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:21:51 node-1 ntpdate[29865]: no servers can be used, exiting
<27>Jul 26 12:22:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:22:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:41 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:23:53 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 12:23:53 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 12:23:59 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 12:23:59 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 12:24:05 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 12:24:10 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 12:24:10 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 12:24:17 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:17 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:17 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:17 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:17 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:17 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:37 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:37 node-1 multipathd: uevent trigger error
<129>Jul 26 12:24:39 node-1 haproxy[18875]: Server mysqld/node-1 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 26 12:24:39 node-1 haproxy[18875]: Backup Server mysqld/node-2 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 26 12:24:39 node-1 haproxy[18875]: 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 26 12:24:39 node-1 haproxy[18875]: proxy mysqld has no server available!
<27>Jul 26 12:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:45 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:46 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:46 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:46 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:46 node-1 multipathd: uevent trigger error
<129>Jul 26 12:24:48 node-1 haproxy[21632]: Server mysqld/node-1 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 26 12:24:48 node-1 haproxy[21632]: Backup Server mysqld/node-2 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 26 12:24:49 node-1 haproxy[21636]: 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 26 12:24:49 node-1 haproxy[21636]: proxy mysqld has no server available!
<129>Jul 26 12:24:49 node-1 haproxy[21636]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:24:49 node-1 haproxy[21636]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:24:49 node-1 haproxy[21636]: 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 26 12:24:49 node-1 haproxy[21636]: proxy object-storage has no server available!
<27>Jul 26 12:24:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:51 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:51 node-1 multipathd: uevent trigger error
<129>Jul 26 12:24:53 node-1 haproxy[23072]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:24:54 node-1 haproxy[23076]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:24:54 node-1 haproxy[23076]: 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 26 12:24:54 node-1 haproxy[23076]: proxy neutron has no server available!
<129>Jul 26 12:24:54 node-1 haproxy[23076]: Server mysqld/node-1 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 26 12:24:54 node-1 haproxy[23076]: Backup Server mysqld/node-2 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 26 12:24:54 node-1 haproxy[23076]: 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 26 12:24:54 node-1 haproxy[23076]: proxy mysqld has no server available!
<129>Jul 26 12:24:54 node-1 haproxy[23076]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:24:55 node-1 haproxy[23076]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:24:55 node-1 haproxy[23076]: 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 26 12:24:55 node-1 haproxy[23076]: proxy object-storage has no server available!
<27>Jul 26 12:24:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:24:56 node-1 multipathd: uevent trigger error
<129>Jul 26 12:24:59 node-1 haproxy[24546]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:24:59 node-1 haproxy[24546]: Server keystone-1/node-2 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 26 12:24:59 node-1 haproxy[24546]: 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 26 12:24:59 node-1 haproxy[24546]: proxy keystone-1 has no server available!
<129>Jul 26 12:24:59 node-1 haproxy[24546]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:24:59 node-1 haproxy[24546]: Server keystone-2/node-2 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 26 12:25:00 node-1 haproxy[24550]: 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 26 12:25:00 node-1 haproxy[24550]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:00 node-1 haproxy[24550]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:00 node-1 haproxy[24550]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:00 node-1 haproxy[24550]: 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 26 12:25:00 node-1 haproxy[24550]: proxy neutron has no server available!
<129>Jul 26 12:25:00 node-1 haproxy[24550]: Server mysqld/node-1 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 26 12:25:00 node-1 haproxy[24550]: Backup Server mysqld/node-2 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 26 12:25:00 node-1 haproxy[24550]: 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 26 12:25:00 node-1 haproxy[24550]: proxy mysqld has no server available!
<129>Jul 26 12:25:00 node-1 haproxy[24550]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:00 node-1 haproxy[24550]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:01 node-1 haproxy[24550]: 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 26 12:25:01 node-1 haproxy[24550]: proxy object-storage has no server available!
<27>Jul 26 12:25:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:02 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:04 node-1 haproxy[25953]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:04 node-1 haproxy[25953]: Server keystone-1/node-2 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 26 12:25:05 node-1 haproxy[25957]: 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 26 12:25:05 node-1 haproxy[25957]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:05 node-1 haproxy[25957]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:05 node-1 haproxy[25957]: Server keystone-2/node-2 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 26 12:25:05 node-1 haproxy[25957]: 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 26 12:25:05 node-1 haproxy[25957]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:05 node-1 haproxy[25957]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:05 node-1 haproxy[25957]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:05 node-1 haproxy[25957]: 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 26 12:25:05 node-1 haproxy[25957]: proxy neutron has no server available!
<129>Jul 26 12:25:05 node-1 haproxy[25957]: Server mysqld/node-1 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 26 12:25:05 node-1 haproxy[25957]: Backup Server mysqld/node-2 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 26 12:25:05 node-1 haproxy[25957]: 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 26 12:25:05 node-1 haproxy[25957]: proxy mysqld has no server available!
<129>Jul 26 12:25:06 node-1 haproxy[25957]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:06 node-1 haproxy[25957]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:06 node-1 haproxy[25957]: 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 26 12:25:06 node-1 haproxy[25957]: proxy object-storage has no server available!
<129>Jul 26 12:25:06 node-1 haproxy[25957]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:06 node-1 haproxy[25957]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:06 node-1 haproxy[25957]: 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 26 12:25:06 node-1 haproxy[25957]: proxy aodh has no server available!
<27>Jul 26 12:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:08 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:10 node-1 haproxy[27397]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:10 node-1 haproxy[27397]: Server keystone-1/node-2 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 26 12:25:10 node-1 haproxy[27397]: 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 26 12:25:10 node-1 haproxy[27397]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:10 node-1 haproxy[27397]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:10 node-1 haproxy[27397]: Server keystone-2/node-2 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 26 12:25:10 node-1 haproxy[27397]: 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 26 12:25:10 node-1 haproxy[27397]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:10 node-1 haproxy[27397]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:10 node-1 haproxy[27397]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:10 node-1 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 26 12:25:10 node-1 haproxy[27397]: proxy neutron has no server available!
<129>Jul 26 12:25:11 node-1 haproxy[27401]: Server mysqld/node-1 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 26 12:25:11 node-1 haproxy[27401]: Backup Server mysqld/node-2 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 26 12:25:11 node-1 haproxy[27401]: 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 26 12:25:11 node-1 haproxy[27401]: proxy mysqld has no server available!
<129>Jul 26 12:25:11 node-1 haproxy[27401]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:11 node-1 haproxy[27401]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:11 node-1 haproxy[27401]: 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 26 12:25:11 node-1 haproxy[27401]: proxy object-storage has no server available!
<129>Jul 26 12:25:11 node-1 haproxy[27401]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:11 node-1 haproxy[27401]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:11 node-1 haproxy[27401]: 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 26 12:25:11 node-1 haproxy[27401]: proxy aodh has no server available!
<129>Jul 26 12:25:11 node-1 haproxy[27401]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:11 node-1 haproxy[27401]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:12 node-1 haproxy[27401]: 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 26 12:25:12 node-1 haproxy[27401]: proxy ceilometer has no server available!
<27>Jul 26 12:25:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:13 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:15 node-1 haproxy[28817]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:15 node-1 haproxy[28817]: Server keystone-1/node-2 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 26 12:25:15 node-1 haproxy[28817]: 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 26 12:25:15 node-1 haproxy[28817]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:16 node-1 haproxy[28826]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:16 node-1 haproxy[28826]: Server keystone-2/node-2 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 26 12:25:16 node-1 haproxy[28826]: 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 26 12:25:16 node-1 haproxy[28826]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:16 node-1 haproxy[28826]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:16 node-1 haproxy[28826]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:16 node-1 haproxy[28826]: 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 26 12:25:16 node-1 haproxy[28826]: proxy neutron has no server available!
<129>Jul 26 12:25:16 node-1 haproxy[28826]: Server mysqld/node-1 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 26 12:25:16 node-1 haproxy[28826]: Backup Server mysqld/node-2 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 26 12:25:16 node-1 haproxy[28826]: 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 26 12:25:16 node-1 haproxy[28826]: proxy mysqld has no server available!
<129>Jul 26 12:25:16 node-1 haproxy[28826]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:16 node-1 haproxy[28826]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:17 node-1 haproxy[28826]: 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 26 12:25:17 node-1 haproxy[28826]: proxy object-storage has no server available!
<129>Jul 26 12:25:17 node-1 haproxy[28826]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:17 node-1 haproxy[28826]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:17 node-1 haproxy[28826]: 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 26 12:25:17 node-1 haproxy[28826]: proxy aodh has no server available!
<129>Jul 26 12:25:17 node-1 haproxy[28826]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:17 node-1 haproxy[28826]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:17 node-1 haproxy[28826]: 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 26 12:25:17 node-1 haproxy[28826]: proxy ceilometer has no server available!
<27>Jul 26 12:25:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:18 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:20 node-1 haproxy[30320]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:21 node-1 haproxy[30324]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:21 node-1 haproxy[30324]: Server keystone-1/node-2 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 26 12:25:21 node-1 haproxy[30324]: 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 26 12:25:21 node-1 haproxy[30324]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:21 node-1 haproxy[30324]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:21 node-1 haproxy[30324]: Server keystone-2/node-2 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 26 12:25:21 node-1 haproxy[30324]: 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 26 12:25:21 node-1 haproxy[30324]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:21 node-1 haproxy[30324]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:21 node-1 haproxy[30324]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:21 node-1 haproxy[30324]: 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 26 12:25:21 node-1 haproxy[30324]: proxy neutron has no server available!
<129>Jul 26 12:25:21 node-1 haproxy[30324]: Server mysqld/node-1 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 26 12:25:21 node-1 haproxy[30324]: Backup Server mysqld/node-2 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 26 12:25:22 node-1 haproxy[30324]: 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 26 12:25:22 node-1 haproxy[30324]: proxy mysqld has no server available!
<129>Jul 26 12:25:22 node-1 haproxy[30324]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:22 node-1 haproxy[30324]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:22 node-1 haproxy[30324]: 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 26 12:25:22 node-1 haproxy[30324]: proxy object-storage has no server available!
<129>Jul 26 12:25:22 node-1 haproxy[30324]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:22 node-1 haproxy[30324]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:22 node-1 haproxy[30324]: 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 26 12:25:22 node-1 haproxy[30324]: proxy aodh has no server available!
<129>Jul 26 12:25:22 node-1 haproxy[30324]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:22 node-1 haproxy[30324]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:22 node-1 haproxy[30324]: 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 26 12:25:22 node-1 haproxy[30324]: proxy ceilometer has no server available!
<27>Jul 26 12:25:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:24 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:26 node-1 haproxy[31801]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:26 node-1 haproxy[31801]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:26 node-1 haproxy[31801]: Server keystone-1/node-2 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 26 12:25:26 node-1 haproxy[31801]: 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 26 12:25:26 node-1 haproxy[31801]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:26 node-1 haproxy[31801]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:26 node-1 haproxy[31801]: Server keystone-2/node-2 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 26 12:25:27 node-1 haproxy[31805]: 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 26 12:25:27 node-1 haproxy[31805]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:27 node-1 haproxy[31805]: 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 26 12:25:27 node-1 haproxy[31805]: proxy glance-api has no server available!
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:27 node-1 haproxy[31805]: 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 26 12:25:27 node-1 haproxy[31805]: proxy glance-glare has no server available!
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:27 node-1 haproxy[31805]: 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 26 12:25:27 node-1 haproxy[31805]: proxy neutron has no server available!
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:27 node-1 haproxy[31805]: 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 26 12:25:27 node-1 haproxy[31805]: proxy glance-registry has no server available!
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server mysqld/node-1 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 26 12:25:27 node-1 haproxy[31805]: Backup Server mysqld/node-2 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 26 12:25:27 node-1 haproxy[31805]: 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 26 12:25:27 node-1 haproxy[31805]: proxy mysqld has no server available!
<129>Jul 26 12:25:27 node-1 haproxy[31805]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:28 node-1 haproxy[31805]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:28 node-1 haproxy[31805]: 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 26 12:25:28 node-1 haproxy[31805]: proxy object-storage has no server available!
<129>Jul 26 12:25:28 node-1 haproxy[31805]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:28 node-1 haproxy[31805]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:28 node-1 haproxy[31805]: 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 26 12:25:28 node-1 haproxy[31805]: proxy aodh has no server available!
<129>Jul 26 12:25:28 node-1 haproxy[31805]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:28 node-1 haproxy[31805]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:28 node-1 haproxy[31805]: 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 26 12:25:28 node-1 haproxy[31805]: proxy ceilometer has no server available!
<27>Jul 26 12:25:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:29 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:32 node-1 haproxy[1020]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:32 node-1 haproxy[1020]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:32 node-1 haproxy[1020]: Server keystone-1/node-2 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 26 12:25:32 node-1 haproxy[1020]: 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 26 12:25:32 node-1 haproxy[1020]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:32 node-1 haproxy[1020]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:32 node-1 haproxy[1020]: Server keystone-2/node-2 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 26 12:25:32 node-1 haproxy[1020]: 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 26 12:25:32 node-1 haproxy[1020]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:32 node-1 haproxy[1020]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server nova-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:33 node-1 haproxy[1024]: 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 26 12:25:33 node-1 haproxy[1024]: proxy nova-api has no server available!
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:33 node-1 haproxy[1024]: 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 26 12:25:33 node-1 haproxy[1024]: proxy nova-metadata-api has no server available!
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:33 node-1 haproxy[1024]: 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 26 12:25:33 node-1 haproxy[1024]: proxy glance-api has no server available!
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:33 node-1 haproxy[1024]: 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 26 12:25:33 node-1 haproxy[1024]: proxy glance-glare has no server available!
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:33 node-1 haproxy[1024]: 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 26 12:25:33 node-1 haproxy[1024]: proxy neutron has no server available!
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:33 node-1 haproxy[1024]: 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 26 12:25:33 node-1 haproxy[1024]: proxy glance-registry has no server available!
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server mysqld/node-1 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 26 12:25:33 node-1 haproxy[1024]: Backup Server mysqld/node-2 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 26 12:25:33 node-1 haproxy[1024]: 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 26 12:25:33 node-1 haproxy[1024]: proxy mysqld has no server available!
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:33 node-1 haproxy[1024]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:34 node-1 haproxy[1024]: 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 26 12:25:34 node-1 haproxy[1024]: proxy object-storage has no server available!
<129>Jul 26 12:25:34 node-1 haproxy[1024]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:34 node-1 haproxy[1024]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:34 node-1 haproxy[1024]: 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 26 12:25:34 node-1 haproxy[1024]: proxy aodh has no server available!
<129>Jul 26 12:25:34 node-1 haproxy[1024]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:34 node-1 haproxy[1024]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:34 node-1 haproxy[1024]: 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 26 12:25:34 node-1 haproxy[1024]: proxy ceilometer has no server available!
<129>Jul 26 12:25:34 node-1 haproxy[1024]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:34 node-1 haproxy[1024]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:34 node-1 haproxy[1024]: 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 26 12:25:34 node-1 haproxy[1024]: proxy nova-novncproxy has no server available!
<27>Jul 26 12:25:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:35 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server keystone-1/node-2 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 26 12:25:38 node-1 haproxy[2434]: 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 26 12:25:38 node-1 haproxy[2434]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server keystone-2/node-2 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 26 12:25:38 node-1 haproxy[2434]: 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 26 12:25:38 node-1 haproxy[2434]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server nova-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:38 node-1 haproxy[2434]: 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 26 12:25:38 node-1 haproxy[2434]: proxy nova-api has no server available!
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:38 node-1 haproxy[2434]: 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 26 12:25:38 node-1 haproxy[2434]: proxy nova-metadata-api has no server available!
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server cinder-api/node-1 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 26 12:25:38 node-1 haproxy[2434]: Backup Server cinder-api/node-2 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 26 12:25:38 node-1 haproxy[2434]: 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 26 12:25:38 node-1 haproxy[2434]: proxy cinder-api has no server available!
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:38 node-1 haproxy[2434]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:38 node-1 haproxy[2434]: 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 26 12:25:38 node-1 haproxy[2434]: proxy glance-api has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:39 node-1 haproxy[2438]: 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 26 12:25:39 node-1 haproxy[2438]: proxy glance-glare has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:39 node-1 haproxy[2438]: 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 26 12:25:39 node-1 haproxy[2438]: proxy neutron has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:39 node-1 haproxy[2438]: 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 26 12:25:39 node-1 haproxy[2438]: proxy glance-registry has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server mysqld/node-1 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 26 12:25:39 node-1 haproxy[2438]: Backup Server mysqld/node-2 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 26 12:25:39 node-1 haproxy[2438]: 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 26 12:25:39 node-1 haproxy[2438]: proxy mysqld has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:39 node-1 haproxy[2438]: 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 26 12:25:39 node-1 haproxy[2438]: proxy object-storage has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:39 node-1 haproxy[2438]: 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 26 12:25:39 node-1 haproxy[2438]: proxy aodh has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:39 node-1 haproxy[2438]: 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 26 12:25:39 node-1 haproxy[2438]: proxy ceilometer has no server available!
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:39 node-1 haproxy[2438]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:40 node-1 haproxy[2438]: 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 26 12:25:40 node-1 haproxy[2438]: proxy nova-novncproxy has no server available!
<27>Jul 26 12:25:41 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:41 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:41 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:41 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:41 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:41 node-1 multipathd: uevent trigger error
<129>Jul 26 12:25:43 node-1 haproxy[3924]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server keystone-1/node-2 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy keystone-1 has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server keystone-2/node-2 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy keystone-2 has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server nova-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy nova-api has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy nova-metadata-api has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server cinder-api/node-1 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 26 12:25:44 node-1 haproxy[3931]: Backup Server cinder-api/node-2 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy cinder-api has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server glance-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy glance-api has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy glance-glare has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server neutron/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy neutron has no server available!
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:44 node-1 haproxy[3931]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:44 node-1 haproxy[3931]: 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 26 12:25:44 node-1 haproxy[3931]: proxy glance-registry has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server mysqld/node-1 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 26 12:25:45 node-1 haproxy[3931]: Backup Server mysqld/node-2 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy mysqld has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server object-storage/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy object-storage has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server aodh/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy aodh has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy ceilometer has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server heat-api/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy heat-api has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy heat-api-cfn has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy heat-api-cloudwatch has no server available!
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 12:25:45 node-1 haproxy[3931]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection 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 26 12:25:45 node-1 haproxy[3931]: 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 26 12:25:45 node-1 haproxy[3931]: proxy nova-novncproxy has no server available!
<27>Jul 26 12:25:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:25:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:26:02 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 12:26:27 node-1 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 26 12:26:29 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 26 12:26:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:27:10 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 12:27:27 node-1 multipathd: uevent trigger error
<27>Jul 26 12:27:27 node-1 multipathd: uevent trigger error
<27>Jul 26 12:27:27 node-1 multipathd: uevent trigger error
<27>Jul 26 12:27:27 node-1 multipathd: uevent trigger error
<27>Jul 26 12:27:27 node-1 multipathd: uevent trigger error
<27>Jul 26 12:27:27 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:29:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 26 12:30:08 node-1 apache2_error [Tue Jul 26 12:30:03.139674 2016] [mpm_event:notice] [pid 14586:tid 140285498382208] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 12:30:08 node-1 apache2_error [Tue Jul 26 12:30:03.139821 2016] [core:notice] [pid 14586:tid 140285498382208] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 26 12:30:08 node-1 apache2_error [Tue Jul 26 12:30:06.159674 2016] [mpm_event:notice] [pid 14586:tid 140285498382208] AH00491: caught SIGTERM, shutting down
<43>Jul 26 12:30:08 node-1 apache2_error [Tue Jul 26 12:30:07.253876 2016] [mpm_worker:notice] [pid 15061:tid 140020998588288] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 12:30:08 node-1 apache2_error [Tue Jul 26 12:30:07.253918 2016] [core:notice] [pid 15061:tid 140020998588288] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 12:30:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:16 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:16 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:16 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:16 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:16 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:19 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:19 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:20 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:20 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:20 node-1 multipathd: uevent trigger error
<27>Jul 26 12:30:20 node-1 multipathd: uevent trigger error
<43>Jul 26 12:31:38 node-1 apache2_error [Tue Jul 26 12:31:32.163297 2016] [mpm_worker:notice] [pid 15061:tid 140020998588288] AH00295: caught SIGTERM, shutting down
<43>Jul 26 12:31:38 node-1 apache2_error [Tue Jul 26 12:31:32.922568 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 12:31:38 node-1 apache2_error [Tue Jul 26 12:31:32.922600 2016] [core:notice] [pid 30880:tid 139960615737216] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 26 12:32:18 node-1 apache2_error [Tue Jul 26 12:32:17.627846 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 12:32:18 node-1 apache2_error [Tue Jul 26 12:32:17.823931 2016] [mpm_worker:warn] [pid 30880:tid 139960615737216] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 12:32:18 node-1 apache2_error [Tue Jul 26 12:32:17.828499 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 12:32:18 node-1 apache2_error [Tue Jul 26 12:32:17.828524 2016] [core:notice] [pid 30880:tid 139960615737216] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 12:33:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:33:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:07 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:07 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:07 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:07 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:07 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:07 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:33:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:31 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:34:49 node-1 multipathd: uevent trigger error
<27>Jul 26 12:35:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:35:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:35:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:35:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:35:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:36:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:37:01 node-1 multipathd: uevent trigger error
<27>Jul 26 12:37:01 node-1 multipathd: uevent trigger error
<27>Jul 26 12:37:01 node-1 multipathd: uevent trigger error
<27>Jul 26 12:37:01 node-1 multipathd: uevent trigger error
<27>Jul 26 12:37:01 node-1 multipathd: uevent trigger error
<27>Jul 26 12:37:01 node-1 multipathd: uevent trigger error
<27>Jul 26 12:37:01 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:02 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:24 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:38:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:39:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:41:04 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:04 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:04 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:04 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:04 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:04 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:22 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:54 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:54 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:54 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:54 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:54 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:54 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:41:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:42:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:42:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:42:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:42:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:42:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:42:42 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:29 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:44 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:44 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:44 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:44 node-1 multipathd: uevent trigger error
<27>Jul 26 12:43:44 node-1 multipathd: uevent trigger error
<27>Jul 26 12:44:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:44:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:44:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:44:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:44:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:45:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:46:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:46:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:46:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:46:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:46:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:46:28 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:13 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:47:18 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:48:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:14 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:14 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:14 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:14 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:14 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:32 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:32 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:32 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:32 node-1 multipathd: uevent trigger error
<27>Jul 26 12:48:32 node-1 multipathd: uevent trigger error
<27>Jul 26 12:49:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:49:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:49:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:49:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:49:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:30 node-1 multipathd: uevent trigger error
<27>Jul 26 12:50:30 node-1 multipathd: uevent trigger error
<11>Jul 26 12:50:44 node-1 liberasurecode[22997]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:44 node-1 liberasurecode[22997]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:44 node-1 liberasurecode[22997]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:44 node-1 liberasurecode[22997]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:44 node-1 liberasurecode[23023]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:44 node-1 liberasurecode[23023]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:44 node-1 liberasurecode[23023]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:44 node-1 liberasurecode[23023]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:46 node-1 liberasurecode[23455]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:46 node-1 liberasurecode[23455]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:46 node-1 liberasurecode[23455]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:46 node-1 liberasurecode[23455]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24100]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24100]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24100]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24100]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24143]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24143]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24143]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24143]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24187]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24187]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24187]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24187]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24263]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24263]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24263]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24263]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24295]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24295]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24295]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24295]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24307]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:50:52 node-1 liberasurecode[24307]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 12:51:01 node-1 liberasurecode[26289]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:51:01 node-1 liberasurecode[26289]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:51:01 node-1 liberasurecode[26289]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:51:01 node-1 liberasurecode[26289]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 12:51:10 node-1 multipathd: uevent trigger error
<27>Jul 26 12:51:10 node-1 multipathd: uevent trigger error
<27>Jul 26 12:51:10 node-1 multipathd: uevent trigger error
<27>Jul 26 12:51:10 node-1 multipathd: uevent trigger error
<27>Jul 26 12:51:10 node-1 multipathd: uevent trigger error
<27>Jul 26 12:51:10 node-1 multipathd: uevent trigger error
<27>Jul 26 12:51:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 26 12:52:00 node-1 apache2_error [Tue Jul 26 12:51:59.390113 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 12:52:00 node-1 apache2_error [Tue Jul 26 12:51:59.771220 2016] [mpm_worker:warn] [pid 30880:tid 139960615737216] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 12:52:00 node-1 apache2_error [Tue Jul 26 12:51:59.775417 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 12:52:00 node-1 apache2_error [Tue Jul 26 12:51:59.775443 2016] [core:notice] [pid 30880:tid 139960615737216] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 26 12:52:40 node-1 apache2_error [Tue Jul 26 12:52:36.801007 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 12:52:40 node-1 apache2_error [Tue Jul 26 12:52:38.312175 2016] [mpm_worker:warn] [pid 30880:tid 139960615737216] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 12:52:40 node-1 apache2_error [Tue Jul 26 12:52:38.322244 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 12:52:40 node-1 apache2_error [Tue Jul 26 12:52:38.322274 2016] [core:notice] [pid 30880:tid 139960615737216] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 12:52:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:52:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:26 node-1 multipathd: uevent trigger error
<43>Jul 26 12:53:30 node-1 apache2_error [Tue Jul 26 12:53:22.597169 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 12:53:30 node-1 apache2_error [Tue Jul 26 12:53:22.795901 2016] [mpm_worker:warn] [pid 30880:tid 139960615737216] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 12:53:30 node-1 apache2_error [Tue Jul 26 12:53:22.805014 2016] [mpm_worker:notice] [pid 30880:tid 139960615737216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 12:53:30 node-1 apache2_error [Tue Jul 26 12:53:22.805057 2016] [core:notice] [pid 30880:tid 139960615737216] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 12:53:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:33 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:39 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:39 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:39 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:39 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:39 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:53:47 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 12:54:26 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:34 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 26 12:54:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:48 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:53 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:53 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:53 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:53 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:53 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:53 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:58 node-1 multipathd: uevent trigger error
<27>Jul 26 12:54:59 node-1 multipathd: uevent trigger error
<11>Jul 26 12:55:01 node-1 liberasurecode[13219]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:55:01 node-1 liberasurecode[13219]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:55:01 node-1 liberasurecode[13219]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 12:55:01 node-1 liberasurecode[13219]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 12:55:10 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 12:55:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:11 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:38 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:38 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:38 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:38 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:38 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:43 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:55:56 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:03 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:08 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:21 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:21 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:21 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:21 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:21 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:21 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:35 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:40 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:45 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:45 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:45 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:45 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:45 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:45 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:50 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:55 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:55 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:55 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:55 node-1 multipathd: uevent trigger error
<27>Jul 26 12:56:55 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:00 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:05 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:09 node-1 multipathd: uevent trigger error
<27>Jul 26 12:57:09 node-1 multipathd: uevent trigger error
