Jul 22 11:14:25 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] start
Jul 22 11:14:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 22 11:14:25 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 22 11:14:25 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 22 11:14:25 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 22 11:14:25 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 22 11:14:25 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 22 11:14:25 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 22 11:14:25 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=1acf71ba-4e14-40e0-a826-17b931b26112 nomdmonddf nomdmonisw
Jul 22 11:14:25 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 22 11:14:25 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 22 11:14:25 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 22 11:14:25 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 22 11:14:25 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 22 11:14:25 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 22 11:14:25 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 22 11:14:25 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 22 11:14:25 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 22 11:14:25 node-1 kernel: [    0.000000] No AGP bridge found
Jul 22 11:14:25 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 22 11:14:25 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 22 11:14:25 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 22 11:14:25 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 22 11:14:25 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 22 11:14:25 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 22 11:14:25 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 22 11:14:25 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 22 11:14:25 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 22 11:14:25 node-1 kernel: [    0.000000]   2 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000]   3 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000]   4 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000]   5 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000]   6 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000]   7 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000]   8 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000]   9 disabled
Jul 22 11:14:25 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 22 11:14:25 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 22 11:14:25 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 22 11:14:25 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 22 11:14:25 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 22 11:14:25 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 22 11:14:25 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 22 11:14:25 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 22 11:14:25 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 22 11:14:25 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 22 11:14:25 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 22 11:14:25 node-1 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 22 11:14:25 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 22 11:14:25 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 22 11:14:25 node-1 kernel: [    0.000000] Zone ranges:
Jul 22 11:14:25 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 22 11:14:25 node-1 kernel: [    0.000000] Early memory node ranges
Jul 22 11:14:25 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 22 11:14:25 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 22 11:14:25 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 22 11:14:25 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 22 11:14:25 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 22 11:14:25 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 22 11:14:25 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 22 11:14:25 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 22 11:14:25 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 22 11:14:25 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 22 11:14:25 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 22 11:14:25 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 22 11:14:25 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 22 11:14:25 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 22 11:14:25 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 22 11:14:25 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 22 11:14:25 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 22 11:14:25 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 22 11:14:25 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 22 11:14:25 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 22 11:14:25 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 22 11:14:25 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 22 11:14:25 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 22 11:14:25 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 22 11:14:25 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 22 11:14:25 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 22 11:14:25 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=1acf71ba-4e14-40e0-a826-17b931b26112 nomdmonddf nomdmonisw
Jul 22 11:14:25 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 22 11:14:25 node-1 kernel: [    0.000000] Checking aperture...
Jul 22 11:14:25 node-1 kernel: [    0.000000] No AGP bridge found
Jul 22 11:14:25 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 22 11:14:25 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 22 11:14:25 node-1 kernel: [    0.000000] Memory: 32653308K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627188K reserved)
Jul 22 11:14:25 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 22 11:14:25 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 22 11:14:25 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 22 11:14:25 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 22 11:14:25 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 22 11:14:25 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 22 11:14:25 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 22 11:14:25 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 22 11:14:25 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 22 11:14:25 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 22 11:14:25 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 22 11:14:25 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 22 11:14:25 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 22 11:14:25 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 22 11:14:25 node-1 kernel: [    0.004000] tsc: Detected 3491.613 MHz processor
Jul 22 11:14:25 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.22 BogoMIPS (lpj=13966452)
Jul 22 11:14:25 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 22 11:14:25 node-1 kernel: [    0.000044] Security Framework initialized
Jul 22 11:14:25 node-1 kernel: [    0.000063] AppArmor: AppArmor initialized
Jul 22 11:14:25 node-1 kernel: [    0.000064] Yama: becoming mindful.
Jul 22 11:14:25 node-1 kernel: [    0.001446] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.006375] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.008299] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.008326] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.008604] Initializing cgroup subsys memory
Jul 22 11:14:25 node-1 kernel: [    0.008612] Initializing cgroup subsys devices
Jul 22 11:14:25 node-1 kernel: [    0.008614] Initializing cgroup subsys freezer
Jul 22 11:14:25 node-1 kernel: [    0.008615] Initializing cgroup subsys blkio
Jul 22 11:14:25 node-1 kernel: [    0.008617] Initializing cgroup subsys perf_event
Jul 22 11:14:25 node-1 kernel: [    0.008619] Initializing cgroup subsys hugetlb
Jul 22 11:14:25 node-1 kernel: [    0.008638] CPU: Physical Processor ID: 0
Jul 22 11:14:25 node-1 kernel: [    0.008639] CPU: Processor Core ID: 0
Jul 22 11:14:25 node-1 kernel: [    0.008643] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 22 11:14:25 node-1 kernel: [    0.008643] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 22 11:14:25 node-1 kernel: [    0.009337] mce: CPU supports 22 MCE banks
Jul 22 11:14:25 node-1 kernel: [    0.009365] CPU0: Thermal monitoring enabled (TM1)
Jul 22 11:14:25 node-1 kernel: [    0.009385] process: using mwait in idle threads
Jul 22 11:14:25 node-1 kernel: [    0.009388] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 22 11:14:25 node-1 kernel: [    0.009388] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 22 11:14:25 node-1 kernel: [    0.009388] tlb_flushall_shift: 6
Jul 22 11:14:25 node-1 kernel: [    0.009477] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 22 11:14:25 node-1 kernel: [    0.010199] ACPI: Core revision 20131115
Jul 22 11:14:25 node-1 kernel: [    0.022895] ACPI: All ACPI Tables successfully acquired
Jul 22 11:14:25 node-1 kernel: [    0.023057] ftrace: allocating 28617 entries in 112 pages
Jul 22 11:14:25 node-1 kernel: [    0.031890] dmar: Host address width 46
Jul 22 11:14:25 node-1 kernel: [    0.031892] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 22 11:14:25 node-1 kernel: [    0.031898] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 11:14:25 node-1 kernel: [    0.031899] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 22 11:14:25 node-1 kernel: [    0.031903] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 11:14:25 node-1 kernel: [    0.031905] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 22 11:14:25 node-1 kernel: [    0.031906] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 22 11:14:25 node-1 kernel: [    0.031907] dmar: ATSR flags: 0x0
Jul 22 11:14:25 node-1 kernel: [    0.031908] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 22 11:14:25 node-1 kernel: [    0.031909] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 22 11:14:25 node-1 kernel: [    0.032025] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 22 11:14:25 node-1 kernel: [    0.032026] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 11:14:25 node-1 kernel: [    0.032027] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 11:14:25 node-1 kernel: [    0.032029] HPET id 0 under DRHD base 0xc7ffc000
Jul 22 11:14:25 node-1 kernel: [    0.032030] Your BIOS is broken and requested that x2apic be disabled.
Jul 22 11:14:25 node-1 kernel: [    0.032030] This will slightly decrease performance.
Jul 22 11:14:25 node-1 kernel: [    0.032030] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 22 11:14:25 node-1 kernel: [    0.032460] Enabled IRQ remapping in xapic mode
Jul 22 11:14:25 node-1 kernel: [    0.032461] x2apic not enabled, IRQ remapping is in xapic mode
Jul 22 11:14:25 node-1 kernel: [    0.032464] Switched APIC routing to physical flat.
Jul 22 11:14:25 node-1 kernel: [    0.033067] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 22 11:14:25 node-1 kernel: [    0.072714] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 22 11:14:25 node-1 kernel: [    0.072720] TSC deadline timer enabled
Jul 22 11:14:25 node-1 kernel: [    0.072727] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 22 11:14:25 node-1 kernel: [    0.072733] ... version:                3
Jul 22 11:14:25 node-1 kernel: [    0.072734] ... bit width:              48
Jul 22 11:14:25 node-1 kernel: [    0.072735] ... generic registers:      4
Jul 22 11:14:25 node-1 kernel: [    0.072736] ... value mask:             0000ffffffffffff
Jul 22 11:14:25 node-1 kernel: [    0.072737] ... max period:             0000ffffffffffff
Jul 22 11:14:25 node-1 kernel: [    0.072738] ... fixed-purpose events:   3
Jul 22 11:14:25 node-1 kernel: [    0.072739] ... event mask:             000000070000000f
Jul 22 11:14:25 node-1 kernel: [    0.074188] x86: Booting SMP configuration:
Jul 22 11:14:25 node-1 kernel: [    0.088291] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 22 11:14:25 node-1 kernel: [    0.074190] .... node  #0, CPUs:        #1  #2  #3
Jul 22 11:14:25 node-1 kernel: [    0.116202] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 22 11:14:25 node-1 kernel: [    0.270339] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 22 11:14:25 node-1 kernel: [    0.325947] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 22 11:14:25 node-1 kernel: [    0.382802] x86: Booted up 2 nodes, 16 CPUs
Jul 22 11:14:25 node-1 kernel: [    0.382806] smpboot: Total of 16 processors activated (111743.37 BogoMIPS)
Jul 22 11:14:25 node-1 kernel: [    0.406789] devtmpfs: initialized
Jul 22 11:14:25 node-1 kernel: [    0.409882] EVM: security.selinux
Jul 22 11:14:25 node-1 kernel: [    0.409884] EVM: security.SMACK64
Jul 22 11:14:25 node-1 kernel: [    0.409885] EVM: security.ima
Jul 22 11:14:25 node-1 kernel: [    0.409886] EVM: security.capability
Jul 22 11:14:25 node-1 kernel: [    0.409936] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.410612] pinctrl core: initialized pinctrl subsystem
Jul 22 11:14:25 node-1 kernel: [    0.410669] regulator-dummy: no parameters
Jul 22 11:14:25 node-1 kernel: [    0.410700] RTC time: 11:13:44, date: 07/22/16
Jul 22 11:14:25 node-1 kernel: [    0.410734] NET: Registered protocol family 16
Jul 22 11:14:25 node-1 kernel: [    0.410817] cpuidle: using governor ladder
Jul 22 11:14:25 node-1 kernel: [    0.410818] cpuidle: using governor menu
Jul 22 11:14:25 node-1 kernel: [    0.410852] ACPI: bus type PCI registered
Jul 22 11:14:25 node-1 kernel: [    0.410853] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 22 11:14:25 node-1 kernel: [    0.410900] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 22 11:14:25 node-1 kernel: [    0.410903] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 22 11:14:25 node-1 kernel: [    0.424635] PCI: Using configuration type 1 for base access
Jul 22 11:14:25 node-1 kernel: [    0.425629] bio: create slab <bio-0> at 0
Jul 22 11:14:25 node-1 kernel: [    0.425908] ACPI: Added _OSI(Module Device)
Jul 22 11:14:25 node-1 kernel: [    0.425910] ACPI: Added _OSI(Processor Device)
Jul 22 11:14:25 node-1 kernel: [    0.425911] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 22 11:14:25 node-1 kernel: [    0.425912] ACPI: Added _OSI(Processor Aggregator Device)
Jul 22 11:14:25 node-1 kernel: [    0.438536] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 22 11:14:25 node-1 kernel: [    0.450096] ACPI: Interpreter enabled
Jul 22 11:14:25 node-1 kernel: [    0.450101] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 22 11:14:25 node-1 kernel: [    0.450105] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 22 11:14:25 node-1 kernel: [    0.450108] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 22 11:14:25 node-1 kernel: [    0.450115] ACPI: (supports S0 S4 S5)
Jul 22 11:14:25 node-1 kernel: [    0.450116] ACPI: Using IOAPIC for interrupt routing
Jul 22 11:14:25 node-1 kernel: [    0.450156] HEST: Table parsing has been initialized.
Jul 22 11:14:25 node-1 kernel: [    0.450159] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 22 11:14:25 node-1 kernel: [    0.450710] ACPI: No dock devices found.
Jul 22 11:14:25 node-1 kernel: [    0.462277] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 22 11:14:25 node-1 kernel: [    0.462282] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 11:14:25 node-1 kernel: [    0.462285] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 11:14:25 node-1 kernel: [    0.462313] PCI host bridge to bus 0000:ff
Jul 22 11:14:25 node-1 kernel: [    0.462315] pci_bus 0000:ff: root bus resource [bus ff]
Jul 22 11:14:25 node-1 kernel: [    0.462323] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462362] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.462392] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462427] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462457] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.462487] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.462518] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462547] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462578] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462606] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462632] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462658] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462686] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462712] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462738] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462765] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462793] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462820] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462847] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.462875] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462901] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.462928] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462954] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.462984] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.463019] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463050] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463079] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463110] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463141] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463172] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463202] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463234] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463265] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463298] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463330] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463363] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463397] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463427] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463455] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463488] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463522] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463560] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463595] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463628] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463659] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463688] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463717] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463746] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463780] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463811] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463842] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463872] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463901] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463931] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463961] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.463992] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464023] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464079] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 22 11:14:25 node-1 kernel: [    0.464082] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 11:14:25 node-1 kernel: [    0.464084] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 11:14:25 node-1 kernel: [    0.464102] PCI host bridge to bus 0000:7f
Jul 22 11:14:25 node-1 kernel: [    0.464103] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 22 11:14:25 node-1 kernel: [    0.464108] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464135] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.464163] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464192] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464213] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.464237] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.464263] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464288] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464310] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464332] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464360] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464384] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464410] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464433] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464458] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464484] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464505] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464528] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464550] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.464573] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464595] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.464616] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464639] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464664] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 11:14:25 node-1 kernel: [    0.464696] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464722] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464748] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464776] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464801] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464829] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464856] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464883] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464907] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464935] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464962] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.464989] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465017] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465043] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465067] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465094] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465119] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465145] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465173] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465199] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465223] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465247] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465272] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465300] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465326] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465352] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465381] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465407] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465429] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465454] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465479] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465508] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.465533] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.466775] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 22 11:14:25 node-1 kernel: [    0.466778] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 11:14:25 node-1 kernel: [    0.467895] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 11:14:25 node-1 kernel: [    0.468405] PCI host bridge to bus 0000:00
Jul 22 11:14:25 node-1 kernel: [    0.468408] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 22 11:14:25 node-1 kernel: [    0.468409] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 22 11:14:25 node-1 kernel: [    0.468411] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 22 11:14:25 node-1 kernel: [    0.468412] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 22 11:14:25 node-1 kernel: [    0.468413] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 22 11:14:25 node-1 kernel: [    0.468415] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 22 11:14:25 node-1 kernel: [    0.468416] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 22 11:14:25 node-1 kernel: [    0.468422] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 22 11:14:25 node-1 kernel: [    0.468504] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.468534] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.468576] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 22 11:14:25 node-1 kernel: [    0.468595] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.468624] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.468664] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 22 11:14:25 node-1 kernel: [    0.468682] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.468711] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.468754] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 22 11:14:25 node-1 kernel: [    0.468770] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.468840] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.468916] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.468991] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 11:14:25 node-1 kernel: [    0.468996] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 22 11:14:25 node-1 kernel: [    0.469080] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 22 11:14:25 node-1 kernel: [    0.469227] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 22 11:14:25 node-1 kernel: [    0.469244] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 22 11:14:25 node-1 kernel: [    0.469323] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.469376] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 22 11:14:25 node-1 kernel: [    0.469397] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.469453] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.469496] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 22 11:14:25 node-1 kernel: [    0.469522] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.469578] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.469621] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 22 11:14:25 node-1 kernel: [    0.469645] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 22 11:14:25 node-1 kernel: [    0.469662] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 22 11:14:25 node-1 kernel: [    0.469740] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.469789] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 22 11:14:25 node-1 kernel: [    0.469815] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 22 11:14:25 node-1 kernel: [    0.470061] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 22 11:14:25 node-1 kernel: [    0.470067] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 22 11:14:25 node-1 kernel: [    0.470073] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.470078] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.470086] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 22 11:14:25 node-1 kernel: [    0.470116] pci 0000:01:00.0: supports D1 D2
Jul 22 11:14:25 node-1 kernel: [    0.476362] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 11:14:25 node-1 kernel: [    0.476368] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 11:14:25 node-1 kernel: [    0.476372] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 11:14:25 node-1 kernel: [    0.476540] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.476573] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 22 11:14:25 node-1 kernel: [    0.484358] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 11:14:25 node-1 kernel: [    0.484364] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.484368] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 11:14:25 node-1 kernel: [    0.484452] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.484524] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.484618] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.484699] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 11:14:25 node-1 kernel: [    0.484716] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.484718] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 11:14:25 node-1 kernel: [    0.484775] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.484901] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.484955] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 11:14:25 node-1 kernel: [    0.484957] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.484959] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.485008] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.485127] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.485166] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.485284] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.485322] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.485442] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.485479] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 22 11:14:25 node-1 kernel: [    0.485598] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 22 11:14:25 node-1 kernel: [    0.485640] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 11:14:25 node-1 kernel: [    0.485642] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.485644] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.485702] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 22 11:14:25 node-1 kernel: [    0.485774] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.485828] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.485868] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 22 11:14:25 node-1 kernel: [    0.485947] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 22 11:14:25 node-1 kernel: [    0.486054] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 11:14:25 node-1 kernel: [    0.486057] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.486059] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.486115] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 22 11:14:25 node-1 kernel: [    0.486168] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.486217] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.486431] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 11:14:25 node-1 kernel: [    0.486435] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 11:14:25 node-1 kernel: [    0.486498] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 22 11:14:25 node-1 kernel: [    0.486551] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.486599] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.486854] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 11:14:25 node-1 kernel: [    0.486858] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 11:14:25 node-1 kernel: [    0.486922] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 22 11:14:25 node-1 kernel: [    0.486984] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.487035] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 22 11:14:25 node-1 kernel: [    0.487259] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 11:14:25 node-1 kernel: [    0.487263] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 11:14:25 node-1 kernel: [    0.487438] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 11:14:25 node-1 kernel: [    0.487476] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 11:14:25 node-1 kernel: [    0.487550] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 22 11:14:25 node-1 kernel: [    0.487569] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 22 11:14:25 node-1 kernel: [    0.487582] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 22 11:14:25 node-1 kernel: [    0.487595] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 22 11:14:25 node-1 kernel: [    0.487645] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 22 11:14:25 node-1 kernel: [    0.492364] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 11:14:25 node-1 kernel: [    0.492373] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 11:14:25 node-1 kernel: [    0.492422] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 22 11:14:25 node-1 kernel: [    0.492910] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 22 11:14:25 node-1 kernel: [    0.492913] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 11:14:25 node-1 kernel: [    0.493037] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 11:14:25 node-1 kernel: [    0.493142] PCI host bridge to bus 0000:80
Jul 22 11:14:25 node-1 kernel: [    0.493144] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 22 11:14:25 node-1 kernel: [    0.493145] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 22 11:14:25 node-1 kernel: [    0.493147] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 22 11:14:25 node-1 kernel: [    0.493155] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.493217] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.493284] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 11:14:25 node-1 kernel: [    0.493345] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 11:14:25 node-1 kernel: [    0.493350] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 22 11:14:25 node-1 kernel: [    0.493421] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 22 11:14:25 node-1 kernel: [    0.493720] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 22 11:14:25 node-1 kernel: [    0.493751] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 22 11:14:25 node-1 kernel: [    0.493781] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 22 11:14:25 node-1 kernel: [    0.493810] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 22 11:14:25 node-1 kernel: [    0.493838] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 11:14:25 node-1 kernel: [    0.493868] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 11:14:25 node-1 kernel: [    0.493898] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 11:14:25 node-1 kernel: [    0.493927] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 11:14:25 node-1 kernel: [    0.494012] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 22 11:14:25 node-1 kernel: [    0.494016] ACPI: \_SB_.UNC1: notify handler is installed
Jul 22 11:14:25 node-1 kernel: [    0.494017] ACPI: \_SB_.UNC0: notify handler is installed
Jul 22 11:14:25 node-1 kernel: [    0.494032] ACPI: \_SB_.PCI0: notify handler is installed
Jul 22 11:14:25 node-1 kernel: [    0.494085] ACPI: \_SB_.PCI1: notify handler is installed
Jul 22 11:14:25 node-1 kernel: [    0.494164] Found 4 acpi root devices
Jul 22 11:14:25 node-1 kernel: [    0.494270] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 22 11:14:25 node-1 kernel: [    0.494272] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 22 11:14:25 node-1 kernel: [    0.494274] vgaarb: loaded
Jul 22 11:14:25 node-1 kernel: [    0.494275] vgaarb: bridge control possible 0000:0c:00.0
Jul 22 11:14:25 node-1 kernel: [    0.494390] SCSI subsystem initialized
Jul 22 11:14:25 node-1 kernel: [    0.494458] libata version 3.00 loaded.
Jul 22 11:14:25 node-1 kernel: [    0.494475] ACPI: bus type USB registered
Jul 22 11:14:25 node-1 kernel: [    0.494485] usbcore: registered new interface driver usbfs
Jul 22 11:14:25 node-1 kernel: [    0.494490] usbcore: registered new interface driver hub
Jul 22 11:14:25 node-1 kernel: [    0.494511] usbcore: registered new device driver usb
Jul 22 11:14:25 node-1 kernel: [    0.494667] PCI: Using ACPI for IRQ routing
Jul 22 11:14:25 node-1 kernel: [    0.498271] PCI: pci_cache_line_size set to 64 bytes
Jul 22 11:14:25 node-1 kernel: [    0.498477] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 22 11:14:25 node-1 kernel: [    0.498478] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 22 11:14:25 node-1 kernel: [    0.498479] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 22 11:14:25 node-1 kernel: [    0.498542] NetLabel: Initializing
Jul 22 11:14:25 node-1 kernel: [    0.498544] NetLabel:  domain hash size = 128
Jul 22 11:14:25 node-1 kernel: [    0.498544] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 22 11:14:25 node-1 kernel: [    0.498554] NetLabel:  unlabeled traffic allowed by default
Jul 22 11:14:25 node-1 kernel: [    0.498609] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 22 11:14:25 node-1 kernel: [    0.498613] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 22 11:14:25 node-1 kernel: [    0.500681] Switched to clocksource hpet
Jul 22 11:14:25 node-1 kernel: [    0.505120] AppArmor: AppArmor Filesystem Enabled
Jul 22 11:14:25 node-1 kernel: [    0.505158] pnp: PnP ACPI init
Jul 22 11:14:25 node-1 kernel: [    0.505170] ACPI: bus type PNP registered
Jul 22 11:14:25 node-1 kernel: [    0.505348] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505359] pnp 00:01: [dma 4]
Jul 22 11:14:25 node-1 kernel: [    0.505377] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505410] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505434] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505455] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505502] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505611] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505614] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 22 11:14:25 node-1 kernel: [    0.505615] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505617] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505618] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505620] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505623] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 22 11:14:25 node-1 kernel: [    0.505625] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505627] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505628] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505629] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505631] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505632] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 22 11:14:25 node-1 kernel: [    0.505635] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505736] pnp 00:07: [dma 0 disabled]
Jul 22 11:14:25 node-1 kernel: [    0.505769] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505851] pnp 00:08: [dma 0 disabled]
Jul 22 11:14:25 node-1 kernel: [    0.505886] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 11:14:25 node-1 kernel: [    0.505943] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 22 11:14:25 node-1 kernel: [    0.506381] pnp: PnP ACPI: found 10 devices
Jul 22 11:14:25 node-1 kernel: [    0.506383] ACPI: bus type PNP unregistered
Jul 22 11:14:25 node-1 kernel: [    0.512395] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 11:14:25 node-1 kernel: [    0.512399] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 11:14:25 node-1 kernel: [    0.512402] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 11:14:25 node-1 kernel: [    0.512407] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 11:14:25 node-1 kernel: [    0.512409] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512424] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512453] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 11:14:25 node-1 kernel: [    0.512470] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512499] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 11:14:25 node-1 kernel: [    0.512514] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 11:14:25 node-1 kernel: [    0.512543] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 11:14:25 node-1 kernel: [    0.512557] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 11:14:25 node-1 kernel: [    0.512586] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 11:14:25 node-1 kernel: [    0.512588] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512603] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512632] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 11:14:25 node-1 kernel: [    0.512634] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512648] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512681] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 11:14:25 node-1 kernel: [    0.512683] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512686] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512690] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 11:14:25 node-1 kernel: [    0.512692] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512695] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512699] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 11:14:25 node-1 kernel: [    0.512705] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 11:14:25 node-1 kernel: [    0.512714] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 11:14:25 node-1 kernel: [    0.512718] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 11:14:25 node-1 kernel: [    0.512725] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 22 11:14:25 node-1 kernel: [    0.512726] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 22 11:14:25 node-1 kernel: [    0.512727] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 22 11:14:25 node-1 kernel: [    0.512728] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 22 11:14:25 node-1 kernel: [    0.512729] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 22 11:14:25 node-1 kernel: [    0.512730] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 22 11:14:25 node-1 kernel: [    0.512731] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 22 11:14:25 node-1 kernel: [    0.512731] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 22 11:14:25 node-1 kernel: [    0.512733] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512734] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512735] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512736] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512736] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512737] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512738] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512739] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512740] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 22 11:14:25 node-1 kernel: [    0.512741] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512742] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 22 11:14:25 node-1 kernel: [    0.512744] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 22 11:14:25 node-1 kernel: [    0.512745] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 22 11:14:25 node-1 kernel: [    0.512746] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 22 11:14:25 node-1 kernel: [    0.512748] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 22 11:14:25 node-1 kernel: [    0.512749] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 22 11:14:25 node-1 kernel: [    0.512789] NET: Registered protocol family 2
Jul 22 11:14:25 node-1 kernel: [    0.513102] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.513477] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.513645] TCP: Hash tables configured (established 262144 bind 65536)
Jul 22 11:14:25 node-1 kernel: [    0.513688] TCP: reno registered
Jul 22 11:14:25 node-1 kernel: [    0.513719] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.513826] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.513987] NET: Registered protocol family 1
Jul 22 11:14:25 node-1 kernel: [    0.548771] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 22 11:14:25 node-1 kernel: [    0.548785] PCI: CLS 64 bytes, default 64
Jul 22 11:14:25 node-1 kernel: [    0.548874] Trying to unpack rootfs image as initramfs...
Jul 22 11:14:25 node-1 kernel: [    0.770623] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Jul 22 11:14:25 node-1 kernel: [    0.770672] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 22 11:14:25 node-1 kernel: [    0.770675] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 22 11:14:25 node-1 kernel: [    0.771106] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771119] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771133] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771145] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771157] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771165] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771170] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771176] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771185] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771196] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771210] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771222] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771232] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771239] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771245] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 22 11:14:25 node-1 kernel: [    0.771252] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 11:14:25 node-1 kernel: [    0.771297] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 22 11:14:25 node-1 kernel: [    0.771300] Scanning for low memory corruption every 60 seconds
Jul 22 11:14:25 node-1 kernel: [    0.771587] Initialise system trusted keyring
Jul 22 11:14:25 node-1 kernel: [    0.771637] audit: initializing netlink socket (disabled)
Jul 22 11:14:25 node-1 kernel: [    0.771653] type=2000 audit(1469186024.724:1): initialized
Jul 22 11:14:25 node-1 kernel: [    0.789581] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 22 11:14:25 node-1 kernel: [    0.791052] zbud: loaded
Jul 22 11:14:25 node-1 kernel: [    0.791171] VFS: Disk quotas dquot_6.5.2
Jul 22 11:14:25 node-1 kernel: [    0.791210] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 22 11:14:25 node-1 kernel: [    0.791580] fuse init (API version 7.22)
Jul 22 11:14:25 node-1 kernel: [    0.791632] msgmni has been set to 32768
Jul 22 11:14:25 node-1 kernel: [    0.791681] Key type big_key registered
Jul 22 11:14:25 node-1 kernel: [    0.792136] Key type asymmetric registered
Jul 22 11:14:25 node-1 kernel: [    0.792137] Asymmetric key parser 'x509' registered
Jul 22 11:14:25 node-1 kernel: [    0.792160] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 22 11:14:25 node-1 kernel: [    0.792229] io scheduler noop registered
Jul 22 11:14:25 node-1 kernel: [    0.792231] io scheduler deadline registered (default)
Jul 22 11:14:25 node-1 kernel: [    0.792249] io scheduler cfq registered
Jul 22 11:14:25 node-1 kernel: [    0.792788] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    0.793014] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    0.793133] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    0.793248] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    0.793376] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    0.793466] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    0.793837] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 22 11:14:26 node-1 kernel: [    0.793863] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 22 11:14:26 node-1 kernel: [    0.793879] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 22 11:14:26 node-1 kernel: [    0.793891] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793894] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793896] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 22 11:14:26 node-1 kernel: [    0.793902] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793903] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793904] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793906] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793907] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793909] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793910] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793912] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793913] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793914] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793916] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793917] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793920] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 22 11:14:26 node-1 kernel: [    0.793937] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793939] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 22 11:14:26 node-1 kernel: [    0.793950] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793953] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 22 11:14:26 node-1 kernel: [    0.793964] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793966] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 22 11:14:26 node-1 kernel: [    0.793969] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 22 11:14:26 node-1 kernel: [    0.794010] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 22 11:14:26 node-1 kernel: [    0.794016] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 22 11:14:26 node-1 kernel: [    0.794019] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 22 11:14:26 node-1 kernel: [    0.794028] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 22 11:14:26 node-1 kernel: [    0.794065] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 22 11:14:26 node-1 kernel: [    0.794066] vesafb: scrolling: redraw
Jul 22 11:14:26 node-1 kernel: [    0.794068] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 22 11:14:26 node-1 kernel: [    0.812738] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 22 11:14:26 node-1 kernel: [    0.821232] Console: switching to colour frame buffer device 80x30
Jul 22 11:14:26 node-1 kernel: [    0.829905] fb0: VESA VGA frame buffer device
Jul 22 11:14:26 node-1 kernel: [    0.830104] intel_idle: MWAIT substates: 0x2120
Jul 22 11:14:26 node-1 kernel: [    0.830105] intel_idle: v0.4 model 0x3F
Jul 22 11:14:26 node-1 kernel: [    0.830106] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 22 11:14:26 node-1 kernel: [    0.830341] ipmi message handler version 39.2
Jul 22 11:14:26 node-1 kernel: [    0.830615] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 22 11:14:26 node-1 kernel: [    0.831045] ACPI: AC Adapter [P111] (on-line)
Jul 22 11:14:26 node-1 kernel: [    0.836273] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 22 11:14:26 node-1 kernel: [    0.847259] ACPI: Power Button [PWRB]
Jul 22 11:14:26 node-1 kernel: [    0.853059] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 22 11:14:26 node-1 kernel: [    0.864667] ACPI: Power Button [PWRF]
Jul 22 11:14:26 node-1 kernel: [    0.882106] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 22 11:14:26 node-1 kernel: [    0.893758] pstore: Registered erst as persistent store backend
Jul 22 11:14:26 node-1 kernel: [    0.899924] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 22 11:14:26 node-1 kernel: [    0.911871] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 22 11:14:26 node-1 kernel: [    0.938600] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 22 11:14:26 node-1 kernel: [    0.971875] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 22 11:14:26 node-1 kernel: [    0.985905] Linux agpgart interface v0.103
Jul 22 11:14:26 node-1 kernel: [    0.993570] brd: module loaded
Jul 22 11:14:26 node-1 kernel: [    1.000621] loop: module loaded
Jul 22 11:14:26 node-1 kernel: [    1.007340] libphy: Fixed MDIO Bus: probed
Jul 22 11:14:26 node-1 kernel: [    1.013805] tun: Universal TUN/TAP device driver, 1.6
Jul 22 11:14:26 node-1 kernel: [    1.020271] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 22 11:14:26 node-1 kernel: [    1.026787] PPP generic driver version 2.4.2
Jul 22 11:14:26 node-1 kernel: [    1.033184] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 22 11:14:26 node-1 kernel: [    1.039616] ehci-pci: EHCI PCI platform driver
Jul 22 11:14:26 node-1 kernel: [    1.046134] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 22 11:14:26 node-1 kernel: [    1.052536] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 22 11:14:26 node-1 kernel: [    1.065114] ehci-pci 0000:00:1a.0: debug port 2
Jul 22 11:14:26 node-1 kernel: [    1.075359] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 22 11:14:26 node-1 kernel: [    1.075377] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 22 11:14:26 node-1 kernel: [    1.092170] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 22 11:14:26 node-1 kernel: [    1.098237] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 11:14:26 node-1 kernel: [    1.104406] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 11:14:26 node-1 kernel: [    1.116329] usb usb1: Product: EHCI Host Controller
Jul 22 11:14:26 node-1 kernel: [    1.122360] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 11:14:26 node-1 kernel: [    1.128408] usb usb1: SerialNumber: 0000:00:1a.0
Jul 22 11:14:26 node-1 kernel: [    1.134382] hub 1-0:1.0: USB hub found
Jul 22 11:14:26 node-1 kernel: [    1.140164] hub 1-0:1.0: 2 ports detected
Jul 22 11:14:26 node-1 kernel: [    1.145970] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 22 11:14:26 node-1 kernel: [    1.151627] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 22 11:14:26 node-1 kernel: [    1.162678] ehci-pci 0000:00:1d.0: debug port 2
Jul 22 11:14:26 node-1 kernel: [    1.172076] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 22 11:14:26 node-1 kernel: [    1.172079] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 22 11:14:26 node-1 kernel: [    1.188088] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 22 11:14:26 node-1 kernel: [    1.193326] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 11:14:26 node-1 kernel: [    1.198655] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 11:14:26 node-1 kernel: [    1.209269] usb usb2: Product: EHCI Host Controller
Jul 22 11:14:26 node-1 kernel: [    1.214770] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 11:14:26 node-1 kernel: [    1.220321] usb usb2: SerialNumber: 0000:00:1d.0
Jul 22 11:14:26 node-1 kernel: [    1.225881] hub 2-0:1.0: USB hub found
Jul 22 11:14:26 node-1 kernel: [    1.231260] hub 2-0:1.0: 2 ports detected
Jul 22 11:14:26 node-1 kernel: [    1.236593] ehci-platform: EHCI generic platform driver
Jul 22 11:14:26 node-1 kernel: [    1.241847] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 22 11:14:26 node-1 kernel: [    1.247191] ohci-pci: OHCI PCI platform driver
Jul 22 11:14:26 node-1 kernel: [    1.252518] ohci-platform: OHCI generic platform driver
Jul 22 11:14:26 node-1 kernel: [    1.257746] uhci_hcd: USB Universal Host Controller Interface driver
Jul 22 11:14:26 node-1 kernel: [    1.263097] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 22 11:14:26 node-1 kernel: [    1.455866] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 22 11:14:26 node-1 kernel: [    1.632045] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 22 11:14:26 node-1 kernel: [    1.637574] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 11:14:26 node-1 kernel: [    1.643313] hub 1-1:1.0: USB hub found
Jul 22 11:14:26 node-1 kernel: [    1.648781] hub 1-1:1.0: 6 ports detected
Jul 22 11:14:26 node-1 kernel: [    1.763599] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 22 11:14:26 node-1 kernel: [    2.027709] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 22 11:14:26 node-1 kernel: [    2.033142] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 11:14:26 node-1 kernel: [    2.038848] hub 2-1:1.0: USB hub found
Jul 22 11:14:26 node-1 kernel: [    2.044445] hub 2-1:1.0: 8 ports detected
Jul 22 11:14:26 node-1 kernel: [    2.303840] i8042: No controller found
Jul 22 11:14:26 node-1 kernel: [    2.309249] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 22 11:14:26 node-1 kernel: [    2.310527] mousedev: PS/2 mouse device common for all mice
Jul 22 11:14:26 node-1 kernel: [    2.312360] rtc_cmos 00:02: RTC can wake from S4
Jul 22 11:14:26 node-1 kernel: [    2.313931] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 22 11:14:26 node-1 kernel: [    2.314537] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 22 11:14:26 node-1 kernel: [    2.315633] device-mapper: uevent: version 1.0.3
Jul 22 11:14:26 node-1 kernel: [    2.316727] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 22 11:14:26 node-1 kernel: [    2.316868] ledtrig-cpu: registered to indicate activity on CPUs
Jul 22 11:14:26 node-1 kernel: [    2.318823] TCP: cubic registered
Jul 22 11:14:26 node-1 kernel: [    2.320146] NET: Registered protocol family 10
Jul 22 11:14:26 node-1 kernel: [    2.322960] NET: Registered protocol family 17
Jul 22 11:14:26 node-1 kernel: [    2.323197] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 22 11:14:26 node-1 kernel: [    2.323312] Key type dns_resolver registered
Jul 22 11:14:26 node-1 kernel: [    2.329876] Loading compiled-in X.509 certificates
Jul 22 11:14:26 node-1 kernel: [    2.331841] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 22 11:14:26 node-1 kernel: [    2.332157] registered taskstats version 1
Jul 22 11:14:26 node-1 kernel: [    2.372378] Key type trusted registered
Jul 22 11:14:26 node-1 kernel: [    2.393899] Key type encrypted registered
Jul 22 11:14:26 node-1 kernel: [    2.393955] AppArmor: AppArmor sha1 policy hashing enabled
Jul 22 11:14:26 node-1 kernel: [    2.393973] IMA: No TPM chip found, activating TPM-bypass!
Jul 22 11:14:26 node-1 kernel: [    2.402797] regulator-dummy: disabling
Jul 22 11:14:26 node-1 kernel: [    2.403796]   Magic number: 8:991:226
Jul 22 11:14:26 node-1 kernel: [    2.403907]  port3: hash matches
Jul 22 11:14:26 node-1 kernel: [    2.403932]  port3: hash matches
Jul 22 11:14:26 node-1 kernel: [    2.405463] acpi device:73: hash matches
Jul 22 11:14:26 node-1 kernel: [    2.406984] memory memory108: hash matches
Jul 22 11:14:26 node-1 kernel: [    2.461211] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 22 11:14:26 node-1 kernel: [    2.461214] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 22 11:14:26 node-1 kernel: [    2.461216] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 22 11:14:26 node-1 kernel: [    2.461217] usb 2-1.4: Manufacturer: Avocent
Jul 22 11:14:26 node-1 kernel: [    2.461219] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 22 11:14:26 node-1 kernel: [    2.500451] rtc_cmos 00:02: setting system clock to 2016-07-22 11:13:46 UTC (1469186026)
Jul 22 11:14:26 node-1 kernel: [    2.512400] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 22 11:14:26 node-1 kernel: [    2.517680] EDD information not available.
Jul 22 11:14:26 node-1 kernel: [    2.522901] PM: Hibernation image not present or could not be loaded.
Jul 22 11:14:26 node-1 kernel: [    2.523766] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 22 11:14:26 node-1 kernel: [    2.534354] Write protecting the kernel read-only data: 12288k
Jul 22 11:14:26 node-1 kernel: [    2.540464] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 22 11:14:26 node-1 kernel: [    2.552702] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 22 11:14:26 node-1 kernel: [    2.583368] device-mapper: multipath: version 1.6.0 loaded
Jul 22 11:14:26 node-1 kernel: [    2.590926] systemd-udevd[216]: starting version 204
Jul 22 11:14:26 node-1 kernel: [    2.614112] md: linear personality registered for level -1
Jul 22 11:14:26 node-1 kernel: [    2.627910] md: multipath personality registered for level -4
Jul 22 11:14:26 node-1 kernel: [    2.635661] md: raid0 personality registered for level 0
Jul 22 11:14:26 node-1 kernel: [    2.643691] md: raid1 personality registered for level 1
Jul 22 11:14:26 node-1 kernel: [    2.654888] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 22 11:14:26 node-1 kernel: [    2.654890] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 22 11:14:26 node-1 kernel: [    2.666794] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 22 11:14:26 node-1 kernel: [    2.666796] 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 22 11:14:26 node-1 kernel: [    2.666798] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 11:14:26 node-1 kernel: [    2.667298] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.667413] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.667582] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.667721] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.668185] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.683083] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 22 11:14:26 node-1 kernel: [    2.683084] 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 22 11:14:26 node-1 kernel: [    2.683085] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 11:14:26 node-1 kernel: [    2.683297] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.683368] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.683472] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.683607] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.683863] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.700241] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 22 11:14:26 node-1 kernel: [    2.700242] 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 22 11:14:26 node-1 kernel: [    2.700243] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 11:14:26 node-1 kernel: [    2.700355] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.700473] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.700608] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.700750] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.700938] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.718181] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 22 11:14:26 node-1 kernel: [    2.718182] 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 22 11:14:26 node-1 kernel: [    2.718183] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 11:14:26 node-1 kernel: [    2.718457] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.718561] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.718763] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.718861] raid6: sse2x1   11015 MB/s
Jul 22 11:14:26 node-1 kernel: [    2.718960] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.719161] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.786807] raid6: sse2x2   13933 MB/s
Jul 22 11:14:26 node-1 kernel: [    2.854787] raid6: sse2x4   16949 MB/s
Jul 22 11:14:26 node-1 kernel: [    2.876725] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 22 11:14:26 node-1 kernel: [    2.883591] hidraw: raw HID events driver (C) Jiri Kosina
Jul 22 11:14:26 node-1 kernel: [    2.884588] megasas: FW now in Ready state
Jul 22 11:14:26 node-1 kernel: [    2.884996] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885139] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885287] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885439] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885563] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885633] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885765] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885887] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.885975] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.886084] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.886204] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.886297] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.886437] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.886553] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.886869] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.887023] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 22 11:14:26 node-1 kernel: [    2.887533] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 22 11:14:26 node-1 kernel: [    2.914356] usbcore: registered new interface driver usbhid
Jul 22 11:14:26 node-1 kernel: [    2.921156] usbhid: USB HID core driver
Jul 22 11:14:26 node-1 kernel: [    2.922675] raid6: avx2x1   21159 MB/s
Jul 22 11:14:26 node-1 kernel: [    2.937265] 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 22 11:14:26 node-1 kernel: [    2.950440] 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 22 11:14:26 node-1 kernel: [    2.964145] 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 22 11:14:26 node-1 kernel: [    2.977848] 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 22 11:14:26 node-1 kernel: [    2.990789] raid6: avx2x2    6149 MB/s
Jul 22 11:14:26 node-1 kernel: [    2.998417] 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 22 11:14:26 node-1 kernel: [    3.012575] 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 22 11:14:26 node-1 kernel: [    3.058494] raid6: avx2x4   16249 MB/s
Jul 22 11:14:26 node-1 kernel: [    3.065478] raid6: using algorithm avx2x1 (21159 MB/s)
Jul 22 11:14:26 node-1 kernel: [    3.072397] raid6: using avx2x2 recovery algorithm
Jul 22 11:14:26 node-1 kernel: [    3.080038] xor: automatically using best checksumming function:
Jul 22 11:14:26 node-1 kernel: [    3.126436]    avx       : 35698.000 MB/sec
Jul 22 11:14:26 node-1 kernel: [    3.133898] async_tx: api initialized (async)
Jul 22 11:14:26 node-1 kernel: [    3.144731] md: raid6 personality registered for level 6
Jul 22 11:14:26 node-1 kernel: [    3.151446] md: raid5 personality registered for level 5
Jul 22 11:14:26 node-1 kernel: [    3.158151] md: raid4 personality registered for level 4
Jul 22 11:14:26 node-1 kernel: [    3.167810] md: raid10 personality registered for level 10
Jul 22 11:14:26 node-1 kernel: [    3.221499] multipathd (353): /proc/353/oom_adj is deprecated, please use /proc/353/oom_score_adj instead.
Jul 22 11:14:26 node-1 kernel: [    3.226654] megasas:IOC Init cmd success
Jul 22 11:14:26 node-1 kernel: [    3.250405] megasas: INIT adapter done
Jul 22 11:14:26 node-1 kernel: [    3.350298] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 22 11:14:26 node-1 kernel: [    3.356654] scsi0 : LSI SAS based MegaRAID driver
Jul 22 11:14:26 node-1 kernel: [    3.363833] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 11:14:26 node-1 kernel: [    3.385518] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 11:14:26 node-1 kernel: [    3.400644] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 22 11:14:26 node-1 kernel: [    3.402058] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 22 11:14:26 node-1 kernel: [    3.403062] sd 0:2:0:0: [sda] Write Protect is off
Jul 22 11:14:26 node-1 kernel: [    3.403096] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 22 11:14:26 node-1 kernel: [    3.403567] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 22 11:14:26 node-1 kernel: [    3.439872]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 22 11:14:26 node-1 kernel: [    3.446322] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 22 11:14:26 node-1 kernel: [    3.498330] Switched to clocksource tsc
Jul 22 11:14:26 node-1 kernel: [    3.581225] random: lvm urandom read with 29 bits of entropy available
Jul 22 11:14:26 node-1 kernel: [    3.753853] bio: create slab <bio-1> at 1
Jul 22 11:14:26 node-1 kernel: [    4.582867] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 11:14:26 node-1 kernel: [    5.271316] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 22 11:14:26 node-1 kernel: [    5.305911] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 22 11:14:26 node-1 kernel: [    5.318438] random: nonblocking pool is initialized
Jul 22 11:14:26 node-1 kernel: [    5.490755] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 22 11:14:26 node-1 kernel: [    5.580527] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 22 11:14:26 node-1 kernel: [    5.710504] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 11:14:26 node-1 kernel: [    5.940048] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 22 11:14:26 node-1 kernel: [    5.986361] XFS (dm-0): Mounting Filesystem
Jul 22 11:14:26 node-1 kernel: [    6.174029] XFS (dm-0): Ending clean mount
Jul 22 11:14:26 node-1 kernel: [    6.211386] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 11:14:26 node-1 kernel: [    6.252611] XFS (dm-1): Mounting Filesystem
Jul 22 11:14:26 node-1 kernel: [    6.323186] XFS (dm-1): Ending clean mount
Jul 22 11:14:26 node-1 kernel: [    8.113736] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 22 11:14:26 node-1 kernel: [    8.142408] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 22 11:14:26 node-1 kernel: [    8.277300] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 22 11:14:26 node-1 kernel: [    8.277305] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 22 11:14:26 node-1 kernel: [    8.277308] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 22 11:14:26 node-1 kernel: [    8.277312] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 22 11:14:26 node-1 kernel: [    8.315408] systemd-udevd[777]: starting version 204
Jul 22 11:14:26 node-1 kernel: [    8.511666] power_meter ACPI000D:00: Found ACPI power meter.
Jul 22 11:14:26 node-1 kernel: [    8.511674] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 22 11:14:26 node-1 kernel: [    8.519489] wmi: Mapper loaded
Jul 22 11:14:26 node-1 kernel: [    8.548112] IPMI System Interface driver.
Jul 22 11:14:26 node-1 kernel: [    8.548190] ipmi_si: probing via ACPI
Jul 22 11:14:26 node-1 kernel: [    8.548206] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 22 11:14:26 node-1 kernel: [    8.548208] ipmi_si: Adding ACPI-specified kcs state machine
Jul 22 11:14:26 node-1 kernel: [    8.548220] ipmi_si: probing via SMBIOS
Jul 22 11:14:26 node-1 kernel: [    8.548222] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 11:14:26 node-1 kernel: [    8.548223] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 22 11:14:26 node-1 kernel: [    8.548225] ipmi_si: probing via SPMI
Jul 22 11:14:26 node-1 kernel: [    8.548226] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 11:14:26 node-1 kernel: [    8.548227] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 22 11:14:26 node-1 kernel: [    8.548229] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 22 11:14:26 node-1 kernel: [    8.562849] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 22 11:14:26 node-1 kernel: [    8.575134] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 22 11:14:26 node-1 kernel: [    8.575139] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 11:14:26 node-1 kernel: [    8.575142] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 22 11:14:26 node-1 kernel: [    8.575143] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 11:14:26 node-1 kernel: [    8.575157] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 22 11:14:26 node-1 kernel: [    8.614311] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Jul 22 11:14:26 node-1 kernel: [    8.642182] systemd-udevd[823]: renamed network interface eth1 to enp7s0
Jul 22 11:14:26 node-1 kernel: [    8.689545] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 22 11:14:26 node-1 kernel: [    8.689553] ipmi_si 00:09: IPMI kcs interface initialized
Jul 22 11:14:26 node-1 kernel: [    8.698106] systemd-udevd[795]: renamed network interface eth3 to enp9s0
Jul 22 11:14:26 node-1 kernel: [    8.734093] systemd-udevd[794]: renamed network interface eth2 to enp8s0
Jul 22 11:14:26 node-1 kernel: [    8.942902] type=1400 audit(1469186033.035:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1018 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.943061] type=1400 audit(1469186033.035:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1018 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.943190] type=1400 audit(1469186033.035:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1018 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.943325] type=1400 audit(1469186033.035:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1007 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.943470] type=1400 audit(1469186033.035:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1007 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.943601] type=1400 audit(1469186033.035:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1007 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.957858] type=1400 audit(1469186033.051:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1033 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.957994] type=1400 audit(1469186033.051:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1033 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.958108] type=1400 audit(1469186033.051:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1033 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    8.966379] type=1400 audit(1469186033.059:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1006 comm="apparmor_parser"
Jul 22 11:14:26 node-1 kernel: [    9.486072] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 22 11:14:26 node-1 kernel: [    9.486929] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 22 11:14:26 node-1 kernel: [    9.643602] enic 0000:06:00.0 enp6s0: Link UP
Jul 22 11:14:26 node-1 kernel: [    9.644025] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 22 11:14:26 node-1 kernel: [    9.644034] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 22 11:14:26 node-1 kernel: [   19.202297] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 22 11:14:27 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 22 11:14:27 node-1 kernel: [   42.185973] init: failsafe main process (8407) killed by TERM signal
Jul 22 11:14:27 node-1 dbus[8443]: [system] AppArmor D-Bus mediation is enabled
Jul 22 11:14:27 node-1 kernel: [   42.465026] audit_printk_skb: 30 callbacks suppressed
Jul 22 11:14:27 node-1 kernel: [   42.465028] type=1400 audit(1469186067.338:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8534 comm="apparmor_parser"
Jul 22 11:14:27 node-1 kernel: [   42.465033] type=1400 audit(1469186067.338:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Jul 22 11:14:27 node-1 kernel: [   42.465036] type=1400 audit(1469186067.338:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Jul 22 11:14:27 node-1 kernel: [   42.465255] type=1400 audit(1469186067.338:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8534 comm="apparmor_parser"
Jul 22 11:14:27 node-1 kernel: [   42.465256] type=1400 audit(1469186067.338:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Jul 22 11:14:27 node-1 kernel: [   42.465368] type=1400 audit(1469186067.338:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8534 comm="apparmor_parser"
Jul 22 11:14:27 node-1 kernel: [   42.467995] type=1400 audit(1469186067.342:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8535 comm="apparmor_parser"
Jul 22 11:14:27 node-1 kernel: [   42.572741] type=1400 audit(1469186067.446:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8537 comm="apparmor_parser"
Jul 22 11:14:27 node-1 cron[8565]: (CRON) INFO (pidfile fd = 3)
Jul 22 11:14:27 node-1 anacron[8584]: Anacron 2.3 started on 2016-07-22
Jul 22 11:14:27 node-1 cron[8600]: (CRON) STARTUP (fork ok)
Jul 22 11:14:27 node-1 anacron[8584]: Will run job `cron.daily' in 5 min.
Jul 22 11:14:27 node-1 anacron[8584]: Will run job `cron.weekly' in 10 min.
Jul 22 11:14:27 node-1 anacron[8584]: Will run job `cron.monthly' in 15 min.
Jul 22 11:14:27 node-1 anacron[8584]: Jobs will be executed sequentially
Jul 22 11:14:27 node-1 cron[8600]: (CRON) INFO (Running @reboot jobs)
Jul 22 11:14:27 node-1 multipathd: path checkers start up
Jul 22 11:14:27 node-1 postfix/master[8744]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 22 11:14:31 node-1 puppet-agent[8928]: Reopening log files
Jul 22 11:14:31 node-1 puppet-agent[8928]: Could not request certificate: Connection refused - connect(2)
Jul 22 11:14:42 node-1 puppet-user[9007]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 22 11:14:42 node-1 puppet-user[9007]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 22 11:14:43 node-1 puppet-user[9007]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 22 11:14:43 node-1 puppet-user[9007]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 22 11:14:43 node-1 puppet-user[9007]: Finished catalog run in 0.90 seconds
Jul 22 11:14:44 node-1 multipathd: uevent trigger error
Jul 22 11:14:44 node-1 puppet-user[9547]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 11:14:44 node-1 puppet-user[9547]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 22 11:14:44 node-1 puppet-user[9547]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 22 11:14:44 node-1 puppet-user[9547]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 22 11:14:44 node-1 puppet-user[9547]: (/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 22 11:14:44 node-1 puppet-user[9547]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 22 11:14:44 node-1 puppet-user[9547]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 22 11:14:44 node-1 puppet-user[9547]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 22 11:14:44 node-1 puppet-user[9547]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 22 11:14:44 node-1 puppet-user[9547]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 22 11:14:44 node-1 puppet-user[9547]: Finished catalog run in 0.06 seconds
Jul 22 11:14:46 node-1 puppet-user[10008]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 22 11:14:46 node-1 puppet-user[10008]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 22 11:14:46 node-1 puppet-user[10008]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 22 11:14:46 node-1 puppet-user[10008]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 22 11:14:46 node-1 puppet-user[10008]: Finished catalog run in 0.03 seconds
Jul 22 11:14:47 node-1 puppet-user[10462]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 22 11:14:47 node-1 puppet-user[10462]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 22 11:14:48 node-1 puppet-user[10462]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 22 11:14:48 node-1 puppet-user[10462]: Finished catalog run in 0.04 seconds
Jul 22 11:14:49 node-1 puppet-user[10909]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 22 11:14:49 node-1 puppet-user[10909]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Jul 22 11:14:49 node-1 puppet-user[10909]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 22 11:14:51 node-1 puppet-user[10909]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Jul 22 11:14:51 node-1 puppet-user[10909]: Finished catalog run in 1.91 seconds
Jul 22 11:14:52 node-1 puppet-user[11433]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 22 11:14:52 node-1 puppet-user[11433]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Jul 22 11:14:53 node-1 puppet-user[11433]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 22 11:14:53 node-1 puppet-user[11433]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Jul 22 11:14:53 node-1 puppet-user[11433]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 22 11:14:53 node-1 puppet-user[11433]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 22 11:14:53 node-1 puppet-user[11433]: Finished catalog run in 0.23 seconds
Jul 22 11:14:54 node-1 puppet-user[11908]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 22 11:14:54 node-1 puppet-user[11908]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Jul 22 11:14:55 node-1 puppet-user[11908]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 22 11:14:55 node-1 kernel: [   70.499496] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 22 11:14:55 node-1 kernel: [   70.499548] 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 22 11:14:55 node-1 puppet-user[11908]: (/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 22 11:14:55 node-1 puppet-user[11908]: Finished catalog run in 0.05 seconds
Jul 22 11:14:57 node-1 puppet-user[12550]: (Scope(Class[main])) MODULAR: sync_time
Jul 22 11:14:57 node-1 puppet-user[12550]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 22 11:14:57 node-1 ntpdate[12966]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 22 11:15:01 node-1 CRON[13058]: (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 22 11:15:03 node-1 ntpdate[12966]: adjust time server 10.20.0.2 offset 0.000120 sec
Jul 22 11:15:03 node-1 puppet-user[12550]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 22 11:15:03 node-1 puppet-user[12550]: Finished catalog run in 6.19 seconds
Jul 22 11:15:08 node-1 kernel: [   83.493482] init: plymouth-upstart-bridge main process ended, respawning
Jul 22 11:15:08 node-1 puppet-agent[8928]: Could not run: SIGTERM
Jul 22 11:15:08 node-1 kernel: [   83.743877] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 22 11:15:08 node-1 ec2: 
Jul 22 11:15:08 node-1 ec2: #############################################################
Jul 22 11:15:08 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 22 11:15:08 node-1 ec2: 1024 68:f0:2f:bd:8a:c2:9c:b9:5a:c3:e8:00:6a:b9:f9:8b  root@node-1.domain.tld (DSA)
Jul 22 11:15:08 node-1 ec2: 256 47:01:96:c6:3c:62:76:ab:7b:fa:98:b7:55:83:a6:1e  root@node-1.domain.tld (ECDSA)
Jul 22 11:15:08 node-1 ec2: 256 1b:d4:13:20:a3:62:5c:b3:7b:07:47:24:bd:9d:0d:f3  root@node-1.domain.tld (ED25519)
Jul 22 11:15:08 node-1 ec2: 2048 5d:1b:49:41:91:ab:cd:e2:e7:51:93:a6:88:2f:1c:56  root@node-1.domain.tld (RSA)
Jul 22 11:15:08 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 22 11:15:08 node-1 ec2: #############################################################
Jul 22 11:15:09 node-1 puppet-user[13293]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 11:15:09 node-1 puppet-user[13293]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 22 11:15:09 node-1 puppet-user[13293]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 22 11:15:09 node-1 puppet-user[13293]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 22 11:15:09 node-1 puppet-user[13293]: Finished catalog run in 0.07 seconds
Jul 22 11:15:10 node-1 puppet-user[13797]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 22 11:15:11 node-1 puppet-user[13797]: Compiled catalog for node-1.domain.tld in environment production in 0.99 seconds
Jul 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:11 node-1 puppet-user[13797]: (/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 22 11:15:12 node-1 puppet-user[13797]: (/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 22 11:15:12 node-1 puppet-user[13797]: (/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 22 11:15:23 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 11:15:23 node-1 nailgun-agent: D, [2016-07-22T11:15:01.408751 #13061] DEBUG -- : Sleep for 22 seconds before sending request
Jul 22 11:15:23 node-1 nailgun-agent: I, [2016-07-22T11:15:23.423073 #13061]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 11:15:23 node-1 nailgun-agent: D, [2016-07-22T11:15:23.811268 #13061] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 22 11:15:23 node-1 puppet-user[13797]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 22 11:15:24 node-1 puppet-user[13797]: Finished catalog run in 12.35 seconds
Jul 22 11:15:25 node-1 puppet-user[14818]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 22 11:15:25 node-1 puppet-user[14818]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Jul 22 11:15:30 node-1 puppet-user[14818]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.079455 #13061] DEBUG -- : Trying to find block devices
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.079693 #13061] DEBUG -- : Found block device: sda
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.079797 #13061] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.079859 #13061] DEBUG -- : Trying to get list of physical devices
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.080252 #13061] DEBUG -- : Getting udev properties for device: sda
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.083939 #13061] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /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"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Jul 22 11:15:36 node-1 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3907", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.084061 #13061] DEBUG -- : Trying to find out if device sda is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.084147 #13061] DEBUG -- : Device sda removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.084176 #13061] DEBUG -- : Device sda seems to be appropriate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.084953 #13061] DEBUG -- : Getting udev properties for device: dm-0
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.088378 #13061] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-MpcZcXqDIiq3UrIK7marJ59q2KHdVTjETdWUDjrOTYAOoE3CtgnKF5ohWll6Qnxw /dev/disk/by-uuid/a65910d6-d959-48ac-881f-29eb5b6e8e49 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "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-MpcZcXqDIiq3UrIK7marJ59q2KHdVTjETdWUDjrOTYAOoE3CtgnKF5ohWll6Qnxw", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a65910d6-d959-48ac-881f-29eb5b6e8e49", "ID_FS_UUID_ENC"=>"a65910d6-d959-48ac-881f-29eb5b6e8e49", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11926", "nomdmonddf"=>"1", "nom
Jul 22 11:15:36 node-1 nailgun-agent: dmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.088437 #13061] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.088503 #13061] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.088549 #13061] DEBUG -- : Device dm-0 seems to be appropriate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.088582 #13061] DEBUG -- : Getting udev properties for device: dm-1
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.092225 #13061] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-iVHNkHghc9k1BSxYDODk7cq4uUkutc1cStTw7BqVJ1GuDjbVFRQqeqLpNh3VQhYI /dev/disk/by-uuid/a8b9537b-bca4-44b0-a408-4cbc4841f2b3 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-iVHNkHghc9k1BSxYDODk7cq4uUkutc1cStTw7BqVJ1GuDjbVFRQqeqLpNh3VQhYI", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a8b9537b-bca4-44b0-a408-4cbc4841f2b3", "ID_FS_UUID_ENC"=>"a8b9537b-bca4-44b0-a408-4cbc4841f2b3", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5
Jul 22 11:15:36 node-1 nailgun-agent: 9200", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.092290 #13061] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.092358 #13061] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.092432 #13061] DEBUG -- : Device dm-1 seems to be appropriate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.092462 #13061] DEBUG -- : Getting udev properties for device: dm-2
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.096088 #13061] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-m0fDLEBnVE81vFl0Z93iqWg0QKA1WXDfpHn0cg4hGNeqx0R3PG4AdUMiSqDNOi4U /dev/disk/by-uuid/000937ee-2511-45cd-9055-4b4196599041 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-m0fDLEBnVE81vFl0Z93iqWg0QKA1WXDfpHn0cg4hGNeqx0R3PG4AdUMiSqDNOi4U", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"000937ee-2511-45cd-9055-4b4196599041", "ID_FS_UUID_ENC"=>"000937ee-2511-45cd-9055-4b4196599041", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87509", "nomdmon
Jul 22 11:15:36 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.096146 #13061] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.096252 #13061] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.096285 #13061] DEBUG -- : Device dm-2 seems to be appropriate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.096319 #13061] DEBUG -- : Getting udev properties for device: dm-3
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.100372 #13061] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-5EUez5GyR9dlQkhrCSwtQlAc5WT53QXa4eLiPIs9pC9vneTeh4eOBlPVsJddwFOa /dev/disk/by-uuid/058e9f62-f367-40a1-8da2-0a719356b7df /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-5EUez5GyR9dlQkhrCSwtQlAc5WT53QXa4eLiPIs9pC9vneTeh4eOBlPVsJddwFOa", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"058e9f62-f367-40a1-8da2-0a719356b7df", "ID_FS_UUID_ENC"=>"058e9f62-f367-40a1-8da2-0a719356b7df", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97330", "nomdmonddf"=>"1",
Jul 22 11:15:36 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.100430 #13061] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.100499 #13061] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.100531 #13061] DEBUG -- : Device dm-3 seems to be appropriate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.100563 #13061] DEBUG -- : Getting udev properties for device: dm-4
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.104191 #13061] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-Z6qXwK1txqgk0ESiE605XBqy3HPxpz3bF38bNY2sh3GrckXr1I63Nfn9GpLY1v6j /dev/disk/by-uuid/1acf71ba-4e14-40e0-a826-17b931b26112 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-Z6qXwK1txqgk0ESiE605XBqy3HPxpz3bF38bNY2sh3GrckXr1I63Nfn9GpLY1v6j", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1acf71ba-4e14-40e0-a826-17b931b26112", "ID_FS_UUID_ENC"=>"1acf71ba-4e14-40e0-a826-17b931b26112", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13727", "nomdmonddf"=>"1", "nom
Jul 22 11:15:36 node-1 nailgun-agent: dmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.104248 #13061] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.104314 #13061] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.104344 #13061] DEBUG -- : Device dm-4 seems to be appropriate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.104375 #13061] DEBUG -- : Getting udev properties for device: dm-5
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.108022 #13061] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-Z6qXwK1txqgk0ESiE605XBqy3HPxpz3bbRMexSXJzEt1onhIzOYpx8SJ1clAOfy2 /dev/disk/by-uuid/3a95628a-17f7-4871-ae1c-4976b978ad20 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-Z6qXwK1txqgk0ESiE605XBqy3HPxpz3bbRMexSXJzEt1onhIzOYpx8SJ1clAOfy2", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"3a95628a-17f7-4871-ae1c-4976b978ad20", "ID_FS_UUID_ENC"=>"3a95628a-17f7-4871-ae1c-4976b978ad20", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14138", "nomdmonddf"=>"1", "nomdmonisw
Jul 22 11:15:36 node-1 nailgun-agent: "=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.108079 #13061] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.108145 #13061] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.108206 #13061] DEBUG -- : Device dm-5 seems to be appropriate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.108238 #13061] DEBUG -- : Getting udev properties for device: ram0
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.111631 #13061] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69349", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.111687 #13061] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.111777 #13061] DEBUG -- : Device ram0 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.111820 #13061] DEBUG -- : Getting udev properties for device: ram1
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.115849 #13061] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69359", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.115905 #13061] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.115978 #13061] DEBUG -- : Device ram1 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.116017 #13061] DEBUG -- : Getting udev properties for device: ram2
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.119656 #13061] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69444", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.119712 #13061] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.119856 #13061] DEBUG -- : Device ram2 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.119899 #13061] DEBUG -- : Getting udev properties for device: ram3
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.123115 #13061] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69456", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.123195 #13061] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.123277 #13061] DEBUG -- : Device ram3 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.123320 #13061] DEBUG -- : Getting udev properties for device: ram4
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.126551 #13061] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69477", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.126601 #13061] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.126674 #13061] DEBUG -- : Device ram4 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.126729 #13061] DEBUG -- : Getting udev properties for device: ram5
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.129908 #13061] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69492", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.129956 #13061] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.130022 #13061] DEBUG -- : Device ram5 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.130100 #13061] DEBUG -- : Getting udev properties for device: ram6
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.133187 #13061] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69504", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.133261 #13061] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.133377 #13061] DEBUG -- : Device ram6 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.133460 #13061] DEBUG -- : Getting udev properties for device: ram7
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.136633 #13061] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69518", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.136680 #13061] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.136764 #13061] DEBUG -- : Device ram7 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.136824 #13061] DEBUG -- : Getting udev properties for device: ram8
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.139661 #13061] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69532", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.139710 #13061] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.139806 #13061] DEBUG -- : Device ram8 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.139843 #13061] DEBUG -- : Getting udev properties for device: ram9
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.142717 #13061] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69543", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.142763 #13061] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.142849 #13061] DEBUG -- : Device ram9 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.142884 #13061] DEBUG -- : Getting udev properties for device: loop0
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.146018 #13061] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69252", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.146098 #13061] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.146167 #13061] DEBUG -- : Device loop0 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.146206 #13061] DEBUG -- : Getting udev properties for device: loop1
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.149435 #13061] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69267", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.149486 #13061] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.149550 #13061] DEBUG -- : Device loop1 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.149611 #13061] DEBUG -- : Getting udev properties for device: loop2
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.152662 #13061] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69280", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.152710 #13061] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.152841 #13061] DEBUG -- : Device loop2 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.152886 #13061] DEBUG -- : Getting udev properties for device: loop3
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.155948 #13061] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69290", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.156017 #13061] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.156088 #13061] DEBUG -- : Device loop3 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.156139 #13061] DEBUG -- : Getting udev properties for device: loop4
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.159248 #13061] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69302", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.159323 #13061] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.159436 #13061] DEBUG -- : Device loop4 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.159476 #13061] DEBUG -- : Getting udev properties for device: loop5
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.162569 #13061] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69312", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.162633 #13061] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.162700 #13061] DEBUG -- : Device loop5 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.162758 #13061] DEBUG -- : Getting udev properties for device: loop6
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.167603 #13061] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69322", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.167675 #13061] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.167785 #13061] DEBUG -- : Device loop6 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.167864 #13061] DEBUG -- : Getting udev properties for device: loop7
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.172659 #13061] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69336", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.172731 #13061] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.172863 #13061] DEBUG -- : Device loop7 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.172923 #13061] DEBUG -- : Getting udev properties for device: ram10
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.176430 #13061] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69371", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.176481 #13061] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.176551 #13061] DEBUG -- : Device ram10 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.176612 #13061] DEBUG -- : Getting udev properties for device: ram11
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.180997 #13061] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69381", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.181104 #13061] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.181204 #13061] DEBUG -- : Device ram11 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.181252 #13061] DEBUG -- : Getting udev properties for device: ram12
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.184905 #13061] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69391", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.184998 #13061] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.185140 #13061] DEBUG -- : Device ram12 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.185198 #13061] DEBUG -- : Getting udev properties for device: ram13
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.189137 #13061] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69402", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.189210 #13061] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.189305 #13061] DEBUG -- : Device ram13 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.189390 #13061] DEBUG -- : Getting udev properties for device: ram14
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.193342 #13061] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69416", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.193417 #13061] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.193548 #13061] DEBUG -- : Device ram14 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.193603 #13061] DEBUG -- : Getting udev properties for device: ram15
Jul 22 11:15:36 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.197952 #13061] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69431", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198028 #13061] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198134 #13061] DEBUG -- : Device ram15 removable parameter: "0"
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198250 #13061] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198323 #13061] DEBUG -- : Block device seems to be physical data storage: sda
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198415 #13061] DEBUG -- : Found block device: dm-0
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198512 #13061] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198550 #13061] DEBUG -- : Found block device: dm-1
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198583 #13061] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198642 #13061] DEBUG -- : Found block device: dm-2
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.198691 #13061] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207247 #13061] DEBUG -- : Found block device: dm-3
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207296 #13061] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207326 #13061] DEBUG -- : Found block device: dm-4
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207357 #13061] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207384 #13061] DEBUG -- : Found block device: dm-5
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207411 #13061] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207436 #13061] DEBUG -- : Found block device: ram0
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207462 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207488 #13061] DEBUG -- : Found block device: ram1
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207621 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207648 #13061] DEBUG -- : Found block device: ram2
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207677 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207702 #13061] DEBUG -- : Found block device: ram3
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207729 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207753 #13061] DEBUG -- : Found block device: ram4
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207779 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207803 #13061] DEBUG -- : Found block device: ram5
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207832 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207939 #13061] DEBUG -- : Found block device: ram6
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207968 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.207993 #13061] DEBUG -- : Found block device: ram7
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208021 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208045 #13061] DEBUG -- : Found block device: ram8
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208074 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208098 #13061] DEBUG -- : Found block device: ram9
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208126 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208151 #13061] DEBUG -- : Found block device: loop0
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208178 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208279 #13061] DEBUG -- : Found block device: loop1
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208307 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208331 #13061] DEBUG -- : Found block device: loop2
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208360 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208385 #13061] DEBUG -- : Found block device: loop3
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208413 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208438 #13061] DEBUG -- : Found block device: loop4
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208464 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208488 #13061] DEBUG -- : Found block device: loop5
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208589 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208616 #13061] DEBUG -- : Found block device: loop6
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208644 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208669 #13061] DEBUG -- : Found block device: loop7
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208697 #13061] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208721 #13061] DEBUG -- : Found block device: ram10
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208750 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208774 #13061] DEBUG -- : Found block device: ram11
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208810 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208905 #13061] DEBUG -- : Found block device: ram12
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208935 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208961 #13061] DEBUG -- : Found block device: ram13
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.208988 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.209013 #13061] DEBUG -- : Found block device: ram14
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.209039 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.209063 #13061] DEBUG -- : Found block device: ram15
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.209089 #13061] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.209166 #13061] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 22 11:15:36 node-1 nailgun-agent: D, [2016-07-22T11:15:36.396183 #13061] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 22 11:15:36 node-1 nailgun-agent: I, [2016-07-22T11:15:36.396561 #13061]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 22 11:16:00 node-1 puppet-user[14818]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 22 11:16:00 node-1 puppet-user[14818]: Finished catalog run in 34.56 seconds
Jul 22 11:16:01 node-1 CRON[17473]: (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 22 11:16:02 node-1 puppet-user[17445]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 22 11:16:02 node-1 puppet-user[17445]: Compiled catalog for node-1.domain.tld in environment production in 0.54 seconds
Jul 22 11:16:03 node-1 puppet-user[17445]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 22 11:16:03 node-1 puppet-user[17445]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 22 11:16:03 node-1 puppet-user[17445]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 22 11:16:03 node-1 puppet-user[17445]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 22 11:16:03 node-1 puppet-user[17445]: Finished catalog run in 0.09 seconds
Jul 22 11:16:05 node-1 puppet-user[17914]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 22 11:16:05 node-1 puppet-user[17914]: Compiled catalog for node-1.domain.tld in environment production in 0.81 seconds
Jul 22 11:16:06 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 22 11:16:06 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 22 11:16:06 node-1 crontab[18345]: (root) LIST (root)
Jul 22 11:16:06 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 22 11:16:06 node-1 crontab[18349]: (root) REPLACE (root)
Jul 22 11:16:08 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 22 11:16:09 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 22 11:16:10 node-1 puppet-user[17914]: (/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 22 11:16:10 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8380" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 11:16:10 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 22 11:16:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:16:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:24 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:24 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:24 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:17:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:07 node-1 ntpdate[2354]: no servers can be used, exiting
<27>Jul 22 11:18:08 node-1 ntpdate[2552]: no servers can be used, exiting
<27>Jul 22 11:18:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:43 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:43 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:43 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:43 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:18:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:19:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:19:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:19:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:19:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:19:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:08 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 11:20:08 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 11:20:14 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 11:20:14 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 11:20:20 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 11:20:25 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 11:20:25 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 11:20:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:45 node-1 multipathd: uevent trigger error
<129>Jul 22 11:20:47 node-1 haproxy[22850]: 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 22 11:20:48 node-1 haproxy[22854]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:20:48 node-1 haproxy[22854]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:20:48 node-1 haproxy[22854]: proxy mysqld has no server available!
<27>Jul 22 11:20:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:54 node-1 multipathd: uevent trigger error
<129>Jul 22 11:20:56 node-1 haproxy[25388]: 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 22 11:20:57 node-1 haproxy[25394]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:20:57 node-1 haproxy[25394]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:20:57 node-1 haproxy[25394]: proxy mysqld has no server available!
<129>Jul 22 11:20:57 node-1 haproxy[25394]: 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 22 11:20:58 node-1 haproxy[25394]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:20:58 node-1 haproxy[25394]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:20:58 node-1 haproxy[25394]: proxy object-storage has no server available!
<27>Jul 22 11:20:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:20:59 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:02 node-1 haproxy[26784]: 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 22 11:21:02 node-1 haproxy[26784]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:02 node-1 haproxy[26784]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:02 node-1 haproxy[26784]: proxy neutron has no server available!
<129>Jul 22 11:21:02 node-1 haproxy[26784]: 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 22 11:21:02 node-1 haproxy[26784]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:03 node-1 haproxy[26793]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:03 node-1 haproxy[26793]: proxy mysqld has no server available!
<129>Jul 22 11:21:03 node-1 haproxy[26793]: 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 22 11:21:03 node-1 haproxy[26793]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:03 node-1 haproxy[26793]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:03 node-1 haproxy[26793]: proxy object-storage has no server available!
<27>Jul 22 11:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:05 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:05 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:07 node-1 haproxy[28209]: 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 22 11:21:07 node-1 haproxy[28209]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:07 node-1 haproxy[28209]: Server keystone-1/node-3 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 22 11:21:07 node-1 haproxy[28209]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:07 node-1 haproxy[28209]: 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 22 11:21:08 node-1 haproxy[28213]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:08 node-1 haproxy[28213]: Server keystone-2/node-3 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 22 11:21:08 node-1 haproxy[28213]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:08 node-1 haproxy[28213]: 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 22 11:21:08 node-1 haproxy[28213]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:08 node-1 haproxy[28213]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:08 node-1 haproxy[28213]: proxy neutron has no server available!
<129>Jul 22 11:21:08 node-1 haproxy[28213]: 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 22 11:21:08 node-1 haproxy[28213]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:09 node-1 haproxy[28213]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:09 node-1 haproxy[28213]: proxy mysqld has no server available!
<129>Jul 22 11:21:09 node-1 haproxy[28213]: 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 22 11:21:09 node-1 haproxy[28213]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:09 node-1 haproxy[28213]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:09 node-1 haproxy[28213]: proxy object-storage has no server available!
<27>Jul 22 11:21:10 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:10 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:10 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:10 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:10 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:12 node-1 haproxy[29574]: 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 22 11:21:12 node-1 haproxy[29574]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:12 node-1 haproxy[29574]: Server keystone-1/node-3 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 22 11:21:12 node-1 haproxy[29574]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:13 node-1 haproxy[29578]: 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 22 11:21:13 node-1 haproxy[29578]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:13 node-1 haproxy[29578]: Server keystone-2/node-3 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 22 11:21:13 node-1 haproxy[29578]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:13 node-1 haproxy[29578]: 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 22 11:21:13 node-1 haproxy[29578]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:13 node-1 haproxy[29578]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:13 node-1 haproxy[29578]: proxy neutron has no server available!
<129>Jul 22 11:21:13 node-1 haproxy[29578]: 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 22 11:21:13 node-1 haproxy[29578]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:13 node-1 haproxy[29578]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:13 node-1 haproxy[29578]: proxy mysqld has no server available!
<129>Jul 22 11:21:14 node-1 haproxy[29578]: 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 22 11:21:14 node-1 haproxy[29578]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:14 node-1 haproxy[29578]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:14 node-1 haproxy[29578]: proxy object-storage has no server available!
<129>Jul 22 11:21:14 node-1 haproxy[29578]: 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 22 11:21:14 node-1 haproxy[29578]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:14 node-1 haproxy[29578]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:14 node-1 haproxy[29578]: proxy aodh has no server available!
<27>Jul 22 11:21:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:16 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:18 node-1 haproxy[30954]: 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 22 11:21:18 node-1 haproxy[30954]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:18 node-1 haproxy[30954]: Server keystone-1/node-3 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 22 11:21:18 node-1 haproxy[30954]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:18 node-1 haproxy[30954]: 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 22 11:21:18 node-1 haproxy[30954]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:18 node-1 haproxy[30954]: Server keystone-2/node-3 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 22 11:21:18 node-1 haproxy[30954]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:18 node-1 haproxy[30954]: 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 22 11:21:19 node-1 haproxy[30958]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:19 node-1 haproxy[30958]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:19 node-1 haproxy[30958]: proxy neutron has no server available!
<129>Jul 22 11:21:19 node-1 haproxy[30958]: 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 22 11:21:19 node-1 haproxy[30958]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:19 node-1 haproxy[30958]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:19 node-1 haproxy[30958]: proxy mysqld has no server available!
<129>Jul 22 11:21:19 node-1 haproxy[30958]: 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 22 11:21:19 node-1 haproxy[30958]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:19 node-1 haproxy[30958]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:19 node-1 haproxy[30958]: proxy object-storage has no server available!
<129>Jul 22 11:21:19 node-1 haproxy[30958]: 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 22 11:21:19 node-1 haproxy[30958]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:20 node-1 haproxy[30958]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:20 node-1 haproxy[30958]: proxy aodh has no server available!
<129>Jul 22 11:21:20 node-1 haproxy[30958]: 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 22 11:21:20 node-1 haproxy[30958]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:20 node-1 haproxy[30958]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:20 node-1 haproxy[30958]: proxy ceilometer has no server available!
<27>Jul 22 11:21:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:21 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:23 node-1 haproxy[32299]: 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 22 11:21:24 node-1 haproxy[32303]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:24 node-1 haproxy[32303]: Server keystone-1/node-3 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 22 11:21:24 node-1 haproxy[32303]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:24 node-1 haproxy[32303]: 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 22 11:21:24 node-1 haproxy[32303]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:24 node-1 haproxy[32303]: Server keystone-2/node-3 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 22 11:21:24 node-1 haproxy[32303]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:24 node-1 haproxy[32303]: 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 22 11:21:24 node-1 haproxy[32303]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:24 node-1 haproxy[32303]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:24 node-1 haproxy[32303]: proxy neutron has no server available!
<129>Jul 22 11:21:24 node-1 haproxy[32303]: 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 22 11:21:24 node-1 haproxy[32303]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:24 node-1 haproxy[32303]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:24 node-1 haproxy[32303]: proxy mysqld has no server available!
<129>Jul 22 11:21:25 node-1 haproxy[32303]: 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 22 11:21:25 node-1 haproxy[32303]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:25 node-1 haproxy[32303]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:25 node-1 haproxy[32303]: proxy object-storage has no server available!
<129>Jul 22 11:21:25 node-1 haproxy[32303]: 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 22 11:21:25 node-1 haproxy[32303]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:25 node-1 haproxy[32303]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:25 node-1 haproxy[32303]: proxy aodh has no server available!
<129>Jul 22 11:21:25 node-1 haproxy[32303]: 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 22 11:21:25 node-1 haproxy[32303]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:25 node-1 haproxy[32303]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:25 node-1 haproxy[32303]: proxy ceilometer has no server available!
<27>Jul 22 11:21:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:27 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:29 node-1 haproxy[1356]: 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 22 11:21:29 node-1 haproxy[1356]: 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 22 11:21:29 node-1 haproxy[1356]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:29 node-1 haproxy[1356]: Server keystone-1/node-3 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 22 11:21:29 node-1 haproxy[1356]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:29 node-1 haproxy[1356]: 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 22 11:21:29 node-1 haproxy[1356]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:29 node-1 haproxy[1356]: Server keystone-2/node-3 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 22 11:21:29 node-1 haproxy[1356]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:30 node-1 haproxy[1365]: 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 22 11:21:30 node-1 haproxy[1365]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:30 node-1 haproxy[1365]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:30 node-1 haproxy[1365]: proxy neutron has no server available!
<129>Jul 22 11:21:30 node-1 haproxy[1365]: 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 22 11:21:30 node-1 haproxy[1365]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:30 node-1 haproxy[1365]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:30 node-1 haproxy[1365]: proxy mysqld has no server available!
<129>Jul 22 11:21:30 node-1 haproxy[1365]: 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 22 11:21:30 node-1 haproxy[1365]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:30 node-1 haproxy[1365]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:30 node-1 haproxy[1365]: proxy object-storage has no server available!
<129>Jul 22 11:21:30 node-1 haproxy[1365]: 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 22 11:21:30 node-1 haproxy[1365]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:30 node-1 haproxy[1365]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:30 node-1 haproxy[1365]: proxy aodh has no server available!
<129>Jul 22 11:21:31 node-1 haproxy[1365]: 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 22 11:21:31 node-1 haproxy[1365]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:31 node-1 haproxy[1365]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:31 node-1 haproxy[1365]: proxy ceilometer has no server available!
<27>Jul 22 11:21:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:32 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:34 node-1 haproxy[2749]: 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 22 11:21:35 node-1 haproxy[2754]: 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 22 11:21:35 node-1 haproxy[2754]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:35 node-1 haproxy[2754]: Server keystone-1/node-3 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 22 11:21:35 node-1 haproxy[2754]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:35 node-1 haproxy[2754]: 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 22 11:21:35 node-1 haproxy[2754]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:35 node-1 haproxy[2754]: Server keystone-2/node-3 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 22 11:21:35 node-1 haproxy[2754]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:35 node-1 haproxy[2754]: 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 22 11:21:35 node-1 haproxy[2754]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:35 node-1 haproxy[2754]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:35 node-1 haproxy[2754]: proxy glance-api has no server available!
<129>Jul 22 11:21:35 node-1 haproxy[2754]: 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 22 11:21:35 node-1 haproxy[2754]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:35 node-1 haproxy[2754]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:35 node-1 haproxy[2754]: proxy glance-glare has no server available!
<129>Jul 22 11:21:35 node-1 haproxy[2754]: 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 22 11:21:35 node-1 haproxy[2754]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:35 node-1 haproxy[2754]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:35 node-1 haproxy[2754]: proxy neutron has no server available!
<129>Jul 22 11:21:36 node-1 haproxy[2754]: 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 22 11:21:36 node-1 haproxy[2754]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:36 node-1 haproxy[2754]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:36 node-1 haproxy[2754]: proxy glance-registry has no server available!
<129>Jul 22 11:21:36 node-1 haproxy[2754]: 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 22 11:21:36 node-1 haproxy[2754]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:36 node-1 haproxy[2754]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:36 node-1 haproxy[2754]: proxy mysqld has no server available!
<129>Jul 22 11:21:36 node-1 haproxy[2754]: 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 22 11:21:36 node-1 haproxy[2754]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:36 node-1 haproxy[2754]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:36 node-1 haproxy[2754]: proxy object-storage has no server available!
<129>Jul 22 11:21:36 node-1 haproxy[2754]: 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 22 11:21:36 node-1 haproxy[2754]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:36 node-1 haproxy[2754]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:36 node-1 haproxy[2754]: proxy aodh has no server available!
<129>Jul 22 11:21:36 node-1 haproxy[2754]: 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 22 11:21:36 node-1 haproxy[2754]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:36 node-1 haproxy[2754]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:36 node-1 haproxy[2754]: proxy ceilometer has no server available!
<27>Jul 22 11:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:38 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:40 node-1 haproxy[4321]: 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 22 11:21:41 node-1 haproxy[4325]: 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 22 11:21:41 node-1 haproxy[4325]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:41 node-1 haproxy[4325]: Server keystone-1/node-3 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 22 11:21:41 node-1 haproxy[4325]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:41 node-1 haproxy[4325]: 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 22 11:21:41 node-1 haproxy[4325]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:41 node-1 haproxy[4325]: Server keystone-2/node-3 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 22 11:21:41 node-1 haproxy[4325]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:41 node-1 haproxy[4325]: 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 22 11:21:41 node-1 haproxy[4325]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:41 node-1 haproxy[4325]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:41 node-1 haproxy[4325]: proxy nova-api has no server available!
<129>Jul 22 11:21:41 node-1 haproxy[4325]: 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 22 11:21:41 node-1 haproxy[4325]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:41 node-1 haproxy[4325]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:41 node-1 haproxy[4325]: proxy nova-metadata-api has no server available!
<129>Jul 22 11:21:41 node-1 haproxy[4325]: 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 22 11:21:41 node-1 haproxy[4325]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:41 node-1 haproxy[4325]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:41 node-1 haproxy[4325]: proxy glance-api has no server available!
<129>Jul 22 11:21:41 node-1 haproxy[4325]: 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 22 11:21:41 node-1 haproxy[4325]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:41 node-1 haproxy[4325]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:41 node-1 haproxy[4325]: proxy glance-glare has no server available!
<129>Jul 22 11:21:41 node-1 haproxy[4325]: 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 22 11:21:41 node-1 haproxy[4325]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:42 node-1 haproxy[4325]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:42 node-1 haproxy[4325]: proxy neutron has no server available!
<129>Jul 22 11:21:42 node-1 haproxy[4325]: 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 22 11:21:42 node-1 haproxy[4325]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:42 node-1 haproxy[4325]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:42 node-1 haproxy[4325]: proxy glance-registry has no server available!
<129>Jul 22 11:21:42 node-1 haproxy[4325]: 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 22 11:21:42 node-1 haproxy[4325]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:42 node-1 haproxy[4325]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:42 node-1 haproxy[4325]: proxy mysqld has no server available!
<129>Jul 22 11:21:42 node-1 haproxy[4325]: 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 22 11:21:42 node-1 haproxy[4325]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:42 node-1 haproxy[4325]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:42 node-1 haproxy[4325]: proxy object-storage has no server available!
<129>Jul 22 11:21:42 node-1 haproxy[4325]: 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 22 11:21:42 node-1 haproxy[4325]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:42 node-1 haproxy[4325]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:42 node-1 haproxy[4325]: proxy aodh has no server available!
<129>Jul 22 11:21:42 node-1 haproxy[4325]: 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 22 11:21:42 node-1 haproxy[4325]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:42 node-1 haproxy[4325]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:42 node-1 haproxy[4325]: proxy ceilometer has no server available!
<129>Jul 22 11:21:42 node-1 haproxy[4325]: 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 22 11:21:42 node-1 haproxy[4325]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:42 node-1 haproxy[4325]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:42 node-1 haproxy[4325]: proxy nova-novncproxy has no server available!
<27>Jul 22 11:21:44 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:44 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:44 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:44 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:44 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:44 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:46 node-1 haproxy[5660]: 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 22 11:21:46 node-1 haproxy[5660]: 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 22 11:21:46 node-1 haproxy[5660]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:46 node-1 haproxy[5660]: Server keystone-1/node-3 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 22 11:21:46 node-1 haproxy[5660]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:46 node-1 haproxy[5660]: 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 22 11:21:46 node-1 haproxy[5660]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:46 node-1 haproxy[5660]: Server keystone-2/node-3 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 22 11:21:46 node-1 haproxy[5660]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:46 node-1 haproxy[5660]: 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 22 11:21:46 node-1 haproxy[5660]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:46 node-1 haproxy[5660]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:46 node-1 haproxy[5660]: proxy nova-api has no server available!
<129>Jul 22 11:21:46 node-1 haproxy[5660]: 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 22 11:21:46 node-1 haproxy[5660]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:46 node-1 haproxy[5660]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:46 node-1 haproxy[5660]: proxy nova-metadata-api has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:47 node-1 haproxy[5664]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:47 node-1 haproxy[5664]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:47 node-1 haproxy[5664]: proxy cinder-api has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:47 node-1 haproxy[5664]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:47 node-1 haproxy[5664]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:47 node-1 haproxy[5664]: proxy glance-api has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:47 node-1 haproxy[5664]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:47 node-1 haproxy[5664]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:47 node-1 haproxy[5664]: proxy glance-glare has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:47 node-1 haproxy[5664]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:47 node-1 haproxy[5664]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:47 node-1 haproxy[5664]: proxy neutron has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:47 node-1 haproxy[5664]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:47 node-1 haproxy[5664]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:47 node-1 haproxy[5664]: proxy glance-registry has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:47 node-1 haproxy[5664]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:47 node-1 haproxy[5664]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:47 node-1 haproxy[5664]: proxy mysqld has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:47 node-1 haproxy[5664]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:47 node-1 haproxy[5664]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:47 node-1 haproxy[5664]: proxy object-storage has no server available!
<129>Jul 22 11:21:47 node-1 haproxy[5664]: 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 22 11:21:48 node-1 haproxy[5664]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:48 node-1 haproxy[5664]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:48 node-1 haproxy[5664]: proxy aodh has no server available!
<129>Jul 22 11:21:48 node-1 haproxy[5664]: 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 22 11:21:48 node-1 haproxy[5664]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:48 node-1 haproxy[5664]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:48 node-1 haproxy[5664]: proxy ceilometer has no server available!
<129>Jul 22 11:21:48 node-1 haproxy[5664]: 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 22 11:21:48 node-1 haproxy[5664]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:48 node-1 haproxy[5664]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:48 node-1 haproxy[5664]: proxy nova-novncproxy has no server available!
<27>Jul 22 11:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:49 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:49 node-1 multipathd: uevent trigger error
<129>Jul 22 11:21:52 node-1 haproxy[7029]: 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 22 11:21:52 node-1 haproxy[7029]: 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 22 11:21:52 node-1 haproxy[7029]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:52 node-1 haproxy[7029]: Server keystone-1/node-3 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 22 11:21:52 node-1 haproxy[7029]: proxy keystone-1 has no server available!
<129>Jul 22 11:21:52 node-1 haproxy[7029]: 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 22 11:21:52 node-1 haproxy[7029]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:52 node-1 haproxy[7029]: Server keystone-2/node-3 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 22 11:21:52 node-1 haproxy[7029]: proxy keystone-2 has no server available!
<129>Jul 22 11:21:52 node-1 haproxy[7029]: 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 22 11:21:52 node-1 haproxy[7029]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:52 node-1 haproxy[7029]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:52 node-1 haproxy[7029]: proxy nova-api has no server available!
<129>Jul 22 11:21:52 node-1 haproxy[7029]: 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 22 11:21:52 node-1 haproxy[7029]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:52 node-1 haproxy[7029]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:52 node-1 haproxy[7029]: proxy nova-metadata-api has no server available!
<129>Jul 22 11:21:52 node-1 haproxy[7029]: 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 22 11:21:52 node-1 haproxy[7029]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:52 node-1 haproxy[7029]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:52 node-1 haproxy[7029]: proxy cinder-api has no server available!
<129>Jul 22 11:21:52 node-1 haproxy[7029]: 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 22 11:21:53 node-1 haproxy[7033]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy glance-api has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy glance-glare has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy neutron has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy glance-registry has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy mysqld has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy object-storage has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy aodh has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy ceilometer has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:53 node-1 haproxy[7033]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:53 node-1 haproxy[7033]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:53 node-1 haproxy[7033]: proxy heat-api has no server available!
<129>Jul 22 11:21:53 node-1 haproxy[7033]: 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 22 11:21:54 node-1 haproxy[7033]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:54 node-1 haproxy[7033]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:54 node-1 haproxy[7033]: proxy heat-api-cfn has no server available!
<129>Jul 22 11:21:54 node-1 haproxy[7033]: 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 22 11:21:54 node-1 haproxy[7033]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:54 node-1 haproxy[7033]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:54 node-1 haproxy[7033]: proxy heat-api-cloudwatch has no server available!
<129>Jul 22 11:21:54 node-1 haproxy[7033]: 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 22 11:21:54 node-1 haproxy[7033]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 11:21:54 node-1 haproxy[7033]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 11:21:54 node-1 haproxy[7033]: proxy nova-novncproxy has no server available!
<27>Jul 22 11:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:55 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:21:59 node-1 multipathd: uevent trigger error
<27>Jul 22 11:22:08 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 22 11:22:33 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 22 11:22:35 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 22 11:22:57 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:23:04 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 11:23:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:23:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:23:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:23:27 node-1 multipathd: uevent trigger error
<27>Jul 22 11:23:28 node-1 multipathd: uevent trigger error
<27>Jul 22 11:25:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:25:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:25:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:25:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:25:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:26:00 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:00 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:00 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:00 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:21 node-1 multipathd: uevent trigger error
<43>Jul 22 11:26:21 node-1 apache2_error [Fri Jul 22 11:26:12.835358 2016] [mpm_event:notice] [pid 16398:tid 140473730320256] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 11:26:21 node-1 apache2_error [Fri Jul 22 11:26:12.835494 2016] [core:notice] [pid 16398:tid 140473730320256] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 22 11:26:21 node-1 apache2_error [Fri Jul 22 11:26:15.906710 2016] [mpm_event:notice] [pid 16398:tid 140473730320256] AH00491: caught SIGTERM, shutting down
<43>Jul 22 11:26:21 node-1 apache2_error [Fri Jul 22 11:26:17.016877 2016] [mpm_worker:notice] [pid 16767:tid 140186337752960] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 11:26:21 node-1 apache2_error [Fri Jul 22 11:26:17.016939 2016] [core:notice] [pid 16767:tid 140186337752960] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 11:26:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:29 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:29 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:29 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:29 node-1 multipathd: uevent trigger error
<27>Jul 22 11:26:29 node-1 multipathd: uevent trigger error
<43>Jul 22 11:27:41 node-1 apache2_error [Fri Jul 22 11:27:38.040981 2016] [mpm_worker:notice] [pid 16767:tid 140186337752960] AH00295: caught SIGTERM, shutting down
<43>Jul 22 11:27:41 node-1 apache2_error [Fri Jul 22 11:27:38.798567 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 11:27:41 node-1 apache2_error [Fri Jul 22 11:27:38.798595 2016] [core:notice] [pid 31034:tid 139907050579840] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 22 11:28:32 node-1 apache2_error [Fri Jul 22 11:28:22.799583 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 11:28:32 node-1 apache2_error [Fri Jul 22 11:28:22.996956 2016] [mpm_worker:warn] [pid 31034:tid 139907050579840] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 11:28:32 node-1 apache2_error [Fri Jul 22 11:28:23.001604 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 11:28:32 node-1 apache2_error [Fri Jul 22 11:28:23.001635 2016] [core:notice] [pid 31034:tid 139907050579840] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 11:28:59 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:29:08 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:08 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:08 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:08 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:13 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:13 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:13 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:13 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:17 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:17 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:17 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:17 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:37 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:58 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:58 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:58 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:58 node-1 multipathd: uevent trigger error
<27>Jul 22 11:29:58 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:03 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:03 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:03 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:03 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:03 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:30:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 22 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 22 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 22 11:31:19 node-1 multipathd: uevent trigger error
<27>Jul 22 11:32:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:32:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:32:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:32:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:32:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:32:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:34 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:34 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:34 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:34 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:34 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:33:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:34:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:34:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:34:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:34:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:34:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:35:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:36:30 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:50 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:06 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:06 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:06 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:06 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:06 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:37:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:38:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:38:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:38:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:38:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:38:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:38:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:09 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 22 11:39:09 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 22 11:39:09 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 22 11:39:10 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 22 11:39:10 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 22 11:39:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:39 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:58 node-1 multipathd: uevent trigger error
<27>Jul 22 11:39:58 node-1 multipathd: uevent trigger error
<27>Jul 22 11:41:06 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:42:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:21 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:42:56 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:30 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:30 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:30 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:30 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:30 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:42 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:42 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:42 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:42 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:42 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:49 node-1 multipathd: uevent trigger error
<27>Jul 22 11:43:49 node-1 multipathd: uevent trigger error
<27>Jul 22 11:44:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:44:37 node-1 multipathd: uevent trigger error
<27>Jul 22 11:44:37 node-1 multipathd: uevent trigger error
<27>Jul 22 11:44:37 node-1 multipathd: uevent trigger error
<27>Jul 22 11:44:37 node-1 multipathd: uevent trigger error
<27>Jul 22 11:44:37 node-1 multipathd: uevent trigger error
<27>Jul 22 11:45:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:45:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:45:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:45:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:45:48 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:07 node-1 multipathd: uevent trigger error
<11>Jul 22 11:46:21 node-1 liberasurecode[24869]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:21 node-1 liberasurecode[24869]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:21 node-1 liberasurecode[24869]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:21 node-1 liberasurecode[24869]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:21 node-1 liberasurecode[24893]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:21 node-1 liberasurecode[24893]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:21 node-1 liberasurecode[24893]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:21 node-1 liberasurecode[24893]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:23 node-1 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:23 node-1 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:23 node-1 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:23 node-1 liberasurecode[25334]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25929]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25929]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25929]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25929]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25967]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[25967]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[26006]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[26006]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[26006]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:28 node-1 liberasurecode[26006]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26089]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26089]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26089]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26089]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26106]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26106]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26106]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26106]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26121]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26133]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:29 node-1 liberasurecode[26133]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:45 node-1 liberasurecode[28616]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:45 node-1 liberasurecode[28616]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:45 node-1 liberasurecode[28616]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:46:45 node-1 liberasurecode[28616]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 11:46:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:46:54 node-1 multipathd: uevent trigger error
<27>Jul 22 11:47:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 22 11:47:43 node-1 apache2_error [Fri Jul 22 11:47:41.493348 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 11:47:43 node-1 apache2_error [Fri Jul 22 11:47:41.874377 2016] [mpm_worker:warn] [pid 31034:tid 139907050579840] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 11:47:43 node-1 apache2_error [Fri Jul 22 11:47:41.878770 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 11:47:43 node-1 apache2_error [Fri Jul 22 11:47:41.878801 2016] [core:notice] [pid 31034:tid 139907050579840] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 11:48:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:48:22 node-1 multipathd: uevent trigger error
<27>Jul 22 11:48:23 node-1 multipathd: uevent trigger error
<27>Jul 22 11:48:23 node-1 multipathd: uevent trigger error
<43>Jul 22 11:48:23 node-1 apache2_error [Fri Jul 22 11:48:18.899743 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 11:48:23 node-1 apache2_error [Fri Jul 22 11:48:19.093156 2016] [mpm_worker:warn] [pid 31034:tid 139907050579840] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 11:48:23 node-1 apache2_error [Fri Jul 22 11:48:19.104100 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 11:48:23 node-1 apache2_error [Fri Jul 22 11:48:19.104143 2016] [core:notice] [pid 31034:tid 139907050579840] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 11:48:35 node-1 multipathd: uevent trigger error
<27>Jul 22 11:48:35 node-1 multipathd: uevent trigger error
<27>Jul 22 11:48:35 node-1 multipathd: uevent trigger error
<27>Jul 22 11:48:35 node-1 multipathd: uevent trigger error
<27>Jul 22 11:48:35 node-1 multipathd: uevent trigger error
<43>Jul 22 11:49:13 node-1 apache2_error [Fri Jul 22 11:49:09.669490 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 11:49:13 node-1 apache2_error [Fri Jul 22 11:49:10.052340 2016] [mpm_worker:warn] [pid 31034:tid 139907050579840] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 11:49:13 node-1 apache2_error [Fri Jul 22 11:49:10.061168 2016] [mpm_worker:notice] [pid 31034:tid 139907050579840] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 11:49:13 node-1 apache2_error [Fri Jul 22 11:49:10.061193 2016] [core:notice] [pid 31034:tid 139907050579840] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 11:49:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:14 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:20 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:20 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:20 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:20 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:20 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:25 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:31 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:47 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:47 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:47 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:47 node-1 multipathd: uevent trigger error
<27>Jul 22 11:49:47 node-1 multipathd: uevent trigger error
<11>Jul 22 11:50:02 node-1 liberasurecode[3704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:50:02 node-1 liberasurecode[3704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:50:02 node-1 liberasurecode[3704]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:50:02 node-1 liberasurecode[3704]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 11:50:08 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 11:50:15 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:15 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:15 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:15 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:15 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:22 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 22 11:50:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:36 node-1 multipathd: uevent trigger error
<27>Jul 22 11:50:37 node-1 multipathd: uevent trigger error
<27>Jul 22 11:51:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 11:53:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:32 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:40 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:40 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:40 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:40 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:40 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:51 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:51 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:51 node-1 multipathd: uevent trigger error
<27>Jul 22 11:53:51 node-1 multipathd: uevent trigger error
<129>Jul 22 11:53:51 node-1 haproxy[13010]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 11:53:51 node-1 multipathd: uevent trigger error
<129>Jul 22 11:53:51 node-1 haproxy[13010]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 11:54:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:12 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:26 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:33 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:38 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:51 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:51 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:51 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:51 node-1 multipathd: uevent trigger error
<27>Jul 22 11:54:51 node-1 multipathd: uevent trigger error
<11>Jul 22 11:55:01 node-1 liberasurecode[4079]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:55:01 node-1 liberasurecode[4079]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:55:01 node-1 liberasurecode[4079]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 11:55:01 node-1 liberasurecode[4079]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 11:55:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:02 node-1 multipathd: uevent trigger error
<129>Jul 22 11:55:12 node-1 haproxy[13010]: 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.
<27>Jul 22 11:55:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:53 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:55:57 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:02 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:07 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:11 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:16 node-1 multipathd: uevent trigger error
<27>Jul 22 11:56:16 node-1 multipathd: uevent trigger error
