Jul 24 16:02:24 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8407" x-info="http://www.rsyslog.com"] start
Jul 24 16:02:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 24 16:02:24 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 24 16:02:24 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 24 16:02:24 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 24 16:02:24 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 24 16:02:24 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 24 16:02:24 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 24 16:02:24 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=b79bf4c1-c9fa-487c-beda-39352777658b nomdmonddf nomdmonisw
Jul 24 16:02:24 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 24 16:02:24 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 24 16:02:24 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 24 16:02:24 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 24 16:02:24 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 24 16:02:24 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 24 16:02:24 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 24 16:02:24 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 24 16:02:24 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 24 16:02:24 node-1 kernel: [    0.000000] No AGP bridge found
Jul 24 16:02:24 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 24 16:02:24 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 24 16:02:24 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 24 16:02:24 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 24 16:02:24 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 24 16:02:24 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 24 16:02:24 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 24 16:02:24 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 24 16:02:24 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 24 16:02:24 node-1 kernel: [    0.000000]   2 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000]   3 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000]   4 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000]   5 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000]   6 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000]   7 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000]   8 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000]   9 disabled
Jul 24 16:02:24 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 24 16:02:24 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 24 16:02:24 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 24 16:02:24 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 24 16:02:24 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 24 16:02:24 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 24 16:02:24 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 24 16:02:24 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 24 16:02:24 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 24 16:02:24 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 24 16:02:24 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 24 16:02:24 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 24 16:02:24 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 24 16:02:24 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 24 16:02:24 node-1 kernel: [    0.000000] Zone ranges:
Jul 24 16:02:24 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 24 16:02:24 node-1 kernel: [    0.000000] Early memory node ranges
Jul 24 16:02:24 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 24 16:02:24 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 24 16:02:24 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 24 16:02:24 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 24 16:02:24 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 24 16:02:24 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 24 16:02:24 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 24 16:02:24 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 24 16:02:24 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 24 16:02:24 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 24 16:02:24 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 24 16:02:24 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 24 16:02:24 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 24 16:02:24 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 24 16:02:24 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 24 16:02:24 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 24 16:02:24 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 24 16:02:24 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 24 16:02:24 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 24 16:02:24 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 24 16:02:24 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 24 16:02:24 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 24 16:02:24 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 24 16:02:24 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 24 16:02:24 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 24 16:02:24 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 24 16:02:24 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=b79bf4c1-c9fa-487c-beda-39352777658b nomdmonddf nomdmonisw
Jul 24 16:02:24 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 24 16:02:24 node-1 kernel: [    0.000000] Checking aperture...
Jul 24 16:02:24 node-1 kernel: [    0.000000] No AGP bridge found
Jul 24 16:02:24 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 24 16:02:24 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 24 16:02:24 node-1 kernel: [    0.000000] Memory: 32653312K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 24 16:02:24 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 24 16:02:24 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 24 16:02:24 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 24 16:02:24 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 24 16:02:24 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 24 16:02:24 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 24 16:02:24 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 24 16:02:24 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 24 16:02:24 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 24 16:02:24 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 24 16:02:24 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 24 16:02:24 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 24 16:02:24 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 24 16:02:24 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 24 16:02:24 node-1 kernel: [    0.004000] tsc: Detected 3491.766 MHz processor
Jul 24 16:02:24 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.53 BogoMIPS (lpj=13967064)
Jul 24 16:02:24 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 24 16:02:24 node-1 kernel: [    0.000042] Security Framework initialized
Jul 24 16:02:24 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Jul 24 16:02:24 node-1 kernel: [    0.000062] Yama: becoming mindful.
Jul 24 16:02:24 node-1 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.006417] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.008346] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.008375] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.008653] Initializing cgroup subsys memory
Jul 24 16:02:24 node-1 kernel: [    0.008661] Initializing cgroup subsys devices
Jul 24 16:02:24 node-1 kernel: [    0.008663] Initializing cgroup subsys freezer
Jul 24 16:02:24 node-1 kernel: [    0.008665] Initializing cgroup subsys blkio
Jul 24 16:02:24 node-1 kernel: [    0.008666] Initializing cgroup subsys perf_event
Jul 24 16:02:24 node-1 kernel: [    0.008668] Initializing cgroup subsys hugetlb
Jul 24 16:02:24 node-1 kernel: [    0.008688] CPU: Physical Processor ID: 0
Jul 24 16:02:24 node-1 kernel: [    0.008689] CPU: Processor Core ID: 0
Jul 24 16:02:24 node-1 kernel: [    0.008693] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 24 16:02:24 node-1 kernel: [    0.008693] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 24 16:02:24 node-1 kernel: [    0.009387] mce: CPU supports 22 MCE banks
Jul 24 16:02:24 node-1 kernel: [    0.009414] CPU0: Thermal monitoring enabled (TM1)
Jul 24 16:02:24 node-1 kernel: [    0.009435] process: using mwait in idle threads
Jul 24 16:02:24 node-1 kernel: [    0.009438] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 24 16:02:24 node-1 kernel: [    0.009438] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 24 16:02:24 node-1 kernel: [    0.009438] tlb_flushall_shift: 6
Jul 24 16:02:24 node-1 kernel: [    0.009528] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 24 16:02:24 node-1 kernel: [    0.010251] ACPI: Core revision 20131115
Jul 24 16:02:24 node-1 kernel: [    0.022955] ACPI: All ACPI Tables successfully acquired
Jul 24 16:02:24 node-1 kernel: [    0.023115] ftrace: allocating 28617 entries in 112 pages
Jul 24 16:02:24 node-1 kernel: [    0.031924] dmar: Host address width 46
Jul 24 16:02:24 node-1 kernel: [    0.031926] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 24 16:02:24 node-1 kernel: [    0.031932] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 16:02:24 node-1 kernel: [    0.031934] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 24 16:02:24 node-1 kernel: [    0.031938] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 16:02:24 node-1 kernel: [    0.031940] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 24 16:02:24 node-1 kernel: [    0.031941] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 24 16:02:24 node-1 kernel: [    0.031942] dmar: ATSR flags: 0x0
Jul 24 16:02:24 node-1 kernel: [    0.031943] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 24 16:02:24 node-1 kernel: [    0.031944] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 24 16:02:24 node-1 kernel: [    0.032060] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 24 16:02:24 node-1 kernel: [    0.032061] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 16:02:24 node-1 kernel: [    0.032062] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 16:02:24 node-1 kernel: [    0.032063] HPET id 0 under DRHD base 0xc7ffc000
Jul 24 16:02:24 node-1 kernel: [    0.032064] Your BIOS is broken and requested that x2apic be disabled.
Jul 24 16:02:24 node-1 kernel: [    0.032064] This will slightly decrease performance.
Jul 24 16:02:24 node-1 kernel: [    0.032064] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 24 16:02:24 node-1 kernel: [    0.032496] Enabled IRQ remapping in xapic mode
Jul 24 16:02:24 node-1 kernel: [    0.032497] x2apic not enabled, IRQ remapping is in xapic mode
Jul 24 16:02:24 node-1 kernel: [    0.032501] Switched APIC routing to physical flat.
Jul 24 16:02:24 node-1 kernel: [    0.033125] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 24 16:02:24 node-1 kernel: [    0.072774] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 24 16:02:24 node-1 kernel: [    0.072779] TSC deadline timer enabled
Jul 24 16:02:24 node-1 kernel: [    0.072787] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 24 16:02:24 node-1 kernel: [    0.072793] ... version:                3
Jul 24 16:02:24 node-1 kernel: [    0.072794] ... bit width:              48
Jul 24 16:02:24 node-1 kernel: [    0.072795] ... generic registers:      4
Jul 24 16:02:24 node-1 kernel: [    0.072796] ... value mask:             0000ffffffffffff
Jul 24 16:02:24 node-1 kernel: [    0.072797] ... max period:             0000ffffffffffff
Jul 24 16:02:24 node-1 kernel: [    0.072798] ... fixed-purpose events:   3
Jul 24 16:02:24 node-1 kernel: [    0.072799] ... event mask:             000000070000000f
Jul 24 16:02:24 node-1 kernel: [    0.074222] x86: Booting SMP configuration:
Jul 24 16:02:24 node-1 kernel: [    0.088326] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 24 16:02:24 node-1 kernel: [    0.074224] .... node  #0, CPUs:        #1  #2  #3
Jul 24 16:02:24 node-1 kernel: [    0.116233] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 24 16:02:24 node-1 kernel: [    0.270368] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 24 16:02:24 node-1 kernel: [    0.325979] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 24 16:02:24 node-1 kernel: [    0.383029] x86: Booted up 2 nodes, 16 CPUs
Jul 24 16:02:24 node-1 kernel: [    0.383032] smpboot: Total of 16 processors activated (111748.30 BogoMIPS)
Jul 24 16:02:24 node-1 kernel: [    0.407521] devtmpfs: initialized
Jul 24 16:02:24 node-1 kernel: [    0.410629] EVM: security.selinux
Jul 24 16:02:24 node-1 kernel: [    0.410631] EVM: security.SMACK64
Jul 24 16:02:24 node-1 kernel: [    0.410632] EVM: security.ima
Jul 24 16:02:24 node-1 kernel: [    0.410633] EVM: security.capability
Jul 24 16:02:24 node-1 kernel: [    0.410684] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.411373] pinctrl core: initialized pinctrl subsystem
Jul 24 16:02:24 node-1 kernel: [    0.411436] regulator-dummy: no parameters
Jul 24 16:02:24 node-1 kernel: [    0.411467] RTC time: 16:01:47, date: 07/24/16
Jul 24 16:02:24 node-1 kernel: [    0.411502] NET: Registered protocol family 16
Jul 24 16:02:24 node-1 kernel: [    0.411587] cpuidle: using governor ladder
Jul 24 16:02:24 node-1 kernel: [    0.411588] cpuidle: using governor menu
Jul 24 16:02:24 node-1 kernel: [    0.411623] ACPI: bus type PCI registered
Jul 24 16:02:24 node-1 kernel: [    0.411625] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 24 16:02:24 node-1 kernel: [    0.411672] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 24 16:02:24 node-1 kernel: [    0.411675] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 24 16:02:24 node-1 kernel: [    0.425408] PCI: Using configuration type 1 for base access
Jul 24 16:02:24 node-1 kernel: [    0.426409] bio: create slab <bio-0> at 0
Jul 24 16:02:24 node-1 kernel: [    0.426694] ACPI: Added _OSI(Module Device)
Jul 24 16:02:24 node-1 kernel: [    0.426696] ACPI: Added _OSI(Processor Device)
Jul 24 16:02:24 node-1 kernel: [    0.426697] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 24 16:02:24 node-1 kernel: [    0.426698] ACPI: Added _OSI(Processor Aggregator Device)
Jul 24 16:02:24 node-1 kernel: [    0.439376] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 24 16:02:24 node-1 kernel: [    0.451052] ACPI: Interpreter enabled
Jul 24 16:02:24 node-1 kernel: [    0.451058] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 24 16:02:24 node-1 kernel: [    0.451062] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 24 16:02:24 node-1 kernel: [    0.451065] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 24 16:02:24 node-1 kernel: [    0.451072] ACPI: (supports S0 S4 S5)
Jul 24 16:02:24 node-1 kernel: [    0.451073] ACPI: Using IOAPIC for interrupt routing
Jul 24 16:02:24 node-1 kernel: [    0.451115] HEST: Table parsing has been initialized.
Jul 24 16:02:24 node-1 kernel: [    0.451118] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 24 16:02:24 node-1 kernel: [    0.451669] ACPI: No dock devices found.
Jul 24 16:02:24 node-1 kernel: [    0.463264] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 24 16:02:24 node-1 kernel: [    0.463269] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 16:02:24 node-1 kernel: [    0.463273] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 16:02:24 node-1 kernel: [    0.463299] PCI host bridge to bus 0000:ff
Jul 24 16:02:24 node-1 kernel: [    0.463301] pci_bus 0000:ff: root bus resource [bus ff]
Jul 24 16:02:24 node-1 kernel: [    0.463309] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463347] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 16:02:24 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 24 16:02:24 node-1 kernel: [    0.463378] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463413] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463442] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.463471] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.463503] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463532] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463560] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463588] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463614] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463640] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463668] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463694] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463721] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463747] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463776] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463804] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463830] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.463858] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463884] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.463910] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463936] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.463966] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.464001] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464031] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464061] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464092] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464123] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464154] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464185] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464215] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464245] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464278] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464310] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464343] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464374] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464403] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464430] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464465] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464498] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464535] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464570] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464604] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464635] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464667] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464697] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464726] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464757] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464789] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464821] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464851] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464880] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464909] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464940] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.464974] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465007] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465065] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 24 16:02:24 node-1 kernel: [    0.465067] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 16:02:24 node-1 kernel: [    0.465070] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 16:02:24 node-1 kernel: [    0.465088] PCI host bridge to bus 0000:7f
Jul 24 16:02:24 node-1 kernel: [    0.465090] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 24 16:02:24 node-1 kernel: [    0.465095] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465123] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.465150] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465179] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465205] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.465231] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.465257] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465283] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465306] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465328] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465351] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465373] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465397] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465421] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465447] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465477] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465499] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465522] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465544] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.465568] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465590] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.465612] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465634] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465660] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 16:02:24 node-1 kernel: [    0.465692] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465718] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465746] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465773] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465798] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465825] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465850] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465877] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465902] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465930] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465957] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.465985] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466013] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466038] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466064] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466092] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466117] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466143] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466171] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466199] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466224] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466249] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466274] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466300] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466327] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466353] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466382] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466407] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466430] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466455] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466481] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466510] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.466536] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.467777] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 24 16:02:24 node-1 kernel: [    0.467781] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 16:02:24 node-1 kernel: [    0.468911] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 16:02:24 node-1 kernel: [    0.469419] PCI host bridge to bus 0000:00
Jul 24 16:02:24 node-1 kernel: [    0.469421] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 24 16:02:24 node-1 kernel: [    0.469423] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 24 16:02:24 node-1 kernel: [    0.469424] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 24 16:02:24 node-1 kernel: [    0.469426] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 24 16:02:24 node-1 kernel: [    0.469427] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 24 16:02:24 node-1 kernel: [    0.469428] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 24 16:02:24 node-1 kernel: [    0.469430] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 24 16:02:24 node-1 kernel: [    0.469436] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 24 16:02:24 node-1 kernel: [    0.469517] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.469548] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.469590] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 24 16:02:24 node-1 kernel: [    0.469608] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.469638] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.469678] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 24 16:02:24 node-1 kernel: [    0.469696] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.469725] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.469768] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 24 16:02:24 node-1 kernel: [    0.469785] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.469855] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.469930] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.470005] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 16:02:24 node-1 kernel: [    0.470010] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 24 16:02:24 node-1 kernel: [    0.470093] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 24 16:02:24 node-1 kernel: [    0.470240] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 24 16:02:24 node-1 kernel: [    0.470258] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 24 16:02:24 node-1 kernel: [    0.470335] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.470388] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 16:02:24 node-1 kernel: [    0.470409] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.470464] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.470508] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 24 16:02:24 node-1 kernel: [    0.470535] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.470591] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.470634] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 24 16:02:24 node-1 kernel: [    0.470659] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 24 16:02:24 node-1 kernel: [    0.470676] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 24 16:02:24 node-1 kernel: [    0.470753] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.470802] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 16:02:24 node-1 kernel: [    0.470827] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 24 16:02:24 node-1 kernel: [    0.471076] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 24 16:02:24 node-1 kernel: [    0.471082] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 24 16:02:24 node-1 kernel: [    0.471088] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.471094] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.471101] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 24 16:02:24 node-1 kernel: [    0.471131] pci 0000:01:00.0: supports D1 D2
Jul 24 16:02:24 node-1 kernel: [    0.477200] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 16:02:24 node-1 kernel: [    0.477203] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 16:02:24 node-1 kernel: [    0.477205] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 16:02:24 node-1 kernel: [    0.477312] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.477346] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 24 16:02:24 node-1 kernel: [    0.485208] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 16:02:24 node-1 kernel: [    0.485226] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.485227] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 16:02:24 node-1 kernel: [    0.485282] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.485350] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.485426] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.485471] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 16:02:24 node-1 kernel: [    0.485475] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.485477] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 16:02:24 node-1 kernel: [    0.485533] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.485656] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.485710] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 16:02:24 node-1 kernel: [    0.485712] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.485714] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.485763] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.485882] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.485922] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.486064] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.486100] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.486220] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.486257] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 24 16:02:24 node-1 kernel: [    0.486377] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 24 16:02:24 node-1 kernel: [    0.486417] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 16:02:24 node-1 kernel: [    0.486420] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.486422] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.486481] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 24 16:02:24 node-1 kernel: [    0.486544] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.486596] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.486638] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 24 16:02:24 node-1 kernel: [    0.486720] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 24 16:02:24 node-1 kernel: [    0.486825] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 16:02:24 node-1 kernel: [    0.486827] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.486829] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.486885] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 24 16:02:24 node-1 kernel: [    0.486938] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.487014] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.487224] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 16:02:24 node-1 kernel: [    0.487227] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 16:02:24 node-1 kernel: [    0.487290] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 24 16:02:24 node-1 kernel: [    0.487344] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.487392] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.487603] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 16:02:24 node-1 kernel: [    0.487607] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 16:02:24 node-1 kernel: [    0.487665] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 24 16:02:24 node-1 kernel: [    0.487725] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.487777] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 24 16:02:24 node-1 kernel: [    0.488030] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 16:02:24 node-1 kernel: [    0.488034] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 16:02:24 node-1 kernel: [    0.488207] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 16:02:24 node-1 kernel: [    0.488245] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 16:02:24 node-1 kernel: [    0.488318] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 24 16:02:24 node-1 kernel: [    0.488337] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 24 16:02:24 node-1 kernel: [    0.488350] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 24 16:02:24 node-1 kernel: [    0.488364] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 24 16:02:24 node-1 kernel: [    0.488413] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 24 16:02:24 node-1 kernel: [    0.493215] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 16:02:24 node-1 kernel: [    0.493224] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 16:02:24 node-1 kernel: [    0.493280] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 24 16:02:24 node-1 kernel: [    0.493768] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 24 16:02:24 node-1 kernel: [    0.493771] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 16:02:24 node-1 kernel: [    0.493895] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 16:02:24 node-1 kernel: [    0.494000] PCI host bridge to bus 0000:80
Jul 24 16:02:24 node-1 kernel: [    0.494002] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 24 16:02:24 node-1 kernel: [    0.494003] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 24 16:02:24 node-1 kernel: [    0.494005] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 24 16:02:24 node-1 kernel: [    0.494013] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.494075] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.494142] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 16:02:24 node-1 kernel: [    0.494202] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 16:02:24 node-1 kernel: [    0.494208] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 24 16:02:24 node-1 kernel: [    0.494280] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 24 16:02:24 node-1 kernel: [    0.494578] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 24 16:02:24 node-1 kernel: [    0.494610] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 24 16:02:24 node-1 kernel: [    0.494639] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 24 16:02:24 node-1 kernel: [    0.494668] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 24 16:02:24 node-1 kernel: [    0.494697] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 16:02:24 node-1 kernel: [    0.494727] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 16:02:24 node-1 kernel: [    0.494756] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 16:02:24 node-1 kernel: [    0.494786] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 16:02:24 node-1 kernel: [    0.494870] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 24 16:02:24 node-1 kernel: [    0.494874] ACPI: \_SB_.UNC1: notify handler is installed
Jul 24 16:02:24 node-1 kernel: [    0.494876] ACPI: \_SB_.UNC0: notify handler is installed
Jul 24 16:02:24 node-1 kernel: [    0.494890] ACPI: \_SB_.PCI0: notify handler is installed
Jul 24 16:02:24 node-1 kernel: [    0.494943] ACPI: \_SB_.PCI1: notify handler is installed
Jul 24 16:02:24 node-1 kernel: [    0.495022] Found 4 acpi root devices
Jul 24 16:02:24 node-1 kernel: [    0.495128] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 24 16:02:24 node-1 kernel: [    0.495130] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 24 16:02:24 node-1 kernel: [    0.495131] vgaarb: loaded
Jul 24 16:02:24 node-1 kernel: [    0.495132] vgaarb: bridge control possible 0000:0c:00.0
Jul 24 16:02:24 node-1 kernel: [    0.495248] SCSI subsystem initialized
Jul 24 16:02:24 node-1 kernel: [    0.495310] libata version 3.00 loaded.
Jul 24 16:02:24 node-1 kernel: [    0.495325] ACPI: bus type USB registered
Jul 24 16:02:24 node-1 kernel: [    0.495335] usbcore: registered new interface driver usbfs
Jul 24 16:02:24 node-1 kernel: [    0.495340] usbcore: registered new interface driver hub
Jul 24 16:02:24 node-1 kernel: [    0.495363] usbcore: registered new device driver usb
Jul 24 16:02:24 node-1 kernel: [    0.495523] PCI: Using ACPI for IRQ routing
Jul 24 16:02:24 node-1 kernel: [    0.499105] PCI: pci_cache_line_size set to 64 bytes
Jul 24 16:02:24 node-1 kernel: [    0.499312] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 24 16:02:24 node-1 kernel: [    0.499313] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 24 16:02:24 node-1 kernel: [    0.499314] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 24 16:02:24 node-1 kernel: [    0.499378] NetLabel: Initializing
Jul 24 16:02:24 node-1 kernel: [    0.499380] NetLabel:  domain hash size = 128
Jul 24 16:02:24 node-1 kernel: [    0.499381] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 24 16:02:24 node-1 kernel: [    0.499390] NetLabel:  unlabeled traffic allowed by default
Jul 24 16:02:24 node-1 kernel: [    0.499444] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 24 16:02:24 node-1 kernel: [    0.499448] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 24 16:02:24 node-1 kernel: [    0.501502] Switched to clocksource hpet
Jul 24 16:02:24 node-1 kernel: [    0.505457] AppArmor: AppArmor Filesystem Enabled
Jul 24 16:02:24 node-1 kernel: [    0.505472] pnp: PnP ACPI init
Jul 24 16:02:24 node-1 kernel: [    0.505478] ACPI: bus type PNP registered
Jul 24 16:02:24 node-1 kernel: [    0.505592] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505600] pnp 00:01: [dma 4]
Jul 24 16:02:24 node-1 kernel: [    0.505612] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505638] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505658] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505676] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505708] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505761] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505763] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 24 16:02:24 node-1 kernel: [    0.505764] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505766] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505767] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505772] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505774] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 24 16:02:24 node-1 kernel: [    0.505776] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505777] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505779] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505780] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505782] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505783] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 24 16:02:24 node-1 kernel: [    0.505786] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505868] pnp 00:07: [dma 0 disabled]
Jul 24 16:02:24 node-1 kernel: [    0.505897] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 16:02:24 node-1 kernel: [    0.505971] pnp 00:08: [dma 0 disabled]
Jul 24 16:02:24 node-1 kernel: [    0.506007] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 16:02:24 node-1 kernel: [    0.506057] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 24 16:02:24 node-1 kernel: [    0.506401] pnp: PnP ACPI: found 10 devices
Jul 24 16:02:24 node-1 kernel: [    0.506403] ACPI: bus type PNP unregistered
Jul 24 16:02:24 node-1 kernel: [    0.512754] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 16:02:24 node-1 kernel: [    0.512756] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 16:02:24 node-1 kernel: [    0.512759] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 16:02:24 node-1 kernel: [    0.512763] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 16:02:24 node-1 kernel: [    0.512765] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.512780] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.512809] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 16:02:24 node-1 kernel: [    0.512824] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 16:02:24 node-1 kernel: [    0.512852] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 16:02:24 node-1 kernel: [    0.512867] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 16:02:24 node-1 kernel: [    0.512896] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 16:02:24 node-1 kernel: [    0.512910] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 16:02:24 node-1 kernel: [    0.512939] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 16:02:24 node-1 kernel: [    0.512941] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.512970] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.512998] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 16:02:24 node-1 kernel: [    0.513000] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513015] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513044] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 16:02:24 node-1 kernel: [    0.513046] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513048] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513053] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 16:02:24 node-1 kernel: [    0.513054] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513057] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513060] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 16:02:24 node-1 kernel: [    0.513065] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 16:02:24 node-1 kernel: [    0.513073] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 16:02:24 node-1 kernel: [    0.513076] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 16:02:24 node-1 kernel: [    0.513083] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 24 16:02:24 node-1 kernel: [    0.513084] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 24 16:02:24 node-1 kernel: [    0.513084] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 24 16:02:24 node-1 kernel: [    0.513085] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 24 16:02:24 node-1 kernel: [    0.513086] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 24 16:02:24 node-1 kernel: [    0.513087] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 24 16:02:24 node-1 kernel: [    0.513088] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 24 16:02:24 node-1 kernel: [    0.513089] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 24 16:02:24 node-1 kernel: [    0.513090] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513091] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513092] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513092] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513093] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513094] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513095] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513096] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513097] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 24 16:02:24 node-1 kernel: [    0.513098] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513099] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 24 16:02:24 node-1 kernel: [    0.513100] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 24 16:02:24 node-1 kernel: [    0.513101] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 24 16:02:24 node-1 kernel: [    0.513102] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 24 16:02:24 node-1 kernel: [    0.513104] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 24 16:02:24 node-1 kernel: [    0.513105] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 24 16:02:24 node-1 kernel: [    0.513140] NET: Registered protocol family 2
Jul 24 16:02:24 node-1 kernel: [    0.513400] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.513738] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.513881] TCP: Hash tables configured (established 262144 bind 65536)
Jul 24 16:02:24 node-1 kernel: [    0.513918] TCP: reno registered
Jul 24 16:02:24 node-1 kernel: [    0.513948] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.514041] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.514187] NET: Registered protocol family 1
Jul 24 16:02:24 node-1 kernel: [    0.549600] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 24 16:02:24 node-1 kernel: [    0.549614] PCI: CLS 64 bytes, default 64
Jul 24 16:02:24 node-1 kernel: [    0.549689] Trying to unpack rootfs image as initramfs...
Jul 24 16:02:24 node-1 kernel: [    0.768685] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 24 16:02:24 node-1 kernel: [    0.768720] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 24 16:02:24 node-1 kernel: [    0.768723] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 24 16:02:24 node-1 kernel: [    0.769141] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769147] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769152] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769158] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769169] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769186] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769202] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769217] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769228] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769238] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769244] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769250] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769259] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769272] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769289] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769302] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 16:02:24 node-1 kernel: [    0.769412] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 24 16:02:24 node-1 kernel: [    0.769418] Scanning for low memory corruption every 60 seconds
Jul 24 16:02:24 node-1 kernel: [    0.769873] Initialise system trusted keyring
Jul 24 16:02:24 node-1 kernel: [    0.769924] audit: initializing netlink socket (disabled)
Jul 24 16:02:24 node-1 kernel: [    0.769940] type=2000 audit(1469376106.724:1): initialized
Jul 24 16:02:24 node-1 kernel: [    0.787882] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 24 16:02:24 node-1 kernel: [    0.789422] zbud: loaded
Jul 24 16:02:24 node-1 kernel: [    0.789543] VFS: Disk quotas dquot_6.5.2
Jul 24 16:02:24 node-1 kernel: [    0.789577] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 24 16:02:24 node-1 kernel: [    0.789958] fuse init (API version 7.22)
Jul 24 16:02:24 node-1 kernel: [    0.790018] msgmni has been set to 32768
Jul 24 16:02:24 node-1 kernel: [    0.790066] Key type big_key registered
Jul 24 16:02:24 node-1 kernel: [    0.790596] Key type asymmetric registered
Jul 24 16:02:24 node-1 kernel: [    0.790598] Asymmetric key parser 'x509' registered
Jul 24 16:02:24 node-1 kernel: [    0.790620] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 24 16:02:24 node-1 kernel: [    0.790691] io scheduler noop registered
Jul 24 16:02:24 node-1 kernel: [    0.790692] io scheduler deadline registered (default)
Jul 24 16:02:24 node-1 kernel: [    0.790711] io scheduler cfq registered
Jul 24 16:02:24 node-1 kernel: [    0.791244] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    0.791444] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    0.791561] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    0.791670] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    0.791784] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    0.791882] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    0.792305] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 24 16:02:24 node-1 kernel: [    0.792331] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 24 16:02:24 node-1 kernel: [    0.792347] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 24 16:02:24 node-1 kernel: [    0.792356] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792358] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792361] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 24 16:02:24 node-1 kernel: [    0.792365] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792367] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792368] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792370] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792372] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792374] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792375] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792376] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792377] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792379] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792380] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792382] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792384] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 24 16:02:24 node-1 kernel: [    0.792389] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792391] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 24 16:02:24 node-1 kernel: [    0.792406] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792409] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 24 16:02:24 node-1 kernel: [    0.792419] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792421] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 24 16:02:24 node-1 kernel: [    0.792424] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 24 16:02:24 node-1 kernel: [    0.792460] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 24 16:02:24 node-1 kernel: [    0.792467] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 24 16:02:24 node-1 kernel: [    0.792479] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 24 16:02:24 node-1 kernel: [    0.792488] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 24 16:02:24 node-1 kernel: [    0.792529] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 24 16:02:24 node-1 kernel: [    0.792531] vesafb: scrolling: redraw
Jul 24 16:02:24 node-1 kernel: [    0.792532] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 24 16:02:24 node-1 kernel: [    0.813114] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 24 16:02:24 node-1 kernel: [    0.821612] Console: switching to colour frame buffer device 80x30
Jul 24 16:02:24 node-1 kernel: [    0.830279] fb0: VESA VGA frame buffer device
Jul 24 16:02:24 node-1 kernel: [    0.830473] intel_idle: MWAIT substates: 0x2120
Jul 24 16:02:24 node-1 kernel: [    0.830474] intel_idle: v0.4 model 0x3F
Jul 24 16:02:24 node-1 kernel: [    0.830475] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 24 16:02:24 node-1 kernel: [    0.830710] ipmi message handler version 39.2
Jul 24 16:02:24 node-1 kernel: [    0.830986] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 24 16:02:24 node-1 kernel: [    0.831421] ACPI: AC Adapter [P111] (on-line)
Jul 24 16:02:24 node-1 kernel: [    0.836747] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 24 16:02:24 node-1 kernel: [    0.847853] ACPI: Power Button [PWRB]
Jul 24 16:02:24 node-1 kernel: [    0.853615] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 24 16:02:24 node-1 kernel: [    0.865264] ACPI: Power Button [PWRF]
Jul 24 16:02:24 node-1 kernel: [    0.891027] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 24 16:02:24 node-1 kernel: [    0.902746] pstore: Registered erst as persistent store backend
Jul 24 16:02:24 node-1 kernel: [    0.908941] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 24 16:02:24 node-1 kernel: [    0.920903] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 24 16:02:24 node-1 kernel: [    0.947654] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 24 16:02:24 node-1 kernel: [    0.980934] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 24 16:02:24 node-1 kernel: [    0.995022] Linux agpgart interface v0.103
Jul 24 16:02:24 node-1 kernel: [    1.002682] brd: module loaded
Jul 24 16:02:24 node-1 kernel: [    1.009795] loop: module loaded
Jul 24 16:02:24 node-1 kernel: [    1.016514] libphy: Fixed MDIO Bus: probed
Jul 24 16:02:24 node-1 kernel: [    1.022980] tun: Universal TUN/TAP device driver, 1.6
Jul 24 16:02:24 node-1 kernel: [    1.029444] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 24 16:02:24 node-1 kernel: [    1.035957] PPP generic driver version 2.4.2
Jul 24 16:02:24 node-1 kernel: [    1.042329] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 24 16:02:24 node-1 kernel: [    1.048764] ehci-pci: EHCI PCI platform driver
Jul 24 16:02:24 node-1 kernel: [    1.055289] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 24 16:02:24 node-1 kernel: [    1.061688] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 24 16:02:24 node-1 kernel: [    1.074204] ehci-pci 0000:00:1a.0: debug port 2
Jul 24 16:02:24 node-1 kernel: [    1.084393] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 24 16:02:24 node-1 kernel: [    1.084412] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 24 16:02:24 node-1 kernel: [    1.100998] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 24 16:02:24 node-1 kernel: [    1.107070] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 16:02:24 node-1 kernel: [    1.113243] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 16:02:24 node-1 kernel: [    1.125227] usb usb1: Product: EHCI Host Controller
Jul 24 16:02:24 node-1 kernel: [    1.131253] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 16:02:24 node-1 kernel: [    1.137297] usb usb1: SerialNumber: 0000:00:1a.0
Jul 24 16:02:24 node-1 kernel: [    1.143250] hub 1-0:1.0: USB hub found
Jul 24 16:02:24 node-1 kernel: [    1.149013] hub 1-0:1.0: 2 ports detected
Jul 24 16:02:24 node-1 kernel: [    1.154813] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 24 16:02:24 node-1 kernel: [    1.160393] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 24 16:02:24 node-1 kernel: [    1.171272] ehci-pci 0000:00:1d.0: debug port 2
Jul 24 16:02:24 node-1 kernel: [    1.180590] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 24 16:02:24 node-1 kernel: [    1.180593] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 24 16:02:24 node-1 kernel: [    1.196916] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 24 16:02:24 node-1 kernel: [    1.202113] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 16:02:24 node-1 kernel: [    1.207410] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 16:02:24 node-1 kernel: [    1.217991] usb usb2: Product: EHCI Host Controller
Jul 24 16:02:24 node-1 kernel: [    1.223453] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 16:02:24 node-1 kernel: [    1.228997] usb usb2: SerialNumber: 0000:00:1d.0
Jul 24 16:02:24 node-1 kernel: [    1.234510] hub 2-0:1.0: USB hub found
Jul 24 16:02:24 node-1 kernel: [    1.239858] hub 2-0:1.0: 2 ports detected
Jul 24 16:02:24 node-1 kernel: [    1.245188] ehci-platform: EHCI generic platform driver
Jul 24 16:02:24 node-1 kernel: [    1.250499] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 24 16:02:24 node-1 kernel: [    1.255880] ohci-pci: OHCI PCI platform driver
Jul 24 16:02:24 node-1 kernel: [    1.261247] ohci-platform: OHCI generic platform driver
Jul 24 16:02:24 node-1 kernel: [    1.266543] uhci_hcd: USB Universal Host Controller Interface driver
Jul 24 16:02:24 node-1 kernel: [    1.271944] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 24 16:02:24 node-1 kernel: [    1.472679] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 24 16:02:24 node-1 kernel: [    1.764445] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 24 16:02:24 node-1 kernel: [    1.780823] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 24 16:02:24 node-1 kernel: [    1.786420] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 16:02:24 node-1 kernel: [    1.792091] hub 1-1:1.0: USB hub found
Jul 24 16:02:24 node-1 kernel: [    1.797684] hub 1-1:1.0: 6 ports detected
Jul 24 16:02:24 node-1 kernel: [    1.916327] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 24 16:02:24 node-1 kernel: [    2.310593] i8042: No controller found
Jul 24 16:02:24 node-1 kernel: [    2.316190] mousedev: PS/2 mouse device common for all mice
Jul 24 16:02:24 node-1 kernel: [    2.321958] rtc_cmos 00:02: RTC can wake from S4
Jul 24 16:02:24 node-1 kernel: [    2.327735] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 24 16:02:24 node-1 kernel: [    2.328670] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 24 16:02:24 node-1 kernel: [    2.328671] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 16:02:24 node-1 kernel: [    2.329314] hub 2-1:1.0: USB hub found
Jul 24 16:02:24 node-1 kernel: [    2.329554] hub 2-1:1.0: 8 ports detected
Jul 24 16:02:24 node-1 kernel: [    2.356135] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 24 16:02:24 node-1 kernel: [    2.367549] device-mapper: uevent: version 1.0.3
Jul 24 16:02:24 node-1 kernel: [    2.373310] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 24 16:02:24 node-1 kernel: [    2.384786] ledtrig-cpu: registered to indicate activity on CPUs
Jul 24 16:02:24 node-1 kernel: [    2.390788] TCP: cubic registered
Jul 24 16:02:24 node-1 kernel: [    2.396694] NET: Registered protocol family 10
Jul 24 16:02:24 node-1 kernel: [    2.402802] NET: Registered protocol family 17
Jul 24 16:02:24 node-1 kernel: [    2.408605] Key type dns_resolver registered
Jul 24 16:02:24 node-1 kernel: [    2.414699] Loading compiled-in X.509 certificates
Jul 24 16:02:24 node-1 kernel: [    2.420947] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 24 16:02:24 node-1 kernel: [    2.432672] registered taskstats version 1
Jul 24 16:02:24 node-1 kernel: [    2.440811] Key type trusted registered
Jul 24 16:02:24 node-1 kernel: [    2.448488] Key type encrypted registered
Jul 24 16:02:24 node-1 kernel: [    2.454017] AppArmor: AppArmor sha1 policy hashing enabled
Jul 24 16:02:24 node-1 kernel: [    2.459562] IMA: No TPM chip found, activating TPM-bypass!
Jul 24 16:02:24 node-1 kernel: [    2.465705] regulator-dummy: disabling
Jul 24 16:02:24 node-1 kernel: [    2.471222]   Magic number: 8:468:35
Jul 24 16:02:24 node-1 kernel: [    2.476739] bdi 7:0: hash matches
Jul 24 16:02:24 node-1 kernel: [    2.482309] memory memory204: hash matches
Jul 24 16:02:24 node-1 kernel: [    2.487619] memory memory71: hash matches
Jul 24 16:02:24 node-1 kernel: [    2.492887] rtc_cmos 00:02: setting system clock to 2016-07-24 16:01:49 UTC (1469376109)
Jul 24 16:02:24 node-1 kernel: [    2.505002] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 24 16:02:24 node-1 kernel: [    2.510452] EDD information not available.
Jul 24 16:02:24 node-1 kernel: [    2.515898] PM: Hibernation image not present or could not be loaded.
Jul 24 16:02:24 node-1 kernel: [    2.516754] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 24 16:02:24 node-1 kernel: [    2.527808] Write protecting the kernel read-only data: 12288k
Jul 24 16:02:24 node-1 kernel: [    2.533972] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 24 16:02:24 node-1 kernel: [    2.546327] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 24 16:02:24 node-1 kernel: [    2.578165] device-mapper: multipath: version 1.6.0 loaded
Jul 24 16:02:24 node-1 kernel: [    2.585875] systemd-udevd[216]: starting version 204
Jul 24 16:02:24 node-1 kernel: [    2.606571] md: linear personality registered for level -1
Jul 24 16:02:24 node-1 kernel: [    2.616075] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 24 16:02:24 node-1 kernel: [    2.627010] md: multipath personality registered for level -4
Jul 24 16:02:24 node-1 kernel: [    2.635029] md: raid0 personality registered for level 0
Jul 24 16:02:24 node-1 kernel: [    2.643128] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 24 16:02:24 node-1 kernel: [    2.649400] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 24 16:02:24 node-1 kernel: [    2.649619] md: raid1 personality registered for level 1
Jul 24 16:02:24 node-1 kernel: [    2.661983] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 24 16:02:24 node-1 kernel: [    2.662440] megasas: FW now in Ready state
Jul 24 16:02:24 node-1 kernel: [    2.662508] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662545] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662583] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662620] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662660] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662697] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662730] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662763] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662801] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662840] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662877] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662910] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662946] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.662982] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.663018] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.663059] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.663230] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 24 16:02:24 node-1 kernel: [    2.695060] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 24 16:02:24 node-1 kernel: [    2.708487] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 16:02:24 node-1 kernel: [    2.722608] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 16:02:24 node-1 kernel: [    2.729766] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.729771] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.729775] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.729781] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.729819] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 16:02:24 node-1 kernel: [    2.750519] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 24 16:02:24 node-1 kernel: [    2.755650] raid6: sse2x1    8332 MB/s
Jul 24 16:02:24 node-1 kernel: [    2.771152] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 16:02:24 node-1 kernel: [    2.785012] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 16:02:24 node-1 kernel: [    2.823550] raid6: sse2x2    9881 MB/s
Jul 24 16:02:24 node-1 kernel: [    2.895492] raid6: sse2x4   10075 MB/s
Jul 24 16:02:24 node-1 kernel: [    2.967425] raid6: avx2x1   14947 MB/s
Jul 24 16:02:24 node-1 kernel: [    3.039368] raid6: avx2x2   18880 MB/s
Jul 24 16:02:24 node-1 kernel: [    3.111306] raid6: avx2x4   21313 MB/s
Jul 24 16:02:24 node-1 kernel: [    3.117435] raid6: using algorithm avx2x4 (21313 MB/s)
Jul 24 16:02:24 node-1 kernel: [    3.123506] raid6: using avx2x2 recovery algorithm
Jul 24 16:02:24 node-1 kernel: [    3.129438] megasas:IOC Init cmd success
Jul 24 16:02:24 node-1 kernel: [    3.129441] Switched to clocksource tsc
Jul 24 16:02:24 node-1 kernel: [    3.141141] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.141147] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.141151] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.141154] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.141210] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.152990] xor: automatically using best checksumming function:
Jul 24 16:02:24 node-1 kernel: [    3.162231] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 24 16:02:24 node-1 kernel: [    3.174167] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 16:02:24 node-1 kernel: [    3.186434] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 16:02:24 node-1 kernel: [    3.192610] megasas: INIT adapter done
Jul 24 16:02:24 node-1 kernel: [    3.195227]    avx       : 36559.000 MB/sec
Jul 24 16:02:24 node-1 kernel: [    3.204443] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.204447] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.204451] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.204455] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.204519] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.216191] async_tx: api initialized (async)
Jul 24 16:02:24 node-1 kernel: [    3.217174] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 24 16:02:24 node-1 kernel: [    3.217177] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 16:02:24 node-1 kernel: [    3.217179] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 24 16:02:24 node-1 kernel: [    3.217181] usb 2-1.4: Manufacturer: Avocent
Jul 24 16:02:24 node-1 kernel: [    3.217182] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 24 16:02:24 node-1 kernel: [    3.225452] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 24 16:02:24 node-1 kernel: [    3.225454] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 16:02:24 node-1 kernel: [    3.225455] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 16:02:24 node-1 kernel: [    3.225515] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.225553] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.225592] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.225630] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.225710] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 16:02:24 node-1 kernel: [    3.279167] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 24 16:02:24 node-1 kernel: [    3.279561] scsi0 : LSI SAS based MegaRAID driver
Jul 24 16:02:24 node-1 kernel: [    3.286881] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 16:02:24 node-1 kernel: [    3.298153] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 16:02:24 node-1 kernel: [    3.302352] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 24 16:02:24 node-1 kernel: [    3.302644] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 24 16:02:24 node-1 kernel: [    3.302674] sd 0:2:0:0: [sda] Write Protect is off
Jul 24 16:02:24 node-1 kernel: [    3.302676] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 24 16:02:24 node-1 kernel: [    3.302751] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 24 16:02:24 node-1 kernel: [    3.331596]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 24 16:02:24 node-1 kernel: [    3.333611] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 24 16:02:24 node-1 kernel: [    3.391503] hidraw: raw HID events driver (C) Jiri Kosina
Jul 24 16:02:24 node-1 kernel: [    3.400517] usbcore: registered new interface driver usbhid
Jul 24 16:02:24 node-1 kernel: [    3.406907] usbhid: USB HID core driver
Jul 24 16:02:24 node-1 kernel: [    3.413246] md: raid6 personality registered for level 6
Jul 24 16:02:24 node-1 kernel: [    3.419547] md: raid5 personality registered for level 5
Jul 24 16:02:24 node-1 kernel: [    3.425620] md: raid4 personality registered for level 4
Jul 24 16:02:24 node-1 kernel: [    3.431683] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 24 16:02:24 node-1 kernel: [    3.444032] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 24 16:02:24 node-1 kernel: [    3.456680] md: raid10 personality registered for level 10
Jul 24 16:02:24 node-1 kernel: [    3.456687] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 24 16:02:24 node-1 kernel: [    3.456737] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 24 16:02:24 node-1 kernel: [    3.456791] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 24 16:02:24 node-1 kernel: [    3.456846] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 24 16:02:24 node-1 kernel: [    3.544371] random: lvm urandom read with 31 bits of entropy available
Jul 24 16:02:24 node-1 kernel: [    3.572965] multipathd (367): /proc/367/oom_adj is deprecated, please use /proc/367/oom_score_adj instead.
Jul 24 16:02:24 node-1 kernel: [    3.728663] bio: create slab <bio-1> at 1
Jul 24 16:02:24 node-1 kernel: [    4.576647] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 16:02:24 node-1 kernel: [    5.266605] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 24 16:02:24 node-1 kernel: [    5.303679] random: nonblocking pool is initialized
Jul 24 16:02:24 node-1 kernel: [    5.328843] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 24 16:02:24 node-1 kernel: [    5.376560] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 24 16:02:24 node-1 kernel: [    5.418439] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 24 16:02:24 node-1 kernel: [    5.464183] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 16:02:24 node-1 kernel: [    5.705335] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 24 16:02:24 node-1 kernel: [    5.746213] XFS (dm-1): Mounting Filesystem
Jul 24 16:02:24 node-1 kernel: [    5.998466] XFS (dm-1): Ending clean mount
Jul 24 16:02:24 node-1 kernel: [    6.051178] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 16:02:24 node-1 kernel: [    6.109626] XFS (dm-2): Mounting Filesystem
Jul 24 16:02:24 node-1 kernel: [    6.263556] XFS (dm-2): Ending clean mount
Jul 24 16:02:24 node-1 kernel: [    6.377415] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 16:02:24 node-1 kernel: [    8.409841] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 16:02:24 node-1 kernel: [    8.424545] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 16:02:24 node-1 kernel: [    8.571682] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 16:02:24 node-1 kernel: [    8.571687] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 24 16:02:24 node-1 kernel: [    8.571691] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 24 16:02:24 node-1 kernel: [    8.571695] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 24 16:02:24 node-1 kernel: [    8.629605] systemd-udevd[801]: starting version 204
Jul 24 16:02:24 node-1 kernel: [    8.923952] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 24 16:02:24 node-1 kernel: [    8.923958] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 16:02:24 node-1 kernel: [    8.923961] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 24 16:02:24 node-1 kernel: [    8.923962] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 16:02:24 node-1 kernel: [    8.924028] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 24 16:02:24 node-1 kernel: [    8.928427] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 24 16:02:24 node-1 kernel: [    8.929509] power_meter ACPI000D:00: Found ACPI power meter.
Jul 24 16:02:24 node-1 kernel: [    8.929517] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 24 16:02:24 node-1 kernel: [    8.936480] wmi: Mapper loaded
Jul 24 16:02:24 node-1 kernel: [    8.951149] IPMI System Interface driver.
Jul 24 16:02:24 node-1 kernel: [    8.951178] ipmi_si: probing via ACPI
Jul 24 16:02:24 node-1 kernel: [    8.951188] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 24 16:02:24 node-1 kernel: [    8.951189] ipmi_si: Adding ACPI-specified kcs state machine
Jul 24 16:02:24 node-1 kernel: [    8.951196] ipmi_si: probing via SMBIOS
Jul 24 16:02:24 node-1 kernel: [    8.951197] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 16:02:24 node-1 kernel: [    8.951197] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 24 16:02:24 node-1 kernel: [    8.951199] ipmi_si: probing via SPMI
Jul 24 16:02:24 node-1 kernel: [    8.951200] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 16:02:24 node-1 kernel: [    8.951200] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 24 16:02:24 node-1 kernel: [    8.951201] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 24 16:02:24 node-1 kernel: [    9.002758] systemd-udevd[840]: renamed network interface eth0 to enp6s0
Jul 24 16:02:24 node-1 kernel: [    9.026649] systemd-udevd[834]: renamed network interface eth1 to enp7s0
Jul 24 16:02:24 node-1 kernel: [    9.050664] systemd-udevd[842]: renamed network interface eth2 to enp8s0
Jul 24 16:02:24 node-1 kernel: [    9.066615] systemd-udevd[839]: renamed network interface eth3 to enp9s0
Jul 24 16:02:24 node-1 kernel: [    9.100047] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 24 16:02:24 node-1 kernel: [    9.100056] ipmi_si 00:09: IPMI kcs interface initialized
Jul 24 16:02:24 node-1 kernel: [    9.362924] type=1400 audit(1469376116.371:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.363078] type=1400 audit(1469376116.371:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.363208] type=1400 audit(1469376116.371:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.368327] type=1400 audit(1469376116.375:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.368464] type=1400 audit(1469376116.375:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1069 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.368580] type=1400 audit(1469376116.375:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1069 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.370358] type=1400 audit(1469376116.379:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1068 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.370498] type=1400 audit(1469376116.379:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1068 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.370620] type=1400 audit(1469376116.379:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1068 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.370851] type=1400 audit(1469376116.379:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Jul 24 16:02:24 node-1 kernel: [    9.950070] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 16:02:24 node-1 kernel: [    9.952968] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 16:02:24 node-1 kernel: [   10.195660] enic 0000:06:00.0 enp6s0: Link UP
Jul 24 16:02:24 node-1 kernel: [   10.196784] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 24 16:02:24 node-1 kernel: [   10.196789] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 24 16:02:24 node-1 kernel: [   20.884140] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 24 16:02:26 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 24 16:02:26 node-1 kernel: [   39.299227] init: failsafe main process (8434) killed by TERM signal
Jul 24 16:02:26 node-1 dbus[8500]: [system] AppArmor D-Bus mediation is enabled
Jul 24 16:02:26 node-1 kernel: [   39.550913] audit_printk_skb: 30 callbacks suppressed
Jul 24 16:02:26 node-1 kernel: [   39.550915] type=1400 audit(1469376146.396:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8561 comm="apparmor_parser"
Jul 24 16:02:26 node-1 kernel: [   39.551007] type=1400 audit(1469376146.396:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8560 comm="apparmor_parser"
Jul 24 16:02:26 node-1 kernel: [   39.551011] type=1400 audit(1469376146.396:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8560 comm="apparmor_parser"
Jul 24 16:02:26 node-1 kernel: [   39.551014] type=1400 audit(1469376146.396:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8560 comm="apparmor_parser"
Jul 24 16:02:26 node-1 kernel: [   39.551236] type=1400 audit(1469376146.396:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8560 comm="apparmor_parser"
Jul 24 16:02:26 node-1 kernel: [   39.551238] type=1400 audit(1469376146.396:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8560 comm="apparmor_parser"
Jul 24 16:02:26 node-1 kernel: [   39.551355] type=1400 audit(1469376146.396:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8560 comm="apparmor_parser"
Jul 24 16:02:26 node-1 kernel: [   39.622043] type=1400 audit(1469376146.468:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8563 comm="apparmor_parser"
Jul 24 16:02:26 node-1 cron[8593]: (CRON) INFO (pidfile fd = 3)
Jul 24 16:02:26 node-1 anacron[8629]: Anacron 2.3 started on 2016-07-24
Jul 24 16:02:26 node-1 cron[8635]: (CRON) STARTUP (fork ok)
Jul 24 16:02:26 node-1 anacron[8629]: Will run job `cron.daily' in 5 min.
Jul 24 16:02:26 node-1 anacron[8629]: Will run job `cron.weekly' in 10 min.
Jul 24 16:02:26 node-1 anacron[8629]: Will run job `cron.monthly' in 15 min.
Jul 24 16:02:26 node-1 anacron[8629]: Jobs will be executed sequentially
Jul 24 16:02:26 node-1 multipathd: path checkers start up
Jul 24 16:02:26 node-1 cron[8635]: (CRON) INFO (Running @reboot jobs)
Jul 24 16:02:27 node-1 postfix/master[8772]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 24 16:02:30 node-1 puppet-agent[8956]: Reopening log files
Jul 24 16:02:31 node-1 puppet-agent[8956]: Could not request certificate: Connection refused - connect(2)
Jul 24 16:02:43 node-1 puppet-user[9035]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 24 16:02:43 node-1 puppet-user[9035]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 24 16:02:45 node-1 puppet-user[9035]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 24 16:02:45 node-1 puppet-user[9035]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 24 16:02:45 node-1 puppet-user[9035]: Finished catalog run in 0.94 seconds
Jul 24 16:02:46 node-1 multipathd: uevent trigger error
Jul 24 16:02:46 node-1 puppet-user[9460]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 16:02:46 node-1 puppet-user[9460]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 24 16:02:46 node-1 puppet-user[9460]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 24 16:02:46 node-1 puppet-user[9460]: Finished catalog run in 0.05 seconds
Jul 24 16:02:47 node-1 puppet-user[10052]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 24 16:02:48 node-1 puppet-user[10052]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 24 16:02:48 node-1 puppet-user[10052]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 24 16:02:48 node-1 puppet-user[10052]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 24 16:02:48 node-1 puppet-user[10052]: Finished catalog run in 0.04 seconds
Jul 24 16:02:49 node-1 puppet-user[10526]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 24 16:02:49 node-1 puppet-user[10526]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 24 16:02:49 node-1 puppet-user[10526]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 24 16:02:49 node-1 puppet-user[10526]: Finished catalog run in 0.05 seconds
Jul 24 16:02:51 node-1 puppet-user[10980]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 24 16:02:51 node-1 puppet-user[10980]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Jul 24 16:02:51 node-1 puppet-user[10980]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 24 16:02:51 node-1 puppet-user[10980]: (/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 24 16:02:52 node-1 puppet-user[10980]: (/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 24 16:02:52 node-1 puppet-user[10980]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Jul 24 16:02:52 node-1 puppet-user[10980]: Finished catalog run in 1.22 seconds
Jul 24 16:02:53 node-1 puppet-user[11502]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 24 16:02:53 node-1 puppet-user[11502]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Jul 24 16:02:54 node-1 puppet-user[11502]: (/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 24 16:02:54 node-1 puppet-user[11502]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Jul 24 16:02:54 node-1 puppet-user[11502]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 24 16:02:54 node-1 puppet-user[11502]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 24 16:02:54 node-1 puppet-user[11502]: (/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 24 16:02:54 node-1 puppet-user[11502]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 24 16:02:54 node-1 puppet-user[11502]: Finished catalog run in 0.38 seconds
Jul 24 16:02:55 node-1 puppet-user[11977]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 24 16:02:55 node-1 puppet-user[11977]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Jul 24 16:02:56 node-1 puppet-user[11977]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 24 16:02:56 node-1 kernel: [   69.157826] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 24 16:02:56 node-1 kernel: [   69.157875] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 24 16:02:56 node-1 puppet-user[11977]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 24 16:02:56 node-1 puppet-user[11977]: Finished catalog run in 0.05 seconds
Jul 24 16:02:57 node-1 puppet-user[12453]: (Scope(Class[main])) MODULAR: sync_time
Jul 24 16:02:57 node-1 puppet-user[12453]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 24 16:02:58 node-1 ntpdate[12866]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 24 16:03:01 node-1 CRON[13135]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 24 16:03:04 node-1 ntpdate[12866]: adjust time server 10.20.0.2 offset 0.001275 sec
Jul 24 16:03:04 node-1 puppet-user[12453]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 24 16:03:04 node-1 puppet-user[12453]: Finished catalog run in 6.17 seconds
Jul 24 16:03:11 node-1 kernel: [   84.866068] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 16:03:11 node-1 puppet-agent[8956]: Could not run: SIGTERM
Jul 24 16:03:12 node-1 kernel: [   85.142982] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 24 16:03:12 node-1 ec2: 
Jul 24 16:03:12 node-1 ec2: #############################################################
Jul 24 16:03:12 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 24 16:03:12 node-1 ec2: 1024 07:bd:46:6d:02:12:ac:d4:f7:19:7b:08:ec:b7:16:c0  root@node-1.domain.tld (DSA)
Jul 24 16:03:12 node-1 ec2: 256 29:70:dc:a7:a7:0e:1a:e8:0d:b9:f7:6a:b3:a5:81:9f  root@node-1.domain.tld (ECDSA)
Jul 24 16:03:12 node-1 ec2: 256 ba:ec:60:fc:71:43:b8:6f:e7:47:7b:0b:ac:d4:10:cc  root@node-1.domain.tld (ED25519)
Jul 24 16:03:12 node-1 ec2: 2048 c8:b6:d0:4b:ac:11:f9:da:0c:5e:53:00:88:c4:ec:0e  root@node-1.domain.tld (RSA)
Jul 24 16:03:12 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 24 16:03:12 node-1 ec2: #############################################################
Jul 24 16:03:20 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 16:03:20 node-1 nailgun-agent: D, [2016-07-24T16:03:01.881276 #13138] DEBUG -- : Sleep for 19 seconds before sending request
Jul 24 16:03:20 node-1 nailgun-agent: I, [2016-07-24T16:03:20.895923 #13138]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 16:03:21 node-1 nailgun-agent: D, [2016-07-24T16:03:21.296122 #13138] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.447972 #13138] DEBUG -- : Trying to find block devices
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.448130 #13138] DEBUG -- : Found block device: sda
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.448223 #13138] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.448254 #13138] DEBUG -- : Trying to get list of physical devices
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.448433 #13138] DEBUG -- : Getting udev properties for device: sda
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.452099 #13138] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Jul 24 16:03:33 node-1 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90422", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.452135 #13138] DEBUG -- : Trying to find out if device sda is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.452197 #13138] DEBUG -- : Device sda removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.452218 #13138] DEBUG -- : Device sda seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.452770 #13138] DEBUG -- : Getting udev properties for device: dm-0
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.456060 #13138] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-NOE6nXdFDvYbb6NgJZ0cLbRUa85upmv9aghPImG01hfEMXx3x6BJGhz7LMr1G53m /dev/disk/by-uuid/05ac43d5-19c5-405d-a610-426a27c456b6 /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-NOE6nXdFDvYbb6NgJZ0cLbRUa85upmv9aghPImG01hfEMXx3x6BJGhz7LMr1G53m", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"05ac43d5-19c5-405d-a610-426a27c456b6", "ID_FS_UUID_ENC"=>"05ac43d5-19c5-405d-a610-426a27c456b6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8
Jul 24 16:03:33 node-1 nailgun-agent: 5857", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.456110 #13138] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.456156 #13138] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.456176 #13138] DEBUG -- : Device dm-0 seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.456195 #13138] DEBUG -- : Getting udev properties for device: dm-1
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.459796 #13138] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-GWJkuj2tksIJauhBZlmLpFrOkw69Tydj7xmHR1ktLIKpuSHBdctlTlJMdapfhVwF /dev/disk/by-uuid/a02c2b0e-a283-4647-9df6-844c9b0f378e /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-GWJkuj2tksIJauhBZlmLpFrOkw69Tydj7xmHR1ktLIKpuSHBdctlTlJMdapfhVwF", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a02c2b0e-a283-4647-9df6-844c9b0f378e", "ID_FS_UUID_ENC"=>"a02c2b0e-a283-4647-9df6-844c9b0f378e", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12115", "nomdmonddf"=>"1", "nom
Jul 24 16:03:33 node-1 nailgun-agent: dmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.459853 #13138] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.459918 #13138] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.459961 #13138] DEBUG -- : Device dm-1 seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.459979 #13138] DEBUG -- : Getting udev properties for device: dm-2
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.463812 #13138] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-WoIsbkHL5Xe8dI8YXVOqMtl2dlx4GXQgEVlY93PUGG3yLgWmX3KxkbcbcOXZfHyA /dev/disk/by-uuid/cc14dc9b-1888-4eb4-a197-aee10303752e /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-WoIsbkHL5Xe8dI8YXVOqMtl2dlx4GXQgEVlY93PUGG3yLgWmX3KxkbcbcOXZfHyA", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cc14dc9b-1888-4eb4-a197-aee10303752e", "ID_FS_UUID_ENC"=>"cc14dc9b-1888-4eb4-a197-aee10303752e", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1
Jul 24 16:03:33 node-1 nailgun-agent: 5340", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.463847 #13138] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.463916 #13138] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.463937 #13138] DEBUG -- : Device dm-2 seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.463955 #13138] DEBUG -- : Getting udev properties for device: dm-3
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.467888 #13138] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-D8Quib6ppFdtohghsqJfxrBuGkIyl6fV9pNPUyBbe6c8EUJBFaDkUj70W39GSu0v /dev/disk/by-uuid/83ee4d09-75b4-44be-bea4-c37d6fbc73df /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-D8Quib6ppFdtohghsqJfxrBuGkIyl6fV9pNPUyBbe6c8EUJBFaDkUj70W39GSu0v", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"83ee4d09-75b4-44be-bea4-c37d6fbc73df", "ID_FS_UUID_ENC"=>"83ee4d09-75b4-44be-bea4-c37d6fbc73df", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24104", "nomdmon
Jul 24 16:03:33 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.467925 #13138] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.467965 #13138] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.467984 #13138] DEBUG -- : Device dm-3 seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.468003 #13138] DEBUG -- : Getting udev properties for device: dm-4
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.472181 #13138] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Ho8okTXroCfN2hE4dMkUYD4UKnCban7r4oXgt5KZPKd6Sm7EKdTPcDa4Y6WxcLk9 /dev/disk/by-uuid/61274b28-e03c-4fee-9dcd-cfba022cfe25 /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-Ho8okTXroCfN2hE4dMkUYD4UKnCban7r4oXgt5KZPKd6Sm7EKdTPcDa4Y6WxcLk9", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"61274b28-e03c-4fee-9dcd-cfba022cfe25", "ID_FS_UUID_ENC"=>"61274b28-e03c-4fee-9dcd-cfba022cfe25", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35041", "nomdmonddf"=>"1",
Jul 24 16:03:33 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.472215 #13138] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.472259 #13138] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.472299 #13138] DEBUG -- : Device dm-4 seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.472318 #13138] DEBUG -- : Getting udev properties for device: dm-5
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.476278 #13138] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-ER6rz812dRZo3Rc73j8UiI1XLdFiZ4ZBUf2JIYhEtOoLyPkRRzQUy5tE4iYLf63x /dev/disk/by-uuid/b79bf4c1-c9fa-487c-beda-39352777658b /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-ER6rz812dRZo3Rc73j8UiI1XLdFiZ4ZBUf2JIYhEtOoLyPkRRzQUy5tE4iYLf63x", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b79bf4c1-c9fa-487c-beda-39352777658b", "ID_FS_UUID_ENC"=>"b79bf4c1-c9fa-487c-beda-39352777658b", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"41955", "nomdmonddf"=>"1", "nom
Jul 24 16:03:33 node-1 nailgun-agent: dmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.476314 #13138] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.476357 #13138] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.476399 #13138] DEBUG -- : Device dm-5 seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.476417 #13138] DEBUG -- : Getting udev properties for device: dm-6
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.480369 #13138] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-ER6rz812dRZo3Rc73j8UiI1XLdFiZ4ZBLNE3Vvr2kY4c6QUiPrWUkYuh1YuvhJIG /dev/disk/by-uuid/cd18ff04-41b5-484c-ae5d-a530a971e9ee /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-ER6rz812dRZo3Rc73j8UiI1XLdFiZ4ZBLNE3Vvr2kY4c6QUiPrWUkYuh1YuvhJIG", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"cd18ff04-41b5-484c-ae5d-a530a971e9ee", "ID_FS_UUID_ENC"=>"cd18ff04-41b5-484c-ae5d-a530a971e9ee", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"42288", "nomdmonddf"=>"1", "nomdmonisw
Jul 24 16:03:33 node-1 nailgun-agent: "=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.480410 #13138] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.480453 #13138] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.480473 #13138] DEBUG -- : Device dm-6 seems to be appropriate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.480513 #13138] DEBUG -- : Getting udev properties for device: ram0
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.484247 #13138] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53661", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.484282 #13138] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.484354 #13138] DEBUG -- : Device ram0 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.484399 #13138] DEBUG -- : Getting udev properties for device: ram1
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.488342 #13138] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53785", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.488404 #13138] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.488470 #13138] DEBUG -- : Device ram1 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.488498 #13138] DEBUG -- : Getting udev properties for device: ram2
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.492381 #13138] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54591", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.492414 #13138] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.492461 #13138] DEBUG -- : Device ram2 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.492489 #13138] DEBUG -- : Getting udev properties for device: ram3
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.496699 #13138] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54683", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.496733 #13138] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.496812 #13138] DEBUG -- : Device ram3 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.496840 #13138] DEBUG -- : Getting udev properties for device: ram4
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.500721 #13138] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54818", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.500754 #13138] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.500798 #13138] DEBUG -- : Device ram4 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.500824 #13138] DEBUG -- : Getting udev properties for device: ram5
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.505144 #13138] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54884", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.505196 #13138] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.505242 #13138] DEBUG -- : Device ram5 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.505270 #13138] DEBUG -- : Getting udev properties for device: ram6
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.509192 #13138] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55052", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.509305 #13138] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.509414 #13138] DEBUG -- : Device ram6 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.509475 #13138] DEBUG -- : Getting udev properties for device: ram7
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.513625 #13138] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55125", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.513700 #13138] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.513821 #13138] DEBUG -- : Device ram7 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.513876 #13138] DEBUG -- : Getting udev properties for device: ram8
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.517964 #13138] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55211", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.518011 #13138] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.518108 #13138] DEBUG -- : Device ram8 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.518146 #13138] DEBUG -- : Getting udev properties for device: ram9
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.521224 #13138] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55322", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.521286 #13138] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.521379 #13138] DEBUG -- : Device ram9 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.521449 #13138] DEBUG -- : Getting udev properties for device: loop0
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.524567 #13138] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53034", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.524614 #13138] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.524679 #13138] DEBUG -- : Device loop0 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.524741 #13138] DEBUG -- : Getting udev properties for device: loop1
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.527987 #13138] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53115", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.528033 #13138] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.528094 #13138] DEBUG -- : Device loop1 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.528131 #13138] DEBUG -- : Getting udev properties for device: loop2
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.531516 #13138] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53200", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.531566 #13138] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.531653 #13138] DEBUG -- : Device loop2 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.531709 #13138] DEBUG -- : Getting udev properties for device: loop3
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.534982 #13138] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53284", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.535025 #13138] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.535123 #13138] DEBUG -- : Device loop3 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.535173 #13138] DEBUG -- : Getting udev properties for device: loop4
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.538155 #13138] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53370", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.538217 #13138] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.538271 #13138] DEBUG -- : Device loop4 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.538306 #13138] DEBUG -- : Getting udev properties for device: loop5
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.541311 #13138] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53452", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.541378 #13138] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.541465 #13138] DEBUG -- : Device loop5 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.541503 #13138] DEBUG -- : Getting udev properties for device: loop6
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.544363 #13138] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53519", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.544425 #13138] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.544487 #13138] DEBUG -- : Device loop6 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.544523 #13138] DEBUG -- : Getting udev properties for device: loop7
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.547487 #13138] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53558", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.547537 #13138] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.547618 #13138] DEBUG -- : Device loop7 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.547664 #13138] DEBUG -- : Getting udev properties for device: ram10
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.557594 #13138] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53881", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.557638 #13138] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.557694 #13138] DEBUG -- : Device ram10 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.557730 #13138] DEBUG -- : Getting udev properties for device: ram11
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.560783 #13138] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53970", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.560823 #13138] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.560880 #13138] DEBUG -- : Device ram11 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.560913 #13138] DEBUG -- : Getting udev properties for device: ram12
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.563800 #13138] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54036", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.563842 #13138] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.563905 #13138] DEBUG -- : Device ram12 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.563938 #13138] DEBUG -- : Getting udev properties for device: ram13
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.566916 #13138] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54170", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.566958 #13138] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.567034 #13138] DEBUG -- : Device ram13 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.567066 #13138] DEBUG -- : Getting udev properties for device: ram14
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.570281 #13138] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54277", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.570328 #13138] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.570410 #13138] DEBUG -- : Device ram14 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.570448 #13138] DEBUG -- : Getting udev properties for device: ram15
Jul 24 16:03:33 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.573600 #13138] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54399", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.573648 #13138] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.573729 #13138] DEBUG -- : Device ram15 removable parameter: "0"
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.573794 #13138] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.573821 #13138] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.573886 #13138] DEBUG -- : Found block device: dm-0
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.573991 #13138] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574016 #13138] DEBUG -- : Found block device: dm-1
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574036 #13138] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574053 #13138] DEBUG -- : Found block device: dm-2
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574071 #13138] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574087 #13138] DEBUG -- : Found block device: dm-3
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574104 #13138] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574122 #13138] DEBUG -- : Found block device: dm-4
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574212 #13138] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574231 #13138] DEBUG -- : Found block device: dm-5
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574250 #13138] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574267 #13138] DEBUG -- : Found block device: dm-6
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574286 #13138] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574303 #13138] DEBUG -- : Found block device: ram0
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574322 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574339 #13138] DEBUG -- : Found block device: ram1
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574426 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574445 #13138] DEBUG -- : Found block device: ram2
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574463 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574481 #13138] DEBUG -- : Found block device: ram3
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574500 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574516 #13138] DEBUG -- : Found block device: ram4
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574534 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574550 #13138] DEBUG -- : Found block device: ram5
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574568 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574634 #13138] DEBUG -- : Found block device: ram6
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574655 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574672 #13138] DEBUG -- : Found block device: ram7
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574694 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574710 #13138] DEBUG -- : Found block device: ram8
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574728 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574743 #13138] DEBUG -- : Found block device: ram9
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574761 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574775 #13138] DEBUG -- : Found block device: loop0
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574793 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574854 #13138] DEBUG -- : Found block device: loop1
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574873 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574889 #13138] DEBUG -- : Found block device: loop2
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574906 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574922 #13138] DEBUG -- : Found block device: loop3
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574940 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574955 #13138] DEBUG -- : Found block device: loop4
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574973 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.574990 #13138] DEBUG -- : Found block device: loop5
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575056 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575072 #13138] DEBUG -- : Found block device: loop6
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575089 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575105 #13138] DEBUG -- : Found block device: loop7
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575122 #13138] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575138 #13138] DEBUG -- : Found block device: ram10
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575154 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575171 #13138] DEBUG -- : Found block device: ram11
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575189 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575204 #13138] DEBUG -- : Found block device: ram12
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575256 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575273 #13138] DEBUG -- : Found block device: ram13
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575291 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575310 #13138] DEBUG -- : Found block device: ram14
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575327 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575343 #13138] DEBUG -- : Found block device: ram15
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575364 #13138] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.575414 #13138] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 24 16:03:33 node-1 nailgun-agent: D, [2016-07-24T16:03:33.788451 #13138] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 24 16:03:33 node-1 nailgun-agent: I, [2016-07-24T16:03:33.788838 #13138]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 24 16:03:51 node-1 puppet-user[13742]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 16:03:51 node-1 puppet-user[13742]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 24 16:03:51 node-1 puppet-user[13742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 24 16:03:51 node-1 puppet-user[13742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 24 16:03:51 node-1 puppet-user[13742]: Finished catalog run in 0.08 seconds
Jul 24 16:03:53 node-1 puppet-user[14196]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 24 16:03:54 node-1 puppet-user[14196]: Compiled catalog for node-1.domain.tld in environment production in 1.19 seconds
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 24 16:03:54 node-1 puppet-user[14196]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 24 16:04:01 node-1 CRON[14837]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 24 16:04:04 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 16:04:04 node-1 nailgun-agent: I, [2016-07-24T16:04:04.968700 #14840]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 16:04:10 node-1 puppet-user[14196]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 24 16:04:10 node-1 puppet-user[14196]: Finished catalog run in 15.79 seconds
Jul 24 16:04:12 node-1 puppet-user[15204]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 24 16:04:12 node-1 puppet-user[15204]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Jul 24 16:04:17 node-1 puppet-user[15204]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 24 16:04:17 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 16:04:18 node-1 nailgun-agent: I, [2016-07-24T16:04:18.103512 #14840]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 24 16:04:51 node-1 puppet-user[15204]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 24 16:04:51 node-1 puppet-user[15204]: Finished catalog run in 38.95 seconds
Jul 24 16:04:53 node-1 puppet-user[17906]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 24 16:04:54 node-1 puppet-user[17906]: Compiled catalog for node-1.domain.tld in environment production in 0.64 seconds
Jul 24 16:04:54 node-1 puppet-user[17906]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 24 16:04:54 node-1 puppet-user[17906]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 24 16:04:54 node-1 puppet-user[17906]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 24 16:04:54 node-1 puppet-user[17906]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 24 16:04:54 node-1 puppet-user[17906]: Finished catalog run in 0.11 seconds
Jul 24 16:04:56 node-1 puppet-user[18371]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 24 16:04:57 node-1 puppet-user[18371]: Compiled catalog for node-1.domain.tld in environment production in 0.84 seconds
Jul 24 16:04:57 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 24 16:04:57 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 24 16:04:57 node-1 crontab[18814]: (root) LIST (root)
Jul 24 16:04:57 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 24 16:04:57 node-1 crontab[18815]: (root) REPLACE (root)
Jul 24 16:05:00 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 24 16:05:01 node-1 CRON[18955]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 24 16:05:01 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 24 16:05:02 node-1 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 24 16:05:03 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8407" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 16:05:03 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 24 16:05:04 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:04 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:04 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:04 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:04 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:25 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:25 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:25 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:25 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:25 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:05:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:06:27 node-1 ntpdate[29036]: no servers can be used, exiting
<27>Jul 24 16:06:59 node-1 multipathd: uevent trigger error
<27>Jul 24 16:06:59 node-1 multipathd: uevent trigger error
<27>Jul 24 16:06:59 node-1 multipathd: uevent trigger error
<27>Jul 24 16:06:59 node-1 multipathd: uevent trigger error
<27>Jul 24 16:06:59 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:03 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:03 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:03 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:03 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:03 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:07:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:32 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 16:08:32 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 16:08:38 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 16:08:38 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 16:08:43 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 16:08:49 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 16:08:49 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 16:08:56 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:56 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:56 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:56 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:56 node-1 multipathd: uevent trigger error
<27>Jul 24 16:08:56 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:15 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:15 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:17 node-1 haproxy[16832]: 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 24 16:09:17 node-1 haproxy[16832]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:18 node-1 haproxy[16836]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:18 node-1 haproxy[16836]: proxy mysqld has no server available!
<27>Jul 24 16:09:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:23 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:26 node-1 haproxy[19377]: 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 24 16:09:26 node-1 haproxy[19377]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:26 node-1 haproxy[19377]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:26 node-1 haproxy[19377]: proxy mysqld has no server available!
<129>Jul 24 16:09:26 node-1 haproxy[19377]: 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 24 16:09:27 node-1 haproxy[19385]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:27 node-1 haproxy[19385]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:27 node-1 haproxy[19385]: proxy object-storage has no server available!
<27>Jul 24 16:09:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:29 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:31 node-1 haproxy[20672]: 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 24 16:09:31 node-1 haproxy[20672]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:31 node-1 haproxy[20672]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:31 node-1 haproxy[20672]: proxy neutron has no server available!
<129>Jul 24 16:09:31 node-1 haproxy[20672]: 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 24 16:09:32 node-1 haproxy[20676]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:32 node-1 haproxy[20676]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:32 node-1 haproxy[20676]: proxy mysqld has no server available!
<129>Jul 24 16:09:32 node-1 haproxy[20676]: 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 24 16:09:32 node-1 haproxy[20676]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:32 node-1 haproxy[20676]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:32 node-1 haproxy[20676]: proxy object-storage has no server available!
<27>Jul 24 16:09:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:34 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:36 node-1 haproxy[22144]: 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 24 16:09:36 node-1 haproxy[22144]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:36 node-1 haproxy[22144]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:36 node-1 haproxy[22144]: proxy keystone-1 has no server available!
<129>Jul 24 16:09:36 node-1 haproxy[22144]: 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 24 16:09:36 node-1 haproxy[22144]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:37 node-1 haproxy[22148]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:37 node-1 haproxy[22148]: proxy keystone-2 has no server available!
<129>Jul 24 16:09:37 node-1 haproxy[22148]: 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 24 16:09:37 node-1 haproxy[22148]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:37 node-1 haproxy[22148]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:37 node-1 haproxy[22148]: proxy neutron has no server available!
<129>Jul 24 16:09:37 node-1 haproxy[22148]: 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 24 16:09:37 node-1 haproxy[22148]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:37 node-1 haproxy[22148]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:37 node-1 haproxy[22148]: proxy mysqld has no server available!
<129>Jul 24 16:09:37 node-1 haproxy[22148]: 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 24 16:09:37 node-1 haproxy[22148]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:38 node-1 haproxy[22148]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:38 node-1 haproxy[22148]: proxy object-storage has no server available!
<27>Jul 24 16:09:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:39 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:41 node-1 haproxy[23408]: 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 24 16:09:41 node-1 haproxy[23408]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:41 node-1 haproxy[23408]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:41 node-1 haproxy[23408]: proxy keystone-1 has no server available!
<129>Jul 24 16:09:41 node-1 haproxy[23408]: 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 24 16:09:41 node-1 haproxy[23408]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:42 node-1 haproxy[23412]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:42 node-1 haproxy[23412]: proxy keystone-2 has no server available!
<129>Jul 24 16:09:42 node-1 haproxy[23412]: 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 24 16:09:42 node-1 haproxy[23412]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:42 node-1 haproxy[23412]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:42 node-1 haproxy[23412]: proxy neutron has no server available!
<129>Jul 24 16:09:42 node-1 haproxy[23412]: 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 24 16:09:42 node-1 haproxy[23412]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:42 node-1 haproxy[23412]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:42 node-1 haproxy[23412]: proxy mysqld has no server available!
<129>Jul 24 16:09:42 node-1 haproxy[23412]: 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 24 16:09:42 node-1 haproxy[23412]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:42 node-1 haproxy[23412]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:42 node-1 haproxy[23412]: proxy object-storage has no server available!
<129>Jul 24 16:09:43 node-1 haproxy[23412]: 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 24 16:09:43 node-1 haproxy[23412]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:43 node-1 haproxy[23412]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:43 node-1 haproxy[23412]: proxy aodh has no server available!
<27>Jul 24 16:09:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:44 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:47 node-1 haproxy[24695]: 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 24 16:09:47 node-1 haproxy[24695]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:47 node-1 haproxy[24695]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:47 node-1 haproxy[24695]: proxy keystone-1 has no server available!
<129>Jul 24 16:09:47 node-1 haproxy[24695]: 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 24 16:09:47 node-1 haproxy[24695]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:47 node-1 haproxy[24695]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:47 node-1 haproxy[24695]: proxy keystone-2 has no server available!
<129>Jul 24 16:09:47 node-1 haproxy[24695]: 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 24 16:09:47 node-1 haproxy[24695]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:47 node-1 haproxy[24695]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:47 node-1 haproxy[24695]: proxy neutron has no server available!
<129>Jul 24 16:09:47 node-1 haproxy[24695]: 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 24 16:09:47 node-1 haproxy[24695]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:48 node-1 haproxy[24699]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:48 node-1 haproxy[24699]: proxy mysqld has no server available!
<129>Jul 24 16:09:48 node-1 haproxy[24699]: 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 24 16:09:48 node-1 haproxy[24699]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:48 node-1 haproxy[24699]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:48 node-1 haproxy[24699]: proxy object-storage has no server available!
<129>Jul 24 16:09:48 node-1 haproxy[24699]: 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 24 16:09:48 node-1 haproxy[24699]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:48 node-1 haproxy[24699]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:48 node-1 haproxy[24699]: proxy aodh has no server available!
<129>Jul 24 16:09:48 node-1 haproxy[24699]: 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 24 16:09:48 node-1 haproxy[24699]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:48 node-1 haproxy[24699]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:48 node-1 haproxy[24699]: proxy ceilometer has no server available!
<27>Jul 24 16:09:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:50 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:52 node-1 haproxy[25960]: 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 24 16:09:52 node-1 haproxy[25960]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:52 node-1 haproxy[25960]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:52 node-1 haproxy[25960]: proxy keystone-1 has no server available!
<129>Jul 24 16:09:52 node-1 haproxy[25960]: 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 24 16:09:52 node-1 haproxy[25960]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:52 node-1 haproxy[25960]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:52 node-1 haproxy[25960]: proxy keystone-2 has no server available!
<129>Jul 24 16:09:52 node-1 haproxy[25960]: 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 24 16:09:52 node-1 haproxy[25960]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:52 node-1 haproxy[25960]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:52 node-1 haproxy[25960]: proxy neutron has no server available!
<129>Jul 24 16:09:53 node-1 haproxy[25964]: 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 24 16:09:53 node-1 haproxy[25964]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:53 node-1 haproxy[25964]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:53 node-1 haproxy[25964]: proxy mysqld has no server available!
<129>Jul 24 16:09:53 node-1 haproxy[25964]: 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 24 16:09:53 node-1 haproxy[25964]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:53 node-1 haproxy[25964]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:53 node-1 haproxy[25964]: proxy object-storage has no server available!
<129>Jul 24 16:09:53 node-1 haproxy[25964]: 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 24 16:09:53 node-1 haproxy[25964]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:53 node-1 haproxy[25964]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:53 node-1 haproxy[25964]: proxy aodh has no server available!
<129>Jul 24 16:09:53 node-1 haproxy[25964]: 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 24 16:09:53 node-1 haproxy[25964]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:54 node-1 haproxy[25964]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:54 node-1 haproxy[25964]: proxy ceilometer has no server available!
<27>Jul 24 16:09:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:09:55 node-1 multipathd: uevent trigger error
<129>Jul 24 16:09:57 node-1 haproxy[27269]: 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 24 16:09:57 node-1 haproxy[27269]: 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 24 16:09:57 node-1 haproxy[27269]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:57 node-1 haproxy[27269]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:57 node-1 haproxy[27269]: proxy keystone-1 has no server available!
<129>Jul 24 16:09:57 node-1 haproxy[27269]: 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 24 16:09:58 node-1 haproxy[27273]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:58 node-1 haproxy[27273]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:58 node-1 haproxy[27273]: proxy keystone-2 has no server available!
<129>Jul 24 16:09:58 node-1 haproxy[27273]: 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 24 16:09:58 node-1 haproxy[27273]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:58 node-1 haproxy[27273]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:58 node-1 haproxy[27273]: proxy neutron has no server available!
<129>Jul 24 16:09:58 node-1 haproxy[27273]: 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 24 16:09:58 node-1 haproxy[27273]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:58 node-1 haproxy[27273]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:58 node-1 haproxy[27273]: proxy mysqld has no server available!
<129>Jul 24 16:09:58 node-1 haproxy[27273]: 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 24 16:09:58 node-1 haproxy[27273]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:58 node-1 haproxy[27273]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:58 node-1 haproxy[27273]: proxy object-storage has no server available!
<129>Jul 24 16:09:58 node-1 haproxy[27273]: 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 24 16:09:58 node-1 haproxy[27273]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:59 node-1 haproxy[27273]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:59 node-1 haproxy[27273]: proxy aodh has no server available!
<129>Jul 24 16:09:59 node-1 haproxy[27273]: 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 24 16:09:59 node-1 haproxy[27273]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:09:59 node-1 haproxy[27273]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:09:59 node-1 haproxy[27273]: proxy ceilometer has no server available!
<27>Jul 24 16:10:00 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:00 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:00 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:00 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:00 node-1 multipathd: uevent trigger error
<129>Jul 24 16:10:03 node-1 haproxy[28617]: 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 24 16:10:03 node-1 haproxy[28617]: 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 24 16:10:03 node-1 haproxy[28617]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:03 node-1 haproxy[28617]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:03 node-1 haproxy[28617]: proxy keystone-1 has no server available!
<129>Jul 24 16:10:03 node-1 haproxy[28617]: 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 24 16:10:03 node-1 haproxy[28617]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:03 node-1 haproxy[28617]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:03 node-1 haproxy[28617]: proxy keystone-2 has no server available!
<129>Jul 24 16:10:03 node-1 haproxy[28617]: 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 24 16:10:03 node-1 haproxy[28617]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:03 node-1 haproxy[28617]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:03 node-1 haproxy[28617]: proxy glance-api has no server available!
<129>Jul 24 16:10:03 node-1 haproxy[28617]: 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 24 16:10:03 node-1 haproxy[28617]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:04 node-1 haproxy[28621]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:04 node-1 haproxy[28621]: proxy glance-glare has no server available!
<129>Jul 24 16:10:04 node-1 haproxy[28621]: 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 24 16:10:04 node-1 haproxy[28621]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:04 node-1 haproxy[28621]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:04 node-1 haproxy[28621]: proxy neutron has no server available!
<129>Jul 24 16:10:04 node-1 haproxy[28621]: 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 24 16:10:04 node-1 haproxy[28621]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:04 node-1 haproxy[28621]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:04 node-1 haproxy[28621]: proxy glance-registry has no server available!
<129>Jul 24 16:10:04 node-1 haproxy[28621]: 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 24 16:10:04 node-1 haproxy[28621]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:04 node-1 haproxy[28621]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:04 node-1 haproxy[28621]: proxy mysqld has no server available!
<129>Jul 24 16:10:04 node-1 haproxy[28621]: 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 24 16:10:04 node-1 haproxy[28621]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:04 node-1 haproxy[28621]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:04 node-1 haproxy[28621]: proxy object-storage has no server available!
<129>Jul 24 16:10:04 node-1 haproxy[28621]: 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 24 16:10:04 node-1 haproxy[28621]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:04 node-1 haproxy[28621]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:04 node-1 haproxy[28621]: proxy aodh has no server available!
<129>Jul 24 16:10:04 node-1 haproxy[28621]: 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 24 16:10:04 node-1 haproxy[28621]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:05 node-1 haproxy[28621]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:05 node-1 haproxy[28621]: proxy ceilometer has no server available!
<27>Jul 24 16:10:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:06 node-1 multipathd: uevent trigger error
<129>Jul 24 16:10:08 node-1 haproxy[29928]: 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 24 16:10:09 node-1 haproxy[29932]: 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 24 16:10:09 node-1 haproxy[29932]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:09 node-1 haproxy[29932]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:09 node-1 haproxy[29932]: proxy keystone-1 has no server available!
<129>Jul 24 16:10:09 node-1 haproxy[29932]: 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 24 16:10:09 node-1 haproxy[29932]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:09 node-1 haproxy[29932]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:09 node-1 haproxy[29932]: proxy keystone-2 has no server available!
<129>Jul 24 16:10:09 node-1 haproxy[29932]: 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 24 16:10:09 node-1 haproxy[29932]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:09 node-1 haproxy[29932]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:09 node-1 haproxy[29932]: proxy nova-api has no server available!
<129>Jul 24 16:10:09 node-1 haproxy[29932]: 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 24 16:10:09 node-1 haproxy[29932]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:09 node-1 haproxy[29932]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:09 node-1 haproxy[29932]: proxy nova-metadata-api has no server available!
<129>Jul 24 16:10:09 node-1 haproxy[29932]: 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 24 16:10:09 node-1 haproxy[29932]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:09 node-1 haproxy[29932]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:09 node-1 haproxy[29932]: proxy glance-api has no server available!
<129>Jul 24 16:10:09 node-1 haproxy[29932]: 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 24 16:10:09 node-1 haproxy[29932]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:09 node-1 haproxy[29932]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:09 node-1 haproxy[29932]: proxy glance-glare has no server available!
<129>Jul 24 16:10:09 node-1 haproxy[29932]: 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 24 16:10:09 node-1 haproxy[29932]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:10 node-1 haproxy[29932]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:10 node-1 haproxy[29932]: proxy neutron has no server available!
<129>Jul 24 16:10:10 node-1 haproxy[29932]: 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 24 16:10:10 node-1 haproxy[29932]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:10 node-1 haproxy[29932]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:10 node-1 haproxy[29932]: proxy glance-registry has no server available!
<129>Jul 24 16:10:10 node-1 haproxy[29932]: 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 24 16:10:10 node-1 haproxy[29932]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:10 node-1 haproxy[29932]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:10 node-1 haproxy[29932]: proxy mysqld has no server available!
<129>Jul 24 16:10:10 node-1 haproxy[29932]: 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 24 16:10:10 node-1 haproxy[29932]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:10 node-1 haproxy[29932]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:10 node-1 haproxy[29932]: proxy object-storage has no server available!
<129>Jul 24 16:10:10 node-1 haproxy[29932]: 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 24 16:10:10 node-1 haproxy[29932]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:10 node-1 haproxy[29932]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:10 node-1 haproxy[29932]: proxy aodh has no server available!
<129>Jul 24 16:10:10 node-1 haproxy[29932]: 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 24 16:10:10 node-1 haproxy[29932]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:10 node-1 haproxy[29932]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:10 node-1 haproxy[29932]: proxy ceilometer has no server available!
<129>Jul 24 16:10:10 node-1 haproxy[29932]: 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 24 16:10:10 node-1 haproxy[29932]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:10 node-1 haproxy[29932]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:10 node-1 haproxy[29932]: proxy nova-novncproxy has no server available!
<27>Jul 24 16:10:11 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:11 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:11 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:11 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:12 node-1 multipathd: uevent trigger error
<129>Jul 24 16:10:14 node-1 haproxy[31207]: 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 24 16:10:14 node-1 haproxy[31207]: 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 24 16:10:14 node-1 haproxy[31207]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:14 node-1 haproxy[31207]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:14 node-1 haproxy[31207]: proxy keystone-1 has no server available!
<129>Jul 24 16:10:14 node-1 haproxy[31207]: 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 24 16:10:14 node-1 haproxy[31207]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:14 node-1 haproxy[31207]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:14 node-1 haproxy[31207]: proxy keystone-2 has no server available!
<129>Jul 24 16:10:14 node-1 haproxy[31207]: 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 24 16:10:14 node-1 haproxy[31207]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:14 node-1 haproxy[31207]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:14 node-1 haproxy[31207]: proxy nova-api has no server available!
<129>Jul 24 16:10:14 node-1 haproxy[31207]: 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 24 16:10:14 node-1 haproxy[31207]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:14 node-1 haproxy[31207]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:14 node-1 haproxy[31207]: proxy nova-metadata-api has no server available!
<129>Jul 24 16:10:14 node-1 haproxy[31207]: 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 24 16:10:14 node-1 haproxy[31207]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:14 node-1 haproxy[31207]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:14 node-1 haproxy[31207]: proxy cinder-api has no server available!
<129>Jul 24 16:10:14 node-1 haproxy[31207]: 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 24 16:10:14 node-1 haproxy[31207]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy glance-api has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy glance-glare has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy neutron has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy glance-registry has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy mysqld has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy object-storage has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy aodh has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:15 node-1 haproxy[31211]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:15 node-1 haproxy[31211]: proxy ceilometer has no server available!
<129>Jul 24 16:10:15 node-1 haproxy[31211]: 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 24 16:10:15 node-1 haproxy[31211]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:16 node-1 haproxy[31211]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:16 node-1 haproxy[31211]: proxy nova-novncproxy has no server available!
<27>Jul 24 16:10:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:17 node-1 multipathd: uevent trigger error
<129>Jul 24 16:10:19 node-1 haproxy[32540]: 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 24 16:10:19 node-1 haproxy[32540]: 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 24 16:10:20 node-1 haproxy[32544]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy keystone-1 has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy keystone-2 has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy nova-api has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy nova-metadata-api has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy cinder-api has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy glance-api has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy glance-glare has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy neutron has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:20 node-1 haproxy[32544]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:20 node-1 haproxy[32544]: proxy glance-registry has no server available!
<129>Jul 24 16:10:20 node-1 haproxy[32544]: 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 24 16:10:20 node-1 haproxy[32544]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy mysqld has no server available!
<129>Jul 24 16:10:21 node-1 haproxy[32544]: 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 24 16:10:21 node-1 haproxy[32544]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy object-storage has no server available!
<129>Jul 24 16:10:21 node-1 haproxy[32544]: 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 24 16:10:21 node-1 haproxy[32544]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy aodh has no server available!
<129>Jul 24 16:10:21 node-1 haproxy[32544]: 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 24 16:10:21 node-1 haproxy[32544]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy ceilometer has no server available!
<129>Jul 24 16:10:21 node-1 haproxy[32544]: 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 24 16:10:21 node-1 haproxy[32544]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy heat-api has no server available!
<129>Jul 24 16:10:21 node-1 haproxy[32544]: 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 24 16:10:21 node-1 haproxy[32544]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy heat-api-cfn has no server available!
<129>Jul 24 16:10:21 node-1 haproxy[32544]: 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 24 16:10:21 node-1 haproxy[32544]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy heat-api-cloudwatch has no server available!
<129>Jul 24 16:10:21 node-1 haproxy[32544]: 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 24 16:10:21 node-1 haproxy[32544]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 16:10:21 node-1 haproxy[32544]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 16:10:21 node-1 haproxy[32544]: proxy nova-novncproxy has no server available!
<27>Jul 24 16:10:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:26 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:26 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:26 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:26 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:26 node-1 multipathd: uevent trigger error
<27>Jul 24 16:10:36 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 16:10:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:11:02 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 24 16:11:04 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 24 16:11:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 16:11:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:11:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:11:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:11:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:11:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:11:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:14:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:20 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:53 node-1 multipathd: uevent trigger error
<43>Jul 24 16:14:53 node-1 apache2_error [Sun Jul 24 16:14:45.989225 2016] [mpm_event:notice] [pid 12778:tid 140407964804992] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 16:14:53 node-1 apache2_error [Sun Jul 24 16:14:45.989313 2016] [core:notice] [pid 12778:tid 140407964804992] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 16:14:53 node-1 apache2_error [Sun Jul 24 16:14:48.376287 2016] [mpm_event:notice] [pid 12778:tid 140407964804992] AH00491: caught SIGTERM, shutting down
<43>Jul 24 16:14:53 node-1 apache2_error [Sun Jul 24 16:14:49.461543 2016] [mpm_worker:notice] [pid 13095:tid 140566305470336] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 16:14:53 node-1 apache2_error [Sun Jul 24 16:14:49.461605 2016] [core:notice] [pid 13095:tid 140566305470336] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 16:14:56 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:14:57 node-1 multipathd: uevent trigger error
<43>Jul 24 16:16:14 node-1 apache2_error [Sun Jul 24 16:16:13.871793 2016] [mpm_worker:notice] [pid 13095:tid 140566305470336] AH00295: caught SIGTERM, shutting down
<43>Jul 24 16:16:24 node-1 apache2_error [Sun Jul 24 16:16:14.630931 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 16:16:24 node-1 apache2_error [Sun Jul 24 16:16:14.630975 2016] [core:notice] [pid 27740:tid 140444090967936] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 16:17:04 node-1 apache2_error [Sun Jul 24 16:17:00.670888 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 16:17:04 node-1 apache2_error [Sun Jul 24 16:17:00.866083 2016] [mpm_worker:warn] [pid 27740:tid 140444090967936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 16:17:04 node-1 apache2_error [Sun Jul 24 16:17:00.869657 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 16:17:04 node-1 apache2_error [Sun Jul 24 16:17:00.869676 2016] [core:notice] [pid 27740:tid 140444090967936] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 16:17:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:17:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:17:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:09 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:35 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:35 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:35 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:35 node-1 multipathd: uevent trigger error
<27>Jul 24 16:18:35 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:23 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:37 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:37 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:37 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:37 node-1 multipathd: uevent trigger error
<27>Jul 24 16:19:37 node-1 multipathd: uevent trigger error
<27>Jul 24 16:20:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:20:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:20:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:20:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:20:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:21:47 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:51 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:51 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:51 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:51 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:51 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:51 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:22:57 node-1 multipathd: uevent trigger error
<27>Jul 24 16:23:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:23:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:23:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:23:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:23:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:23:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:25:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:25:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:25:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:25:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:25:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:26:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:26:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:27:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:27:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:27:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:27:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:27:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:32 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:28:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:29:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:31:14 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:14 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:14 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:14 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:14 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:14 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:31:55 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:32:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:50 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:32:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:10 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:10 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:10 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:10 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:10 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:43 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:43 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:43 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:43 node-1 multipathd: uevent trigger error
<27>Jul 24 16:33:43 node-1 multipathd: uevent trigger error
<27>Jul 24 16:34:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:34:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:34:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:34:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:34:49 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:07 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:07 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:07 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:07 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:07 node-1 multipathd: uevent trigger error
<11>Jul 24 16:35:20 node-1 liberasurecode[17673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:20 node-1 liberasurecode[17673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:20 node-1 liberasurecode[17673]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:20 node-1 liberasurecode[17673]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:20 node-1 liberasurecode[17705]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:20 node-1 liberasurecode[17705]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:20 node-1 liberasurecode[17705]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:20 node-1 liberasurecode[17705]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:22 node-1 liberasurecode[18275]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:22 node-1 liberasurecode[18275]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:22 node-1 liberasurecode[18275]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:22 node-1 liberasurecode[18275]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 16:35:25 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 24 16:35:28 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19334]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19374]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19374]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19430]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19430]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19430]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:28 node-1 liberasurecode[19430]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19499]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19499]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19511]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19511]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19523]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19523]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19523]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19523]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19539]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19539]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19539]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:29 node-1 liberasurecode[19539]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:45 node-1 liberasurecode[21856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:45 node-1 liberasurecode[21856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:45 node-1 liberasurecode[21856]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:35:45 node-1 liberasurecode[21856]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 16:35:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:54 node-1 multipathd: uevent trigger error
<27>Jul 24 16:35:54 node-1 multipathd: uevent trigger error
<43>Jul 24 16:36:45 node-1 apache2_error [Sun Jul 24 16:36:39.965130 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 16:36:45 node-1 apache2_error [Sun Jul 24 16:36:40.346093 2016] [mpm_worker:warn] [pid 27740:tid 140444090967936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 16:36:45 node-1 apache2_error [Sun Jul 24 16:36:40.351704 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 16:36:45 node-1 apache2_error [Sun Jul 24 16:36:40.351734 2016] [core:notice] [pid 27740:tid 140444090967936] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 16:37:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:21 node-1 multipathd: uevent trigger error
<43>Jul 24 16:37:25 node-1 apache2_error [Sun Jul 24 16:37:17.601943 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 16:37:25 node-1 apache2_error [Sun Jul 24 16:37:17.798767 2016] [mpm_worker:warn] [pid 27740:tid 140444090967936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 16:37:25 node-1 apache2_error [Sun Jul 24 16:37:17.810830 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 16:37:25 node-1 apache2_error [Sun Jul 24 16:37:17.810862 2016] [core:notice] [pid 27740:tid 140444090967936] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 16:37:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:37:28 node-1 multipathd: uevent trigger error
<43>Jul 24 16:38:05 node-1 apache2_error [Sun Jul 24 16:38:02.564490 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 16:38:05 node-1 apache2_error [Sun Jul 24 16:38:02.950283 2016] [mpm_worker:warn] [pid 27740:tid 140444090967936] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 16:38:05 node-1 apache2_error [Sun Jul 24 16:38:02.960555 2016] [mpm_worker:notice] [pid 27740:tid 140444090967936] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 16:38:05 node-1 apache2_error [Sun Jul 24 16:38:02.960581 2016] [core:notice] [pid 27740:tid 140444090967936] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 16:38:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:06 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:13 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:18 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:18 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:18 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:18 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:18 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:18 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:18 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 16:38:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:27 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:38:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:03 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:10 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 24 16:39:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:19 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:24 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:28 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:33 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:45 node-1 multipathd: uevent trigger error
<27>Jul 24 16:39:46 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<11>Jul 24 16:40:01 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:40:01 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:40:01 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:40:01 node-1 liberasurecode[12183]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 16:40:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:16 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:29 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:36 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:36 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:36 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:36 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:41 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:41 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:41 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:41 node-1 multipathd: uevent trigger error
<27>Jul 24 16:40:41 node-1 multipathd: uevent trigger error
<27>Jul 24 16:41:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:41:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:41:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:41:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:41:58 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:12 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:17 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:21 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:30 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:34 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:39 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:43 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:44 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:48 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:53 node-1 multipathd: uevent trigger error
<27>Jul 24 16:42:53 node-1 multipathd: uevent trigger error
<11>Jul 24 16:45:01 node-1 liberasurecode[831]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:45:01 node-1 liberasurecode[831]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:45:01 node-1 liberasurecode[831]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 16:45:01 node-1 liberasurecode[831]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
