Sep 23 07:13:43 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] start
Sep 23 07:13:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 23 07:13:43 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 23 07:13:43 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 23 07:13:43 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 23 07:13:43 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 23 07:13:43 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 23 07:13:43 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 23 07:13:43 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4d408674-bf7a-4fbd-9662-b3741f23b1ae nomdmonddf nomdmonisw
Sep 23 07:13:43 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 23 07:13:43 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 23 07:13:43 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 23 07:13:43 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 23 07:13:43 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 23 07:13:43 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 23 07:13:43 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 23 07:13:43 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
Sep 23 07:13:43 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 23 07:13:43 node-1 kernel: [    0.000000] No AGP bridge found
Sep 23 07:13:43 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 23 07:13:43 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 23 07:13:43 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 23 07:13:43 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 23 07:13:43 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 23 07:13:43 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 23 07:13:43 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 23 07:13:43 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 23 07:13:43 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 23 07:13:43 node-1 kernel: [    0.000000]   2 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000]   3 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000]   4 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000]   5 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000]   6 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000]   7 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000]   8 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000]   9 disabled
Sep 23 07:13:43 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 23 07:13:43 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 23 07:13:43 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 23 07:13:43 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 23 07:13:43 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 23 07:13:43 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 23 07:13:43 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 23 07:13:43 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 23 07:13:43 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 23 07:13:43 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 23 07:13:43 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 23 07:13:43 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 23 07:13:43 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 23 07:13:43 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 23 07:13:43 node-1 kernel: [    0.000000] Zone ranges:
Sep 23 07:13:43 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 23 07:13:43 node-1 kernel: [    0.000000] Early memory node ranges
Sep 23 07:13:43 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 23 07:13:43 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 23 07:13:43 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 23 07:13:43 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 23 07:13:43 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 23 07:13:43 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 23 07:13:43 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 23 07:13:43 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 23 07:13:43 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 23 07:13:43 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 23 07:13:43 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 23 07:13:43 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 23 07:13:43 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 23 07:13:43 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 23 07:13:43 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 23 07:13:43 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 23 07:13:43 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 23 07:13:43 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 23 07:13:43 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 23 07:13:43 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 23 07:13:43 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 23 07:13:43 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 23 07:13:43 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 23 07:13:43 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 
Sep 23 07:13:43 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 23 07:13:43 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 23 07:13:43 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=4d408674-bf7a-4fbd-9662-b3741f23b1ae nomdmonddf nomdmonisw
Sep 23 07:13:43 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 23 07:13:43 node-1 kernel: [    0.000000] Checking aperture...
Sep 23 07:13:43 node-1 kernel: [    0.000000] No AGP bridge found
Sep 23 07:13:43 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 23 07:13:43 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 23 07:13:43 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 23 07:13:43 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 23 07:13:43 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 23 07:13:43 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 23 07:13:43 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 23 07:13:43 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 23 07:13:43 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 23 07:13:43 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 23 07:13:43 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 23 07:13:43 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 23 07:13:43 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 23 07:13:43 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 23 07:13:43 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 23 07:13:43 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 23 07:13:43 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 23 07:13:43 node-1 kernel: [    0.004000] tsc: Detected 3492.174 MHz processor
Sep 23 07:13:43 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.34 BogoMIPS (lpj=13968696)
Sep 23 07:13:43 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 23 07:13:43 node-1 kernel: [    0.000048] Security Framework initialized
Sep 23 07:13:43 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Sep 23 07:13:43 node-1 kernel: [    0.000067] Yama: becoming mindful.
Sep 23 07:13:43 node-1 kernel: [    0.001457] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.006374] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.008306] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.008335] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.008627] Initializing cgroup subsys memory
Sep 23 07:13:43 node-1 kernel: [    0.008635] Initializing cgroup subsys devices
Sep 23 07:13:43 node-1 kernel: [    0.008637] Initializing cgroup subsys freezer
Sep 23 07:13:43 node-1 kernel: [    0.008639] Initializing cgroup subsys blkio
Sep 23 07:13:43 node-1 kernel: [    0.008640] Initializing cgroup subsys perf_event
Sep 23 07:13:43 node-1 kernel: [    0.008642] Initializing cgroup subsys hugetlb
Sep 23 07:13:43 node-1 kernel: [    0.008662] CPU: Physical Processor ID: 0
Sep 23 07:13:43 node-1 kernel: [    0.008663] CPU: Processor Core ID: 0
Sep 23 07:13:43 node-1 kernel: [    0.008667] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 23 07:13:43 node-1 kernel: [    0.008667] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 23 07:13:43 node-1 kernel: [    0.009361] mce: CPU supports 22 MCE banks
Sep 23 07:13:43 node-1 kernel: [    0.009388] CPU0: Thermal monitoring enabled (TM1)
Sep 23 07:13:43 node-1 kernel: [    0.009409] process: using mwait in idle threads
Sep 23 07:13:43 node-1 kernel: [    0.009412] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 23 07:13:43 node-1 kernel: [    0.009412] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 23 07:13:43 node-1 kernel: [    0.009412] tlb_flushall_shift: 6
Sep 23 07:13:43 node-1 kernel: [    0.009501] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 23 07:13:43 node-1 kernel: [    0.010226] ACPI: Core revision 20131115
Sep 23 07:13:43 node-1 kernel: [    0.022914] ACPI: All ACPI Tables successfully acquired
Sep 23 07:13:43 node-1 kernel: [    0.023075] ftrace: allocating 28617 entries in 112 pages
Sep 23 07:13:43 node-1 kernel: [    0.032051] dmar: Host address width 46
Sep 23 07:13:43 node-1 kernel: [    0.032053] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 23 07:13:43 node-1 kernel: [    0.032059] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 23 07:13:43 node-1 kernel: [    0.032061] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 23 07:13:43 node-1 kernel: [    0.032065] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 23 07:13:43 node-1 kernel: [    0.032067] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 23 07:13:43 node-1 kernel: [    0.032068] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 23 07:13:43 node-1 kernel: [    0.032069] dmar: ATSR flags: 0x0
Sep 23 07:13:43 node-1 kernel: [    0.032070] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 23 07:13:43 node-1 kernel: [    0.032071] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 23 07:13:43 node-1 kernel: [    0.032186] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 23 07:13:43 node-1 kernel: [    0.032187] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 23 07:13:43 node-1 kernel: [    0.032188] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 23 07:13:43 node-1 kernel: [    0.032190] HPET id 0 under DRHD base 0xc7ffc000
Sep 23 07:13:43 node-1 kernel: [    0.032191] Your BIOS is broken and requested that x2apic be disabled.
Sep 23 07:13:43 node-1 kernel: [    0.032191] This will slightly decrease performance.
Sep 23 07:13:43 node-1 kernel: [    0.032191] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 23 07:13:43 node-1 kernel: [    0.032623] Enabled IRQ remapping in xapic mode
Sep 23 07:13:43 node-1 kernel: [    0.032624] x2apic not enabled, IRQ remapping is in xapic mode
Sep 23 07:13:43 node-1 kernel: [    0.032628] Switched APIC routing to physical flat.
Sep 23 07:13:43 node-1 kernel: [    0.033254] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 23 07:13:43 node-1 kernel: [    0.072907] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 23 07:13:43 node-1 kernel: [    0.072912] TSC deadline timer enabled
Sep 23 07:13:43 node-1 kernel: [    0.072930] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 23 07:13:43 node-1 kernel: [    0.072936] ... version:                3
Sep 23 07:13:43 node-1 kernel: [    0.072937] ... bit width:              48
Sep 23 07:13:43 node-1 kernel: [    0.072938] ... generic registers:      4
Sep 23 07:13:43 node-1 kernel: [    0.072939] ... value mask:             0000ffffffffffff
Sep 23 07:13:43 node-1 kernel: [    0.072940] ... max period:             0000ffffffffffff
Sep 23 07:13:43 node-1 kernel: [    0.072941] ... fixed-purpose events:   3
Sep 23 07:13:43 node-1 kernel: [    0.072942] ... event mask:             000000070000000f
Sep 23 07:13:43 node-1 kernel: [    0.074335] x86: Booting SMP configuration:
Sep 23 07:13:43 node-1 kernel: [    0.088444] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 23 07:13:43 node-1 kernel: [    0.074337] .... node  #0, CPUs:        #1  #2  #3
Sep 23 07:13:43 node-1 kernel: [    0.116358] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 23 07:13:43 node-1 kernel: [    0.270505] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 23 07:13:43 node-1 kernel: [    0.326132] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 23 07:13:43 node-1 kernel: [    0.382988] x86: Booted up 2 nodes, 16 CPUs
Sep 23 07:13:43 node-1 kernel: [    0.382991] smpboot: Total of 16 processors activated (111762.14 BogoMIPS)
Sep 23 07:13:43 node-1 kernel: [    0.407057] devtmpfs: initialized
Sep 23 07:13:43 node-1 kernel: [    0.410183] EVM: security.selinux
Sep 23 07:13:43 node-1 kernel: [    0.410185] EVM: security.SMACK64
Sep 23 07:13:43 node-1 kernel: [    0.410185] EVM: security.ima
Sep 23 07:13:43 node-1 kernel: [    0.410186] EVM: security.capability
Sep 23 07:13:43 node-1 kernel: [    0.410235] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.410922] pinctrl core: initialized pinctrl subsystem
Sep 23 07:13:43 node-1 kernel: [    0.410988] regulator-dummy: no parameters
Sep 23 07:13:43 node-1 kernel: [    0.411020] RTC time:  7:13:08, date: 09/23/16
Sep 23 07:13:43 node-1 kernel: [    0.411055] NET: Registered protocol family 16
Sep 23 07:13:43 node-1 kernel: [    0.411140] cpuidle: using governor ladder
Sep 23 07:13:43 node-1 kernel: [    0.411142] cpuidle: using governor menu
Sep 23 07:13:43 node-1 kernel: [    0.411176] ACPI: bus type PCI registered
Sep 23 07:13:43 node-1 kernel: [    0.411178] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 23 07:13:43 node-1 kernel: [    0.411224] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 23 07:13:43 node-1 kernel: [    0.411226] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 23 07:13:43 node-1 kernel: [    0.424959] PCI: Using configuration type 1 for base access
Sep 23 07:13:43 node-1 kernel: [    0.425957] bio: create slab <bio-0> at 0
Sep 23 07:13:43 node-1 kernel: [    0.426234] ACPI: Added _OSI(Module Device)
Sep 23 07:13:43 node-1 kernel: [    0.426236] ACPI: Added _OSI(Processor Device)
Sep 23 07:13:43 node-1 kernel: [    0.426237] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 23 07:13:43 node-1 kernel: [    0.426238] ACPI: Added _OSI(Processor Aggregator Device)
Sep 23 07:13:43 node-1 kernel: [    0.438840] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 23 07:13:43 node-1 kernel: [    0.449375] ACPI: Interpreter enabled
Sep 23 07:13:43 node-1 kernel: [    0.449381] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 23 07:13:43 node-1 kernel: [    0.449385] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 23 07:13:43 node-1 kernel: [    0.449387] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 23 07:13:43 node-1 kernel: [    0.449394] ACPI: (supports S0 S4 S5)
Sep 23 07:13:43 node-1 kernel: [    0.449395] ACPI: Using IOAPIC for interrupt routing
Sep 23 07:13:43 node-1 kernel: [    0.449441] HEST: Table parsing has been initialized.
Sep 23 07:13:43 node-1 kernel: [    0.449444] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 23 07:13:43 node-1 kernel: [    0.449999] ACPI: No dock devices found.
Sep 23 07:13:43 node-1 kernel: [    0.461738] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 23 07:13:43 node-1 kernel: [    0.461742] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 23 07:13:43 node-1 kernel: [    0.461746] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 23 07:13:43 node-1 kernel: [    0.461774] PCI host bridge to bus 0000:ff
Sep 23 07:13:43 node-1 kernel: [    0.461776] pci_bus 0000:ff: root bus resource [bus ff]
Sep 23 07:13:43 node-1 kernel: [    0.461784] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.461822] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.461853] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.461889] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.461918] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.461948] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.461979] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462009] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462040] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462068] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462094] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462121] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462149] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462175] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462202] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462229] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462258] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462286] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462312] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.462340] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462368] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.462395] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462423] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462454] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.462489] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462520] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462550] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462581] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462611] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462642] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462672] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462703] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462733] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462766] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462800] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462833] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462867] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462898] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462926] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462957] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.462990] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463029] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463066] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463097] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463126] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463158] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463188] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463219] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463253] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463285] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463317] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463347] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463377] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463407] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463437] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463469] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463502] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463560] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 23 07:13:43 node-1 kernel: [    0.463563] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 23 07:13:43 node-1 kernel: [    0.463566] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 23 07:13:43 node-1 kernel: [    0.463584] PCI host bridge to bus 0000:7f
Sep 23 07:13:43 node-1 kernel: [    0.463586] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 23 07:13:43 node-1 kernel: [    0.463591] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463622] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.463652] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463682] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463704] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.463729] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.463756] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463783] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463807] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463830] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463852] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463875] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463899] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463921] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463945] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463971] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.463993] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464016] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464039] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.464062] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464085] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.464107] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464130] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464157] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 23 07:13:43 node-1 kernel: [    0.464191] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464218] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464244] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464272] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464297] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464326] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464353] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464381] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464408] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464437] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464465] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464494] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464523] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464548] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464573] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464601] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464627] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464659] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464690] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464719] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464743] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464771] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464797] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464827] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464854] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464882] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464913] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464939] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464962] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.464989] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.465015] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.465047] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.465074] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.466332] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 23 07:13:43 node-1 kernel: [    0.466336] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 23 07:13:43 node-1 kernel: [    0.467460] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 23 07:13:43 node-1 kernel: [    0.467971] PCI host bridge to bus 0000:00
Sep 23 07:13:43 node-1 kernel: [    0.467973] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 23 07:13:43 node-1 kernel: [    0.467975] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 23 07:13:43 node-1 kernel: [    0.467976] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 23 07:13:43 node-1 kernel: [    0.467978] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 23 07:13:43 node-1 kernel: [    0.467979] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 23 07:13:43 node-1 kernel: [    0.467980] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 23 07:13:43 node-1 kernel: [    0.467982] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 23 07:13:43 node-1 kernel: [    0.467988] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 23 07:13:43 node-1 kernel: [    0.468071] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.468102] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.468143] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 23 07:13:43 node-1 kernel: [    0.468163] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.468193] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.468233] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 23 07:13:43 node-1 kernel: [    0.468252] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.468282] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.468325] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 23 07:13:43 node-1 kernel: [    0.468343] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.468414] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.468491] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.468568] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 23 07:13:43 node-1 kernel: [    0.468573] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 23 07:13:43 node-1 kernel: [    0.468658] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 23 07:13:43 node-1 kernel: [    0.468806] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 23 07:13:43 node-1 kernel: [    0.468823] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 23 07:13:43 node-1 kernel: [    0.468900] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.468959] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 23 07:13:43 node-1 kernel: [    0.468981] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.469036] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.469080] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 23 07:13:43 node-1 kernel: [    0.469108] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.469164] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.469207] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 23 07:13:43 node-1 kernel: [    0.469231] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 23 07:13:43 node-1 kernel: [    0.469249] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 23 07:13:43 node-1 kernel: [    0.469326] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.469376] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 23 07:13:43 node-1 kernel: [    0.469403] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 23 07:13:43 node-1 kernel: [    0.469652] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 23 07:13:43 node-1 kernel: [    0.469658] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 23 07:13:43 node-1 kernel: [    0.469664] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.469670] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.469677] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 23 07:13:43 node-1 kernel: [    0.469707] pci 0000:01:00.0: supports D1 D2
Sep 23 07:13:43 node-1 kernel: [    0.475634] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 23 07:13:43 node-1 kernel: [    0.475641] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 23 07:13:43 node-1 kernel: [    0.475645] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 23 07:13:43 node-1 kernel: [    0.475908] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.475969] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 23 07:13:43 node-1 kernel: [    0.483631] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 23 07:13:43 node-1 kernel: [    0.483638] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.483654] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 23 07:13:43 node-1 kernel: [    0.483709] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.483776] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.483853] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.483898] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 23 07:13:43 node-1 kernel: [    0.483902] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.483903] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 23 07:13:43 node-1 kernel: [    0.483956] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.484083] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.484137] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 23 07:13:43 node-1 kernel: [    0.484140] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.484142] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.484191] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.484310] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.484352] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.484471] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.484510] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.484649] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.484688] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 23 07:13:43 node-1 kernel: [    0.484806] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 23 07:13:43 node-1 kernel: [    0.484851] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 23 07:13:43 node-1 kernel: [    0.484853] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.484855] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.484914] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 23 07:13:43 node-1 kernel: [    0.484979] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.485031] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.485073] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 23 07:13:43 node-1 kernel: [    0.485155] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 23 07:13:43 node-1 kernel: [    0.485261] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 23 07:13:43 node-1 kernel: [    0.485263] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.485265] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.485321] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 23 07:13:43 node-1 kernel: [    0.485375] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.485424] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.485666] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 23 07:13:43 node-1 kernel: [    0.485670] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 23 07:13:43 node-1 kernel: [    0.485735] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 23 07:13:43 node-1 kernel: [    0.485789] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.485838] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.486048] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 23 07:13:43 node-1 kernel: [    0.486051] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 23 07:13:43 node-1 kernel: [    0.486110] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 23 07:13:43 node-1 kernel: [    0.486169] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.486222] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 23 07:13:43 node-1 kernel: [    0.486444] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 23 07:13:43 node-1 kernel: [    0.486448] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 23 07:13:43 node-1 kernel: [    0.486645] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 23 07:13:43 node-1 kernel: [    0.486683] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 23 07:13:43 node-1 kernel: [    0.486758] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 23 07:13:43 node-1 kernel: [    0.486777] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 23 07:13:43 node-1 kernel: [    0.486790] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 23 07:13:43 node-1 kernel: [    0.486803] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 23 07:13:43 node-1 kernel: [    0.486853] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 23 07:13:43 node-1 kernel: [    0.491638] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 23 07:13:43 node-1 kernel: [    0.491647] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 23 07:13:43 node-1 kernel: [    0.491699] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 23 07:13:43 node-1 kernel: [    0.492397] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 23 07:13:43 node-1 kernel: [    0.492400] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 23 07:13:43 node-1 kernel: [    0.492525] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 23 07:13:43 node-1 kernel: [    0.492632] PCI host bridge to bus 0000:80
Sep 23 07:13:43 node-1 kernel: [    0.492634] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 23 07:13:43 node-1 kernel: [    0.492636] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 23 07:13:43 node-1 kernel: [    0.492637] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 23 07:13:43 node-1 kernel: [    0.492645] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.492709] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.492777] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 23 07:13:43 node-1 kernel: [    0.492840] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 23 07:13:43 node-1 kernel: [    0.492846] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 23 07:13:43 node-1 kernel: [    0.492917] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 23 07:13:43 node-1 kernel: [    0.493217] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 23 07:13:43 node-1 kernel: [    0.493249] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 23 07:13:43 node-1 kernel: [    0.493279] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 23 07:13:43 node-1 kernel: [    0.493308] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 23 07:13:43 node-1 kernel: [    0.493338] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 23 07:13:43 node-1 kernel: [    0.493367] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 23 07:13:43 node-1 kernel: [    0.493397] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 23 07:13:43 node-1 kernel: [    0.493427] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 23 07:13:43 node-1 kernel: [    0.493513] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 23 07:13:43 node-1 kernel: [    0.493517] ACPI: \_SB_.UNC1: notify handler is installed
Sep 23 07:13:43 node-1 kernel: [    0.493518] ACPI: \_SB_.UNC0: notify handler is installed
Sep 23 07:13:43 node-1 kernel: [    0.493533] ACPI: \_SB_.PCI0: notify handler is installed
Sep 23 07:13:43 node-1 kernel: [    0.493586] ACPI: \_SB_.PCI1: notify handler is installed
Sep 23 07:13:43 node-1 kernel: [    0.493665] Found 4 acpi root devices
Sep 23 07:13:43 node-1 kernel: [    0.493774] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 23 07:13:43 node-1 kernel: [    0.493776] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 23 07:13:43 node-1 kernel: [    0.493778] vgaarb: loaded
Sep 23 07:13:43 node-1 kernel: [    0.493779] vgaarb: bridge control possible 0000:0c:00.0
Sep 23 07:13:43 node-1 kernel: [    0.493902] SCSI subsystem initialized
Sep 23 07:13:43 node-1 kernel: [    0.493966] libata version 3.00 loaded.
Sep 23 07:13:43 node-1 kernel: [    0.493981] ACPI: bus type USB registered
Sep 23 07:13:43 node-1 kernel: [    0.493992] usbcore: registered new interface driver usbfs
Sep 23 07:13:43 node-1 kernel: [    0.493997] usbcore: registered new interface driver hub
Sep 23 07:13:43 node-1 kernel: [    0.494021] usbcore: registered new device driver usb
Sep 23 07:13:43 node-1 kernel: [    0.494188] PCI: Using ACPI for IRQ routing
Sep 23 07:13:43 node-1 kernel: [    0.497775] PCI: pci_cache_line_size set to 64 bytes
Sep 23 07:13:43 node-1 kernel: [    0.497982] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 23 07:13:43 node-1 kernel: [    0.497983] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 23 07:13:43 node-1 kernel: [    0.497984] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 23 07:13:43 node-1 kernel: [    0.498049] NetLabel: Initializing
Sep 23 07:13:43 node-1 kernel: [    0.498051] NetLabel:  domain hash size = 128
Sep 23 07:13:43 node-1 kernel: [    0.498051] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 23 07:13:43 node-1 kernel: [    0.498062] NetLabel:  unlabeled traffic allowed by default
Sep 23 07:13:43 node-1 kernel: [    0.498119] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 23 07:13:43 node-1 kernel: [    0.498123] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 23 07:13:43 node-1 kernel: [    0.500193] Switched to clocksource hpet
Sep 23 07:13:43 node-1 kernel: [    0.504636] AppArmor: AppArmor Filesystem Enabled
Sep 23 07:13:43 node-1 kernel: [    0.504674] pnp: PnP ACPI init
Sep 23 07:13:43 node-1 kernel: [    0.504686] ACPI: bus type PNP registered
Sep 23 07:13:43 node-1 kernel: [    0.504863] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 23 07:13:43 node-1 kernel: [    0.504874] pnp 00:01: [dma 4]
Sep 23 07:13:43 node-1 kernel: [    0.504893] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 23 07:13:43 node-1 kernel: [    0.504927] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 23 07:13:43 node-1 kernel: [    0.504952] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 23 07:13:43 node-1 kernel: [    0.504973] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 23 07:13:43 node-1 kernel: [    0.505021] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 23 07:13:43 node-1 kernel: [    0.505132] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505135] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 23 07:13:43 node-1 kernel: [    0.505137] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505138] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505140] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505141] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505144] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 23 07:13:43 node-1 kernel: [    0.505146] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505148] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505149] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505151] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505152] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505154] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 23 07:13:43 node-1 kernel: [    0.505156] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 23 07:13:43 node-1 kernel: [    0.505256] pnp 00:07: [dma 0 disabled]
Sep 23 07:13:43 node-1 kernel: [    0.505289] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 23 07:13:43 node-1 kernel: [    0.505371] pnp 00:08: [dma 0 disabled]
Sep 23 07:13:43 node-1 kernel: [    0.505407] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 23 07:13:43 node-1 kernel: [    0.505465] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 23 07:13:43 node-1 kernel: [    0.505912] pnp: PnP ACPI: found 10 devices
Sep 23 07:13:43 node-1 kernel: [    0.505914] ACPI: bus type PNP unregistered
Sep 23 07:13:43 node-1 kernel: [    0.511930] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 23 07:13:43 node-1 kernel: [    0.511934] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 23 07:13:43 node-1 kernel: [    0.511937] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 23 07:13:43 node-1 kernel: [    0.511942] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 23 07:13:43 node-1 kernel: [    0.511944] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.511959] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.511991] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 23 07:13:43 node-1 kernel: [    0.512006] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512035] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 23 07:13:43 node-1 kernel: [    0.512050] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 23 07:13:43 node-1 kernel: [    0.512079] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 23 07:13:43 node-1 kernel: [    0.512093] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 23 07:13:43 node-1 kernel: [    0.512122] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 23 07:13:43 node-1 kernel: [    0.512124] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512139] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512173] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 23 07:13:43 node-1 kernel: [    0.512175] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512189] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512218] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 23 07:13:43 node-1 kernel: [    0.512220] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512223] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512228] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 23 07:13:43 node-1 kernel: [    0.512230] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512232] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512237] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 23 07:13:43 node-1 kernel: [    0.512243] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 23 07:13:43 node-1 kernel: [    0.512251] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 23 07:13:43 node-1 kernel: [    0.512255] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 23 07:13:43 node-1 kernel: [    0.512262] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 23 07:13:43 node-1 kernel: [    0.512263] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 23 07:13:43 node-1 kernel: [    0.512264] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 23 07:13:43 node-1 kernel: [    0.512265] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 23 07:13:43 node-1 kernel: [    0.512266] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 23 07:13:43 node-1 kernel: [    0.512267] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 23 07:13:43 node-1 kernel: [    0.512268] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 23 07:13:43 node-1 kernel: [    0.512269] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 23 07:13:43 node-1 kernel: [    0.512270] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512271] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512272] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512273] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512274] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512275] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512276] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512277] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512278] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 23 07:13:43 node-1 kernel: [    0.512279] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512280] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 23 07:13:43 node-1 kernel: [    0.512282] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 23 07:13:43 node-1 kernel: [    0.512283] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 23 07:13:43 node-1 kernel: [    0.512284] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 23 07:13:43 node-1 kernel: [    0.512287] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 23 07:13:43 node-1 kernel: [    0.512288] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 23 07:13:43 node-1 kernel: [    0.512327] NET: Registered protocol family 2
Sep 23 07:13:43 node-1 kernel: [    0.512625] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.513005] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.513170] TCP: Hash tables configured (established 262144 bind 65536)
Sep 23 07:13:43 node-1 kernel: [    0.513212] TCP: reno registered
Sep 23 07:13:43 node-1 kernel: [    0.513243] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.513353] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.513518] NET: Registered protocol family 1
Sep 23 07:13:43 node-1 kernel: [    0.552286] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 23 07:13:43 node-1 kernel: [    0.552302] PCI: CLS 64 bytes, default 64
Sep 23 07:13:43 node-1 kernel: [    0.552388] Trying to unpack rootfs image as initramfs...
Sep 23 07:13:43 node-1 kernel: [    0.775100] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 23 07:13:43 node-1 kernel: [    0.775166] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 23 07:13:43 node-1 kernel: [    0.775169] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 23 07:13:43 node-1 kernel: [    0.775563] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775571] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775579] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775586] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775594] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775601] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775606] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775612] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775619] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775625] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775634] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775641] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775647] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775653] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775659] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775665] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 23 07:13:43 node-1 kernel: [    0.775717] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 23 07:13:43 node-1 kernel: [    0.775720] Scanning for low memory corruption every 60 seconds
Sep 23 07:13:43 node-1 kernel: [    0.776032] Initialise system trusted keyring
Sep 23 07:13:43 node-1 kernel: [    0.776083] audit: initializing netlink socket (disabled)
Sep 23 07:13:43 node-1 kernel: [    0.776094] type=2000 audit(1474614787.732:1): initialized
Sep 23 07:13:43 node-1 kernel: [    0.793930] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 23 07:13:43 node-1 kernel: [    0.795435] zbud: loaded
Sep 23 07:13:43 node-1 kernel: [    0.795558] VFS: Disk quotas dquot_6.5.2
Sep 23 07:13:43 node-1 kernel: [    0.795597] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 23 07:13:43 node-1 kernel: [    0.795959] fuse init (API version 7.22)
Sep 23 07:13:43 node-1 kernel: [    0.796011] msgmni has been set to 32768
Sep 23 07:13:43 node-1 kernel: [    0.796055] Key type big_key registered
Sep 23 07:13:43 node-1 kernel: [    0.796545] Key type asymmetric registered
Sep 23 07:13:43 node-1 kernel: [    0.796547] Asymmetric key parser 'x509' registered
Sep 23 07:13:43 node-1 kernel: [    0.796569] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 23 07:13:43 node-1 kernel: [    0.796637] io scheduler noop registered
Sep 23 07:13:43 node-1 kernel: [    0.796639] io scheduler deadline registered (default)
Sep 23 07:13:43 node-1 kernel: [    0.796656] io scheduler cfq registered
Sep 23 07:13:43 node-1 kernel: [    0.797179] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    0.797370] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    0.797488] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    0.797603] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    0.797731] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    0.797820] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    0.798218] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 23 07:13:43 node-1 kernel: [    0.798257] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 23 07:13:43 node-1 kernel: [    0.798284] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 23 07:13:43 node-1 kernel: [    0.798306] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798311] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798317] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 23 07:13:43 node-1 kernel: [    0.798328] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798332] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798336] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798340] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798344] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798347] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798351] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798355] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798358] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798362] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798365] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798369] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798375] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 23 07:13:43 node-1 kernel: [    0.798391] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798397] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 23 07:13:43 node-1 kernel: [    0.798416] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798422] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 23 07:13:43 node-1 kernel: [    0.798441] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798445] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 23 07:13:43 node-1 kernel: [    0.798451] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 23 07:13:43 node-1 kernel: [    0.798501] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 23 07:13:43 node-1 kernel: [    0.798513] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 23 07:13:43 node-1 kernel: [    0.798522] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 23 07:13:43 node-1 kernel: [    0.798544] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 23 07:13:43 node-1 kernel: [    0.798629] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 23 07:13:43 node-1 kernel: [    0.798632] vesafb: scrolling: redraw
Sep 23 07:13:43 node-1 kernel: [    0.798636] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 23 07:13:43 node-1 kernel: [    0.819033] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 23 07:13:43 node-1 kernel: [    0.827535] Console: switching to colour frame buffer device 80x30
Sep 23 07:13:43 node-1 kernel: [    0.836217] fb0: VESA VGA frame buffer device
Sep 23 07:13:43 node-1 kernel: [    0.836410] intel_idle: MWAIT substates: 0x2120
Sep 23 07:13:43 node-1 kernel: [    0.836411] intel_idle: v0.4 model 0x3F
Sep 23 07:13:43 node-1 kernel: [    0.836412] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 23 07:13:43 node-1 kernel: [    0.836635] ipmi message handler version 39.2
Sep 23 07:13:43 node-1 kernel: [    0.836896] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 23 07:13:43 node-1 kernel: [    0.837327] ACPI: AC Adapter [P111] (on-line)
Sep 23 07:13:43 node-1 kernel: [    0.842603] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 23 07:13:43 node-1 kernel: [    0.853641] ACPI: Power Button [PWRB]
Sep 23 07:13:43 node-1 kernel: [    0.859419] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 23 07:13:43 node-1 kernel: [    0.871081] ACPI: Power Button [PWRF]
Sep 23 07:13:43 node-1 kernel: [    0.897692] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 23 07:13:43 node-1 kernel: [    0.909369] pstore: Registered erst as persistent store backend
Sep 23 07:13:43 node-1 kernel: [    0.915579] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 23 07:13:43 node-1 kernel: [    0.927532] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 23 07:13:43 node-1 kernel: [    0.954279] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 23 07:13:43 node-1 kernel: [    0.987599] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 23 07:13:43 node-1 kernel: [    1.001699] Linux agpgart interface v0.103
Sep 23 07:13:43 node-1 kernel: [    1.009378] brd: module loaded
Sep 23 07:13:43 node-1 kernel: [    1.016420] loop: module loaded
Sep 23 07:13:43 node-1 kernel: [    1.023127] libphy: Fixed MDIO Bus: probed
Sep 23 07:13:43 node-1 kernel: [    1.029587] tun: Universal TUN/TAP device driver, 1.6
Sep 23 07:13:43 node-1 kernel: [    1.036048] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 23 07:13:43 node-1 kernel: [    1.042552] PPP generic driver version 2.4.2
Sep 23 07:13:43 node-1 kernel: [    1.048924] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 23 07:13:43 node-1 kernel: [    1.055357] ehci-pci: EHCI PCI platform driver
Sep 23 07:13:43 node-1 kernel: [    1.061862] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 23 07:13:43 node-1 kernel: [    1.068265] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 23 07:13:43 node-1 kernel: [    1.080768] ehci-pci 0000:00:1a.0: debug port 2
Sep 23 07:13:43 node-1 kernel: [    1.090953] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 23 07:13:43 node-1 kernel: [    1.090972] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 23 07:13:43 node-1 kernel: [    1.107669] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 23 07:13:43 node-1 kernel: [    1.113721] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 23 07:13:43 node-1 kernel: [    1.119895] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 23 07:13:43 node-1 kernel: [    1.131822] usb usb1: Product: EHCI Host Controller
Sep 23 07:13:43 node-1 kernel: [    1.137881] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 23 07:13:43 node-1 kernel: [    1.143952] usb usb1: SerialNumber: 0000:00:1a.0
Sep 23 07:13:43 node-1 kernel: [    1.149912] hub 1-0:1.0: USB hub found
Sep 23 07:13:43 node-1 kernel: [    1.155670] hub 1-0:1.0: 2 ports detected
Sep 23 07:13:43 node-1 kernel: [    1.161452] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 23 07:13:43 node-1 kernel: [    1.167034] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 23 07:13:43 node-1 kernel: [    1.177909] ehci-pci 0000:00:1d.0: debug port 2
Sep 23 07:13:43 node-1 kernel: [    1.187214] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 23 07:13:43 node-1 kernel: [    1.187217] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 23 07:13:43 node-1 kernel: [    1.203588] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 23 07:13:43 node-1 kernel: [    1.208780] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 23 07:13:43 node-1 kernel: [    1.214067] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 23 07:13:43 node-1 kernel: [    1.224640] usb usb2: Product: EHCI Host Controller
Sep 23 07:13:43 node-1 kernel: [    1.230104] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 23 07:13:43 node-1 kernel: [    1.235657] usb usb2: SerialNumber: 0000:00:1d.0
Sep 23 07:13:43 node-1 kernel: [    1.241195] hub 2-0:1.0: USB hub found
Sep 23 07:13:43 node-1 kernel: [    1.246553] hub 2-0:1.0: 2 ports detected
Sep 23 07:13:43 node-1 kernel: [    1.251856] ehci-platform: EHCI generic platform driver
Sep 23 07:13:43 node-1 kernel: [    1.257079] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 23 07:13:43 node-1 kernel: [    1.262384] ohci-pci: OHCI PCI platform driver
Sep 23 07:13:43 node-1 kernel: [    1.267688] ohci-platform: OHCI generic platform driver
Sep 23 07:13:43 node-1 kernel: [    1.272898] uhci_hcd: USB Universal Host Controller Interface driver
Sep 23 07:13:43 node-1 kernel: [    1.278255] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 23 07:13:43 node-1 kernel: [    1.471367] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 23 07:13:43 node-1 kernel: [    1.631610] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 23 07:13:43 node-1 kernel: [    1.637120] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 23 07:13:43 node-1 kernel: [    1.642882] hub 1-1:1.0: USB hub found
Sep 23 07:13:43 node-1 kernel: [    1.648346] hub 1-1:1.0: 6 ports detected
Sep 23 07:13:43 node-1 kernel: [    1.763111] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 23 07:13:43 node-1 kernel: [    2.031270] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 23 07:13:43 node-1 kernel: [    2.036694] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 23 07:13:43 node-1 kernel: [    2.042285] hub 2-1:1.0: USB hub found
Sep 23 07:13:43 node-1 kernel: [    2.047881] hub 2-1:1.0: 8 ports detected
Sep 23 07:13:43 node-1 kernel: [    2.318943] i8042: No controller found
Sep 23 07:13:43 node-1 kernel: [    2.322710] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 23 07:13:43 node-1 kernel: [    2.329815] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 23 07:13:43 node-1 kernel: [    2.331347] mousedev: PS/2 mouse device common for all mice
Sep 23 07:13:43 node-1 kernel: [    2.333006] rtc_cmos 00:02: RTC can wake from S4
Sep 23 07:13:43 node-1 kernel: [    2.334427] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 23 07:13:43 node-1 kernel: [    2.335082] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 23 07:13:43 node-1 kernel: [    2.335989] device-mapper: uevent: version 1.0.3
Sep 23 07:13:43 node-1 kernel: [    2.336964] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 23 07:13:43 node-1 kernel: [    2.337136] ledtrig-cpu: registered to indicate activity on CPUs
Sep 23 07:13:43 node-1 kernel: [    2.339273] TCP: cubic registered
Sep 23 07:13:43 node-1 kernel: [    2.340307] NET: Registered protocol family 10
Sep 23 07:13:43 node-1 kernel: [    2.343343] NET: Registered protocol family 17
Sep 23 07:13:43 node-1 kernel: [    2.343468] Key type dns_resolver registered
Sep 23 07:13:43 node-1 kernel: [    2.350110] Loading compiled-in X.509 certificates
Sep 23 07:13:43 node-1 kernel: [    2.352197] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 23 07:13:43 node-1 kernel: [    2.352476] registered taskstats version 1
Sep 23 07:13:43 node-1 kernel: [    2.392265] Key type trusted registered
Sep 23 07:13:43 node-1 kernel: [    2.416409] Key type encrypted registered
Sep 23 07:13:43 node-1 kernel: [    2.416420] AppArmor: AppArmor sha1 policy hashing enabled
Sep 23 07:13:43 node-1 kernel: [    2.416456] IMA: No TPM chip found, activating TPM-bypass!
Sep 23 07:13:43 node-1 kernel: [    2.425532] regulator-dummy: disabling
Sep 23 07:13:43 node-1 kernel: [    2.426363]   Magic number: 0:655:218
Sep 23 07:13:43 node-1 kernel: [    2.428279] acpi device:69: hash matches
Sep 23 07:13:43 node-1 kernel: [    2.428445] acpi device:3c: hash matches
Sep 23 07:13:43 node-1 kernel: [    2.429634] memory memory100: hash matches
Sep 23 07:13:43 node-1 kernel: [    2.468254] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 23 07:13:43 node-1 kernel: [    2.468255] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 23 07:13:43 node-1 kernel: [    2.468256] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 23 07:13:43 node-1 kernel: [    2.468256] usb 2-1.4: Manufacturer: Avocent
Sep 23 07:13:43 node-1 kernel: [    2.468257] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 23 07:13:43 node-1 kernel: [    2.510421] rtc_cmos 00:02: setting system clock to 2016-09-23 07:13:10 UTC (1474614790)
Sep 23 07:13:43 node-1 kernel: [    2.522305] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 23 07:13:43 node-1 kernel: [    2.527723] EDD information not available.
Sep 23 07:13:43 node-1 kernel: [    2.533079] PM: Hibernation image not present or could not be loaded.
Sep 23 07:13:43 node-1 kernel: [    2.533939] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 23 07:13:43 node-1 kernel: [    2.544615] Write protecting the kernel read-only data: 12288k
Sep 23 07:13:43 node-1 kernel: [    2.550550] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 23 07:13:43 node-1 kernel: [    2.562827] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 23 07:13:43 node-1 kernel: [    2.594919] device-mapper: multipath: version 1.6.0 loaded
Sep 23 07:13:43 node-1 kernel: [    2.602593] systemd-udevd[215]: starting version 204
Sep 23 07:13:43 node-1 kernel: [    2.620650] md: linear personality registered for level -1
Sep 23 07:13:43 node-1 kernel: [    2.635115] md: multipath personality registered for level -4
Sep 23 07:13:43 node-1 kernel: [    2.642940] md: raid0 personality registered for level 0
Sep 23 07:13:43 node-1 kernel: [    2.651106] md: raid1 personality registered for level 1
Sep 23 07:13:43 node-1 kernel: [    2.660385] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 23 07:13:43 node-1 kernel: [    2.666588] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 23 07:13:43 node-1 kernel: [    2.672793] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 23 07:13:43 node-1 kernel: [    2.674948] megasas: FW now in Ready state
Sep 23 07:13:43 node-1 kernel: [    2.675313] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.675446] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.675577] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.675746] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.675837] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.675961] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676028] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676160] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676274] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676419] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676472] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676590] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676755] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.676850] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.677013] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.677129] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.677778] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 23 07:13:43 node-1 kernel: [    2.698528] hidraw: raw HID events driver (C) Jiri Kosina
Sep 23 07:13:43 node-1 kernel: [    2.707146] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 23 07:13:43 node-1 kernel: [    2.711627] usbcore: registered new interface driver usbhid
Sep 23 07:13:43 node-1 kernel: [    2.711642] usbhid: USB HID core driver
Sep 23 07:13:43 node-1 kernel: [    2.726362] raid6: sse2x1    9687 MB/s
Sep 23 07:13:43 node-1 kernel: [    2.740020] 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
Sep 23 07:13:43 node-1 kernel: [    2.753307] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 23 07:13:43 node-1 kernel: [    2.760038] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.760044] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.760049] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.760054] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.760095] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.783403] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 23 07:13:43 node-1 kernel: [    2.794323] raid6: sse2x2   13543 MB/s
Sep 23 07:13:43 node-1 kernel: [    2.802377] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 23 07:13:43 node-1 kernel: [    2.815167] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 23 07:13:43 node-1 kernel: [    2.821797] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.821802] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.821806] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.821810] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.821813] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.821818] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.821862] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.821903] 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
Sep 23 07:13:43 node-1 kernel: [    2.822333] 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
Sep 23 07:13:43 node-1 kernel: [    2.822440] 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
Sep 23 07:13:43 node-1 kernel: [    2.822901] 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
Sep 23 07:13:43 node-1 kernel: [    2.822956] 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
Sep 23 07:13:43 node-1 kernel: [    2.823430] 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
Sep 23 07:13:43 node-1 kernel: [    2.862271] raid6: sse2x4   16011 MB/s
Sep 23 07:13:43 node-1 kernel: [    2.930133] raid6: avx2x1   22347 MB/s
Sep 23 07:13:43 node-1 kernel: [    2.936464] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 23 07:13:43 node-1 kernel: [    2.936465] 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
Sep 23 07:13:43 node-1 kernel: [    2.936466] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 23 07:13:43 node-1 kernel: [    2.936528] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.936567] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.936606] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.936646] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.936716] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.947992] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 23 07:13:43 node-1 kernel: [    2.947994] 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
Sep 23 07:13:43 node-1 kernel: [    2.947994] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 23 07:13:43 node-1 kernel: [    2.948055] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.948094] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.948135] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.948174] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 23 07:13:43 node-1 kernel: [    2.948235] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 23 07:13:43 node-1 kernel: [    3.014134] megasas:IOC Init cmd success
Sep 23 07:13:43 node-1 kernel: [    3.062036] megasas: INIT adapter done
Sep 23 07:13:43 node-1 kernel: [    3.113979] raid6: avx2x2   26318 MB/s
Sep 23 07:13:43 node-1 kernel: [    3.137978] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 23 07:13:43 node-1 kernel: [    3.144987] scsi0 : LSI SAS based MegaRAID driver
Sep 23 07:13:43 node-1 kernel: [    3.152461] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 23 07:13:43 node-1 kernel: [    3.171649] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 23 07:13:43 node-1 kernel: [    3.185917] raid6: avx2x4   30474 MB/s
Sep 23 07:13:43 node-1 kernel: [    3.188438] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 23 07:13:43 node-1 kernel: [    3.188630] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 23 07:13:43 node-1 kernel: [    3.189114] sd 0:2:0:0: [sda] Write Protect is off
Sep 23 07:13:43 node-1 kernel: [    3.189115] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 23 07:13:43 node-1 kernel: [    3.189189] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 23 07:13:43 node-1 kernel: [    3.221180]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 23 07:13:43 node-1 kernel: [    3.223968] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 23 07:13:43 node-1 kernel: [    3.241770] raid6: using algorithm avx2x4 (30474 MB/s)
Sep 23 07:13:43 node-1 kernel: [    3.247883] raid6: using avx2x2 recovery algorithm
Sep 23 07:13:43 node-1 kernel: [    3.254631] xor: automatically using best checksumming function:
Sep 23 07:13:43 node-1 kernel: [    3.297802]    avx       : 35708.000 MB/sec
Sep 23 07:13:43 node-1 kernel: [    3.304524] async_tx: api initialized (async)
Sep 23 07:13:43 node-1 kernel: [    3.314612] md: raid6 personality registered for level 6
Sep 23 07:13:43 node-1 kernel: [    3.320403] md: raid5 personality registered for level 5
Sep 23 07:13:43 node-1 kernel: [    3.325961] md: raid4 personality registered for level 4
Sep 23 07:13:43 node-1 kernel: [    3.334459] md: raid10 personality registered for level 10
Sep 23 07:13:43 node-1 kernel: [    3.378359] random: lvm urandom read with 26 bits of entropy available
Sep 23 07:13:43 node-1 kernel: [    3.387254] multipathd (363): /proc/363/oom_adj is deprecated, please use /proc/363/oom_score_adj instead.
Sep 23 07:13:43 node-1 kernel: [    3.498547] bio: create slab <bio-1> at 1
Sep 23 07:13:43 node-1 kernel: [    3.509732] Switched to clocksource tsc
Sep 23 07:13:43 node-1 kernel: [    4.298530] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 23 07:13:43 node-1 kernel: [    5.028043] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 23 07:13:43 node-1 kernel: [    5.052786] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 23 07:13:43 node-1 kernel: [    5.187764] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 23 07:13:43 node-1 kernel: [    5.241636] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 23 07:13:43 node-1 kernel: [    5.311779] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 23 07:13:43 node-1 kernel: [    5.436205] random: nonblocking pool is initialized
Sep 23 07:13:43 node-1 kernel: [    5.514819] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 23 07:13:43 node-1 kernel: [    5.570086] XFS (dm-0): Mounting Filesystem
Sep 23 07:13:43 node-1 kernel: [    5.805142] XFS (dm-0): Ending clean mount
Sep 23 07:13:43 node-1 kernel: [    5.896574] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 23 07:13:43 node-1 kernel: [    5.950027] XFS (dm-1): Mounting Filesystem
Sep 23 07:13:43 node-1 kernel: [    6.109040] XFS (dm-1): Ending clean mount
Sep 23 07:13:43 node-1 kernel: [    7.727596] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 23 07:13:43 node-1 kernel: [    7.755659] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 23 07:13:43 node-1 kernel: [    7.896672] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 23 07:13:43 node-1 kernel: [    7.896678] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 23 07:13:43 node-1 kernel: [    7.896682] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 23 07:13:43 node-1 kernel: [    7.896686] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 23 07:13:43 node-1 kernel: [    7.940445] systemd-udevd[774]: starting version 204
Sep 23 07:13:43 node-1 kernel: [    8.155453] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 23 07:13:43 node-1 kernel: [    8.155459] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 23 07:13:43 node-1 kernel: [    8.155462] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 23 07:13:43 node-1 kernel: [    8.155464] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 23 07:13:43 node-1 kernel: [    8.155496] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 23 07:13:43 node-1 kernel: [    8.155522] power_meter ACPI000D:00: Found ACPI power meter.
Sep 23 07:13:43 node-1 kernel: [    8.155542] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 23 07:13:43 node-1 kernel: [    8.166151] wmi: Mapper loaded
Sep 23 07:13:43 node-1 kernel: [    8.167236] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 23 07:13:43 node-1 kernel: [    8.176546] IPMI System Interface driver.
Sep 23 07:13:43 node-1 kernel: [    8.176606] ipmi_si: probing via ACPI
Sep 23 07:13:43 node-1 kernel: [    8.176619] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 23 07:13:43 node-1 kernel: [    8.176620] ipmi_si: Adding ACPI-specified kcs state machine
Sep 23 07:13:43 node-1 kernel: [    8.176640] ipmi_si: probing via SMBIOS
Sep 23 07:13:43 node-1 kernel: [    8.176641] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 23 07:13:43 node-1 kernel: [    8.176642] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 23 07:13:43 node-1 kernel: [    8.176644] ipmi_si: probing via SPMI
Sep 23 07:13:43 node-1 kernel: [    8.176645] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 23 07:13:43 node-1 kernel: [    8.176646] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 23 07:13:43 node-1 kernel: [    8.176648] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 23 07:13:43 node-1 kernel: [    8.242096] systemd-udevd[812]: renamed network interface eth1 to enp7s0
Sep 23 07:13:43 node-1 kernel: [    8.266005] systemd-udevd[814]: renamed network interface eth3 to enp9s0
Sep 23 07:13:43 node-1 kernel: [    8.301977] systemd-udevd[813]: renamed network interface eth2 to enp8s0
Sep 23 07:13:43 node-1 kernel: [    8.314895] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 23 07:13:43 node-1 kernel: [    8.314901] ipmi_si 00:09: IPMI kcs interface initialized
Sep 23 07:13:43 node-1 kernel: [    8.337936] systemd-udevd[810]: renamed network interface eth0 to enp6s0
Sep 23 07:13:43 node-1 kernel: [    8.551570] type=1400 audit(1474614796.622:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1037 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.551720] type=1400 audit(1474614796.622:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1037 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.551847] type=1400 audit(1474614796.622:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1037 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.555858] type=1400 audit(1474614796.626:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1039 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.555997] type=1400 audit(1474614796.626:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1039 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.556117] type=1400 audit(1474614796.626:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1039 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.565776] type=1400 audit(1474614796.638:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1038 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.565911] type=1400 audit(1474614796.638:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1038 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.566026] type=1400 audit(1474614796.638:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1038 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    8.570892] type=1400 audit(1474614796.642:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Sep 23 07:13:43 node-1 kernel: [    9.057371] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 23 07:13:43 node-1 kernel: [    9.065904] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 23 07:13:43 node-1 kernel: [    9.288823] enic 0000:06:00.0 enp6s0: Link UP
Sep 23 07:13:43 node-1 kernel: [    9.289245] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 23 07:13:43 node-1 kernel: [    9.289251] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 23 07:13:43 node-1 kernel: [   18.839537] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 23 07:13:43 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 23 07:13:44 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 23 07:13:44 node-1 kernel: [   37.387025] init: failsafe main process (8413) killed by TERM signal
Sep 23 07:13:44 node-1 dbus[8445]: [system] AppArmor D-Bus mediation is enabled
Sep 23 07:13:45 node-1 kernel: [   37.559573] audit_printk_skb: 30 callbacks suppressed
Sep 23 07:13:45 node-1 kernel: [   37.559575] type=1400 audit(1474614825.124:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8538 comm="apparmor_parser"
Sep 23 07:13:45 node-1 kernel: [   37.559580] type=1400 audit(1474614825.124:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Sep 23 07:13:45 node-1 kernel: [   37.559582] type=1400 audit(1474614825.124:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Sep 23 07:13:45 node-1 kernel: [   37.559798] type=1400 audit(1474614825.124:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Sep 23 07:13:45 node-1 kernel: [   37.559800] type=1400 audit(1474614825.124:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Sep 23 07:13:45 node-1 kernel: [   37.559913] type=1400 audit(1474614825.124:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Sep 23 07:13:45 node-1 kernel: [   37.565542] type=1400 audit(1474614825.132:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8539 comm="apparmor_parser"
Sep 23 07:13:45 node-1 kernel: [   37.625910] type=1400 audit(1474614825.188:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8541 comm="apparmor_parser"
Sep 23 07:13:45 node-1 cron[8570]: (CRON) INFO (pidfile fd = 3)
Sep 23 07:13:45 node-1 anacron[8588]: Anacron 2.3 started on 2016-09-23
Sep 23 07:13:45 node-1 cron[8608]: (CRON) STARTUP (fork ok)
Sep 23 07:13:45 node-1 cron[8608]: (CRON) INFO (Running @reboot jobs)
Sep 23 07:13:45 node-1 multipathd: path checkers start up
Sep 23 07:13:45 node-1 anacron[8588]: Will run job `cron.daily' in 5 min.
Sep 23 07:13:45 node-1 anacron[8588]: Will run job `cron.weekly' in 10 min.
Sep 23 07:13:45 node-1 anacron[8588]: Will run job `cron.monthly' in 15 min.
Sep 23 07:13:45 node-1 anacron[8588]: Jobs will be executed sequentially
Sep 23 07:13:45 node-1 postfix/master[8750]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 23 07:13:49 node-1 puppet-agent[8936]: Reopening log files
Sep 23 07:13:50 node-1 puppet-agent[8936]: Could not request certificate: Connection refused - connect(2)
Sep 23 07:14:01 node-1 CRON[9087]: (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")
Sep 23 07:14:04 node-1 puppet-user[9155]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 23 07:14:04 node-1 puppet-user[9155]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 23 07:14:05 node-1 puppet-user[9155]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 23 07:14:05 node-1 puppet-user[9155]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 23 07:14:06 node-1 puppet-user[9155]: Finished catalog run in 0.99 seconds
Sep 23 07:14:07 node-1 multipathd: uevent trigger error
Sep 23 07:14:07 node-1 puppet-user[9585]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 23 07:14:07 node-1 puppet-user[9585]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Sep 23 07:14:07 node-1 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 23 07:14:07 node-1 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 23 07:14:07 node-1 puppet-user[9585]: (/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"]'
Sep 23 07:14:07 node-1 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 23 07:14:07 node-1 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 23 07:14:07 node-1 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 23 07:14:07 node-1 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 23 07:14:07 node-1 puppet-user[9585]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 23 07:14:07 node-1 puppet-user[9585]: Finished catalog run in 0.05 seconds
Sep 23 07:14:08 node-1 puppet-user[10042]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 23 07:14:08 node-1 puppet-user[10042]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 23 07:14:08 node-1 puppet-user[10042]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 23 07:14:08 node-1 puppet-user[10042]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 23 07:14:08 node-1 puppet-user[10042]: Finished catalog run in 0.03 seconds
Sep 23 07:14:10 node-1 puppet-user[10500]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 23 07:14:10 node-1 puppet-user[10500]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 23 07:14:10 node-1 puppet-user[10500]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 23 07:14:10 node-1 puppet-user[10500]: Finished catalog run in 0.04 seconds
Sep 23 07:14:11 node-1 puppet-user[10947]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 23 07:14:11 node-1 puppet-user[10947]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Sep 23 07:14:11 node-1 puppet-user[10947]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 23 07:14:14 node-1 puppet-user[10947]: (/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
Sep 23 07:14:14 node-1 puppet-user[10947]: Finished catalog run in 2.35 seconds
Sep 23 07:14:15 node-1 puppet-user[11671]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 23 07:14:15 node-1 puppet-user[11671]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Sep 23 07:14:15 node-1 puppet-user[11671]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 23 07:14:15 node-1 puppet-user[11671]: (/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
Sep 23 07:14:15 node-1 puppet-user[11671]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 23 07:14:15 node-1 puppet-user[11671]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 23 07:14:15 node-1 puppet-user[11671]: Finished catalog run in 0.22 seconds
Sep 23 07:14:17 node-1 puppet-user[12150]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 23 07:14:17 node-1 puppet-user[12150]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep 23 07:14:17 node-1 puppet-user[12150]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 23 07:14:17 node-1 kernel: [   69.935021] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 23 07:14:17 node-1 kernel: [   69.935071] 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.
Sep 23 07:14:17 node-1 puppet-user[12150]: (/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'
Sep 23 07:14:17 node-1 puppet-user[12150]: Finished catalog run in 0.05 seconds
Sep 23 07:14:19 node-1 puppet-user[12612]: (Scope(Class[main])) MODULAR: sync_time
Sep 23 07:14:19 node-1 puppet-user[12612]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 23 07:14:19 node-1 ntpdate[13023]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 23 07:14:25 node-1 ntpdate[13023]: adjust time server 10.20.0.2 offset 0.267735 sec
Sep 23 07:14:25 node-1 puppet-user[12612]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 23 07:14:25 node-1 puppet-user[12612]: Finished catalog run in 6.17 seconds
Sep 23 07:14:26 node-1 kernel: [   78.666492] init: plymouth-upstart-bridge main process ended, respawning
Sep 23 07:14:26 node-1 puppet-agent[8936]: Could not run: SIGTERM
Sep 23 07:14:26 node-1 kernel: [   78.943308] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 23 07:14:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 23 07:14:26 node-1 nailgun-agent: D, [2016-09-23T07:14:01.595394 #9090] DEBUG -- : Sleep for 25 seconds before sending request
Sep 23 07:14:26 node-1 nailgun-agent: I, [2016-09-23T07:14:26.657099 #9090]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 23 07:14:26 node-1 ec2: 
Sep 23 07:14:26 node-1 ec2: #############################################################
Sep 23 07:14:26 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 23 07:14:26 node-1 ec2: 1024 c1:98:d0:c9:9e:b8:15:e3:5d:d9:05:ae:51:b3:f3:97  root@node-1.domain.tld (DSA)
Sep 23 07:14:26 node-1 ec2: 256 b3:d7:ec:8b:5b:b7:a1:89:6b:b5:35:25:d4:1f:6a:c0  root@node-1.domain.tld (ECDSA)
Sep 23 07:14:26 node-1 ec2: 256 09:a5:89:26:f6:40:c1:c5:ea:61:d7:44:76:2c:8b:98  root@node-1.domain.tld (ED25519)
Sep 23 07:14:26 node-1 ec2: 2048 be:ed:51:d1:92:5d:19:4a:4f:62:12:f4:b9:fc:09:6d  root@node-1.domain.tld (RSA)
Sep 23 07:14:26 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 23 07:14:26 node-1 ec2: #############################################################
Sep 23 07:14:27 node-1 nailgun-agent: D, [2016-09-23T07:14:27.120899 #9090] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 23 07:14:31 node-1 puppet-user[13530]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 23 07:14:31 node-1 puppet-user[13530]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 23 07:14:31 node-1 puppet-user[13530]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 23 07:14:31 node-1 puppet-user[13530]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Sep 23 07:14:31 node-1 puppet-user[13530]: Finished catalog run in 0.06 seconds
Sep 23 07:14:32 node-1 puppet-user[13983]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 23 07:14:33 node-1 puppet-user[13983]: Compiled catalog for node-1.domain.tld in environment production in 0.42 seconds
Sep 23 07:14:33 node-1 puppet-user[13983]: (/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
Sep 23 07:14:33 node-1 puppet-user[13983]: (/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
Sep 23 07:14:33 node-1 puppet-user[13983]: (/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
Sep 23 07:14:33 node-1 puppet-user[13983]: (/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
Sep 23 07:14:33 node-1 puppet-user[13983]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 23 07:14:33 node-1 puppet-user[13983]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 23 07:14:33 node-1 puppet-user[13983]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 23 07:14:33 node-1 puppet-user[13983]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 23 07:14:33 node-1 puppet-user[13983]: (/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
Sep 23 07:14:33 node-1 puppet-user[13983]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 23 07:14:34 node-1 puppet-user[13983]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 23 07:14:34 node-1 puppet-user[13983]: Finished catalog run in 0.79 seconds
Sep 23 07:14:35 node-1 puppet-user[14488]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 23 07:14:35 node-1 puppet-user[14488]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Sep 23 07:14:38 node-1 puppet-user[14488]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.128851 #9090] DEBUG -- : Trying to find block devices
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.128971 #9090] DEBUG -- : Found block device: sda
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.129052 #9090] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.129076 #9090] DEBUG -- : Trying to get list of physical devices
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.129235 #9090] DEBUG -- : Getting udev properties for device: sda
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.131230 #9090] 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"=>"0x618e72837274ff201cc7880
Sep 23 07:14:39 node-1 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81931", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.131254 #9090] DEBUG -- : Trying to find out if device sda is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.131294 #9090] DEBUG -- : Device sda removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.131309 #9090] DEBUG -- : Device sda seems to be appropriate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.131741 #9090] DEBUG -- : Getting udev properties for device: dm-0
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.133768 #9090] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-lh3FCMWsHevvOfms6qv9pzp9gQWuF6hplQD31dxYzgCKXd0c8fBgSpXk7OGjQjON /dev/disk/by-uuid/034aef5e-cf67-4b7c-9690-8e4a13e9c74c /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-lh3FCMWsHevvOfms6qv9pzp9gQWuF6hplQD31dxYzgCKXd0c8fBgSpXk7OGjQjON", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"034aef5e-cf67-4b7c-9690-8e4a13e9c74c", "ID_FS_UUID_ENC"=>"034aef5e-cf67-4b7c-9690-8e4a13e9c74c", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56801", "nomdmonddf"=>"1", "nomd
Sep 23 07:14:39 node-1 nailgun-agent: monisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.133812 #9090] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.133852 #9090] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.133866 #9090] DEBUG -- : Device dm-0 seems to be appropriate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.133880 #9090] DEBUG -- : Getting udev properties for device: dm-1
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.135542 #9090] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-otdowLWRIJP7H1R11jsnTFW6Ym2B2K5hu0tmjrajvgqMy8r99U4JPsu3qrNRKadi /dev/disk/by-uuid/49965c17-d3b6-4e39-b090-55c0895f3ef8 /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-otdowLWRIJP7H1R11jsnTFW6Ym2B2K5hu0tmjrajvgqMy8r99U4JPsu3qrNRKadi", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"49965c17-d3b6-4e39-b090-55c0895f3ef8", "ID_FS_UUID_ENC"=>"49965c17-d3b6-4e39-b090-55c0895f3ef8", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10
Sep 23 07:14:39 node-1 nailgun-agent: 358", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.135566 #9090] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.135594 #9090] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.135661 #9090] DEBUG -- : Device dm-1 seems to be appropriate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.135674 #9090] DEBUG -- : Getting udev properties for device: dm-2
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.137467 #9090] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-quNsy5xwJIXSOWdQKCo1VcAU4syNTs5X122U2Hk0qSl0R9OWRJlT3Z9rMKiNDTLB /dev/disk/by-uuid/51793e2a-68c5-478f-8819-edfdad4fee48 /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-quNsy5xwJIXSOWdQKCo1VcAU4syNTs5X122U2Hk0qSl0R9OWRJlT3Z9rMKiNDTLB", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"51793e2a-68c5-478f-8819-edfdad4fee48", "ID_FS_UUID_ENC"=>"51793e2a-68c5-478f-8819-edfdad4fee48", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15894", "nomdmond
Sep 23 07:14:39 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.137491 #9090] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.137517 #9090] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.137540 #9090] DEBUG -- : Device dm-2 seems to be appropriate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.137554 #9090] DEBUG -- : Getting udev properties for device: dm-3
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.139369 #9090] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-zy3p63F8oJ9EJap2WY811k4n5xGNDH7SFDFe7uhLWjfBkRzmaQWjj8M9Dieae0Bu /dev/disk/by-uuid/44482705-4f85-430e-b070-28874dc3de02 /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-zy3p63F8oJ9EJap2WY811k4n5xGNDH7SFDFe7uhLWjfBkRzmaQWjj8M9Dieae0Bu", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"44482705-4f85-430e-b070-28874dc3de02", "ID_FS_UUID_ENC"=>"44482705-4f85-430e-b070-28874dc3de02", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19451", "nomdmonddf"=>"1", 
Sep 23 07:14:39 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.139392 #9090] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.139419 #9090] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.139431 #9090] DEBUG -- : Device dm-3 seems to be appropriate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.139460 #9090] DEBUG -- : Getting udev properties for device: dm-4
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.141204 #9090] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-06B8WClzlNALV5NPEVf3Dk4TXcGeCwDnTp0FSlF9DLd660tOr4dFOrEwqcfKA6Pa /dev/disk/by-uuid/4d408674-bf7a-4fbd-9662-b3741f23b1ae /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-06B8WClzlNALV5NPEVf3Dk4TXcGeCwDnTp0FSlF9DLd660tOr4dFOrEwqcfKA6Pa", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4d408674-bf7a-4fbd-9662-b3741f23b1ae", "ID_FS_UUID_ENC"=>"4d408674-bf7a-4fbd-9662-b3741f23b1ae", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35401", "nomdmonddf"=>"1", "nomd
Sep 23 07:14:39 node-1 nailgun-agent: monisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.141227 #9090] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.141288 #9090] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.141301 #9090] DEBUG -- : Device dm-4 seems to be appropriate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.141315 #9090] DEBUG -- : Getting udev properties for device: dm-5
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.143223 #9090] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-06B8WClzlNALV5NPEVf3Dk4TXcGeCwDn6Y4qLX0bmWVZTDNUkS9MF6wtBJi43HWE /dev/disk/by-uuid/b5fd4300-1754-4098-8bfb-7302ce66d8ce /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-06B8WClzlNALV5NPEVf3Dk4TXcGeCwDn6Y4qLX0bmWVZTDNUkS9MF6wtBJi43HWE", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"b5fd4300-1754-4098-8bfb-7302ce66d8ce", "ID_FS_UUID_ENC"=>"b5fd4300-1754-4098-8bfb-7302ce66d8ce", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36018", "nomdmonddf"=>"1", "nomdmonisw"
Sep 23 07:14:39 node-1 nailgun-agent: =>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.143247 #9090] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.143275 #9090] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.143290 #9090] DEBUG -- : Device dm-5 seems to be appropriate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.143316 #9090] DEBUG -- : Getting udev properties for device: ram0
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.145096 #9090] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36192", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.145118 #9090] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.145149 #9090] DEBUG -- : Device ram0 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.145176 #9090] DEBUG -- : Getting udev properties for device: ram1
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.146728 #9090] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36208", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.146749 #9090] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.146791 #9090] DEBUG -- : Device ram1 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.146821 #9090] DEBUG -- : Getting udev properties for device: ram2
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.148391 #9090] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36473", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.148412 #9090] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.148446 #9090] DEBUG -- : Device ram2 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.148464 #9090] DEBUG -- : Getting udev properties for device: ram3
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.150130 #9090] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36491", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.150151 #9090] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.150198 #9090] DEBUG -- : Device ram3 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.150217 #9090] DEBUG -- : Getting udev properties for device: ram4
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.151817 #9090] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36510", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.151852 #9090] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.151884 #9090] DEBUG -- : Device ram4 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.151902 #9090] DEBUG -- : Getting udev properties for device: ram5
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.153481 #9090] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36529", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.153502 #9090] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.153533 #9090] DEBUG -- : Device ram5 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.153553 #9090] DEBUG -- : Getting udev properties for device: ram6
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.155170 #9090] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36552", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.155190 #9090] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.155220 #9090] DEBUG -- : Device ram6 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.155238 #9090] DEBUG -- : Getting udev properties for device: ram7
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.156680 #9090] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36568", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.156716 #9090] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.156751 #9090] DEBUG -- : Device ram7 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.156769 #9090] DEBUG -- : Getting udev properties for device: ram8
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.158442 #9090] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36581", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.158469 #9090] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.158496 #9090] DEBUG -- : Device ram8 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.158526 #9090] DEBUG -- : Getting udev properties for device: ram9
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.159987 #9090] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36597", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.160007 #9090] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.160057 #9090] DEBUG -- : Device ram9 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.160088 #9090] DEBUG -- : Getting udev properties for device: loop0
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.161546 #9090] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36058", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.161567 #9090] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.161619 #9090] DEBUG -- : Device loop0 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.161637 #9090] DEBUG -- : Getting udev properties for device: loop1
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.163157 #9090] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36069", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.163177 #9090] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.163221 #9090] DEBUG -- : Device loop1 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.163238 #9090] DEBUG -- : Getting udev properties for device: loop2
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.164661 #9090] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36090", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.164682 #9090] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.164710 #9090] DEBUG -- : Device loop2 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.164745 #9090] DEBUG -- : Getting udev properties for device: loop3
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.166418 #9090] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36105", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.166440 #9090] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.166471 #9090] DEBUG -- : Device loop3 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.166489 #9090] DEBUG -- : Getting udev properties for device: loop4
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.168076 #9090] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36123", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.168108 #9090] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.168147 #9090] DEBUG -- : Device loop4 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.168171 #9090] DEBUG -- : Getting udev properties for device: loop5
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.169771 #9090] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36140", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.169792 #9090] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.169821 #9090] DEBUG -- : Device loop5 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.169868 #9090] DEBUG -- : Getting udev properties for device: loop6
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.171501 #9090] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36157", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.171531 #9090] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.171567 #9090] DEBUG -- : Device loop6 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.171585 #9090] DEBUG -- : Getting udev properties for device: loop7
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.173147 #9090] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36172", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.173168 #9090] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.173217 #9090] DEBUG -- : Device loop7 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.173235 #9090] DEBUG -- : Getting udev properties for device: ram10
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.174896 #9090] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36222", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.174916 #9090] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.174958 #9090] DEBUG -- : Device ram10 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.174981 #9090] DEBUG -- : Getting udev properties for device: ram11
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.180905 #9090] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36237", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.180935 #9090] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.180982 #9090] DEBUG -- : Device ram11 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.181003 #9090] DEBUG -- : Getting udev properties for device: ram12
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.182990 #9090] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36253", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.183066 #9090] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.183123 #9090] DEBUG -- : Device ram12 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.183164 #9090] DEBUG -- : Getting udev properties for device: ram13
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.185079 #9090] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36434", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.185111 #9090] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.185193 #9090] DEBUG -- : Device ram13 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.185219 #9090] DEBUG -- : Getting udev properties for device: ram14
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.187269 #9090] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36449", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.187301 #9090] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.187344 #9090] DEBUG -- : Device ram14 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.187370 #9090] DEBUG -- : Getting udev properties for device: ram15
Sep 23 07:14:39 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189256 #9090] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36459", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189287 #9090] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189327 #9090] DEBUG -- : Device ram15 removable parameter: "0"
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189373 #9090] 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"}]
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189393 #9090] DEBUG -- : Block device seems to be physical data storage: sda
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189461 #9090] DEBUG -- : Found block device: dm-0
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189520 #9090] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189545 #9090] DEBUG -- : Found block device: dm-1
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189562 #9090] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189574 #9090] DEBUG -- : Found block device: dm-2
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189587 #9090] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189597 #9090] DEBUG -- : Found block device: dm-3
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189608 #9090] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189618 #9090] DEBUG -- : Found block device: dm-4
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189630 #9090] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189640 #9090] DEBUG -- : Found block device: dm-5
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189685 #9090] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189696 #9090] DEBUG -- : Found block device: ram0
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189707 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189716 #9090] DEBUG -- : Found block device: ram1
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189726 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189736 #9090] DEBUG -- : Found block device: ram2
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189747 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189759 #9090] DEBUG -- : Found block device: ram3
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189770 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189780 #9090] DEBUG -- : Found block device: ram4
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189827 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189837 #9090] DEBUG -- : Found block device: ram5
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189849 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189858 #9090] DEBUG -- : Found block device: ram6
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189869 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189879 #9090] DEBUG -- : Found block device: ram7
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189891 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189900 #9090] DEBUG -- : Found block device: ram8
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189911 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189965 #9090] DEBUG -- : Found block device: ram9
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189978 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189988 #9090] DEBUG -- : Found block device: loop0
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.189999 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190008 #9090] DEBUG -- : Found block device: loop1
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190021 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190030 #9090] DEBUG -- : Found block device: loop2
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190041 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190051 #9090] DEBUG -- : Found block device: loop3
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190064 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190120 #9090] DEBUG -- : Found block device: loop4
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190133 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190143 #9090] DEBUG -- : Found block device: loop5
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190154 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190163 #9090] DEBUG -- : Found block device: loop6
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190174 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190183 #9090] DEBUG -- : Found block device: loop7
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190194 #9090] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190204 #9090] DEBUG -- : Found block device: ram10
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190264 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190276 #9090] DEBUG -- : Found block device: ram11
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190288 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190298 #9090] DEBUG -- : Found block device: ram12
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190309 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190318 #9090] DEBUG -- : Found block device: ram13
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190329 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190339 #9090] DEBUG -- : Found block device: ram14
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190351 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190401 #9090] DEBUG -- : Found block device: ram15
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190414 #9090] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.190450 #9090] 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}]
Sep 23 07:14:39 node-1 nailgun-agent: D, [2016-09-23T07:14:39.345219 #9090] DEBUG -- : Response: status: 200 body: {"id": 1}
Sep 23 07:14:39 node-1 nailgun-agent: I, [2016-09-23T07:14:39.345371 #9090]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 23 07:15:01 node-1 CRON[16850]: (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")
Sep 23 07:15:05 node-1 puppet-user[14488]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 23 07:15:05 node-1 puppet-user[14488]: Finished catalog run in 29.36 seconds
Sep 23 07:15:06 node-1 puppet-user[17079]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 23 07:15:07 node-1 puppet-user[17079]: Compiled catalog for node-1.domain.tld in environment production in 0.61 seconds
Sep 23 07:15:07 node-1 puppet-user[17079]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 23 07:15:07 node-1 puppet-user[17079]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 23 07:15:07 node-1 puppet-user[17079]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 23 07:15:07 node-1 puppet-user[17079]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 23 07:15:07 node-1 puppet-user[17079]: Finished catalog run in 0.10 seconds
Sep 23 07:15:09 node-1 puppet-user[17537]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 23 07:15:10 node-1 puppet-user[17537]: Compiled catalog for node-1.domain.tld in environment production in 0.90 seconds
Sep 23 07:15:10 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 23 07:15:10 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 23 07:15:10 node-1 crontab[17973]: (root) LIST (root)
Sep 23 07:15:10 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 23 07:15:10 node-1 crontab[17974]: (root) REPLACE (root)
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 23 07:15:12 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/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
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 23 07:15:13 node-1 puppet-user[17537]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 23 07:15:13 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 23 07:15:13 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 23 07:15:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:15:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:16:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:00 node-1 ntpdate[1469]: no servers can be used, exiting
<27>Sep 23 07:17:00 node-1 ntpdate[1709]: no servers can be used, exiting
<27>Sep 23 07:17:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:35 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:35 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:35 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:35 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:35 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:17:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:18:55 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 23 07:18:55 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 23 07:19:01 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 23 07:19:01 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 23 07:19:06 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 23 07:19:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 23 07:19:12 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 23 07:19:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:20 node-1 ntpdate[19385]: the NTP socket is in use, exiting
<27>Sep 23 07:19:20 node-1 ntpdate[19437]: the NTP socket is in use, exiting
<27>Sep 23 07:19:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:32 node-1 multipathd: uevent trigger error
<129>Sep 23 07:19:34 node-1 haproxy[22127]: 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>Sep 23 07:19:35 node-1 haproxy[22132]: 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>Sep 23 07:19:35 node-1 haproxy[22132]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:35 node-1 haproxy[22132]: proxy mysqld has no server available!
<27>Sep 23 07:19:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:41 node-1 multipathd: uevent trigger error
<129>Sep 23 07:19:43 node-1 haproxy[24650]: 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>Sep 23 07:19:44 node-1 haproxy[24654]: 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>Sep 23 07:19:44 node-1 haproxy[24654]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:44 node-1 haproxy[24654]: proxy mysqld has no server available!
<129>Sep 23 07:19:44 node-1 haproxy[24654]: 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>Sep 23 07:19:45 node-1 haproxy[24654]: 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>Sep 23 07:19:45 node-1 haproxy[24654]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:45 node-1 haproxy[24654]: proxy object-storage has no server available!
<27>Sep 23 07:19:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:46 node-1 multipathd: uevent trigger error
<129>Sep 23 07:19:49 node-1 haproxy[26012]: 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>Sep 23 07:19:49 node-1 haproxy[26012]: 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>Sep 23 07:19:49 node-1 haproxy[26012]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:49 node-1 haproxy[26012]: proxy neutron has no server available!
<129>Sep 23 07:19:49 node-1 haproxy[26012]: 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>Sep 23 07:19:50 node-1 haproxy[26016]: 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>Sep 23 07:19:50 node-1 haproxy[26016]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:50 node-1 haproxy[26016]: proxy mysqld has no server available!
<129>Sep 23 07:19:50 node-1 haproxy[26016]: 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>Sep 23 07:19:50 node-1 haproxy[26016]: 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>Sep 23 07:19:50 node-1 haproxy[26016]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:50 node-1 haproxy[26016]: proxy object-storage has no server available!
<27>Sep 23 07:19:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:52 node-1 multipathd: uevent trigger error
<129>Sep 23 07:19:54 node-1 haproxy[27385]: 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>Sep 23 07:19:54 node-1 haproxy[27385]: Server keystone-1/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>Sep 23 07:19:54 node-1 haproxy[27385]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:54 node-1 haproxy[27385]: proxy keystone-1 has no server available!
<129>Sep 23 07:19:54 node-1 haproxy[27385]: 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>Sep 23 07:19:55 node-1 haproxy[27389]: Server keystone-2/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>Sep 23 07:19:55 node-1 haproxy[27389]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:55 node-1 haproxy[27389]: proxy keystone-2 has no server available!
<129>Sep 23 07:19:55 node-1 haproxy[27389]: 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>Sep 23 07:19:55 node-1 haproxy[27389]: 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>Sep 23 07:19:55 node-1 haproxy[27389]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:55 node-1 haproxy[27389]: proxy neutron has no server available!
<129>Sep 23 07:19:55 node-1 haproxy[27389]: 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>Sep 23 07:19:55 node-1 haproxy[27389]: 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>Sep 23 07:19:56 node-1 haproxy[27389]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:56 node-1 haproxy[27389]: proxy mysqld has no server available!
<129>Sep 23 07:19:56 node-1 haproxy[27389]: 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>Sep 23 07:19:56 node-1 haproxy[27389]: 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>Sep 23 07:19:56 node-1 haproxy[27389]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:19:56 node-1 haproxy[27389]: proxy object-storage has no server available!
<27>Sep 23 07:19:57 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:57 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:57 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:57 node-1 multipathd: uevent trigger error
<27>Sep 23 07:19:57 node-1 multipathd: uevent trigger error
<129>Sep 23 07:19:59 node-1 haproxy[28712]: 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>Sep 23 07:20:00 node-1 haproxy[28721]: Server keystone-1/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>Sep 23 07:20:00 node-1 haproxy[28721]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:00 node-1 haproxy[28721]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:00 node-1 haproxy[28721]: 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>Sep 23 07:20:00 node-1 haproxy[28721]: Server keystone-2/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>Sep 23 07:20:00 node-1 haproxy[28721]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:00 node-1 haproxy[28721]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:00 node-1 haproxy[28721]: 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>Sep 23 07:20:00 node-1 haproxy[28721]: 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>Sep 23 07:20:00 node-1 haproxy[28721]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:00 node-1 haproxy[28721]: proxy neutron has no server available!
<129>Sep 23 07:20:00 node-1 haproxy[28721]: 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>Sep 23 07:20:01 node-1 haproxy[28721]: 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>Sep 23 07:20:01 node-1 haproxy[28721]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:01 node-1 haproxy[28721]: proxy mysqld has no server available!
<129>Sep 23 07:20:01 node-1 haproxy[28721]: 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>Sep 23 07:20:01 node-1 haproxy[28721]: 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>Sep 23 07:20:01 node-1 haproxy[28721]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:01 node-1 haproxy[28721]: proxy object-storage has no server available!
<129>Sep 23 07:20:01 node-1 haproxy[28721]: 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>Sep 23 07:20:01 node-1 haproxy[28721]: 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>Sep 23 07:20:01 node-1 haproxy[28721]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:01 node-1 haproxy[28721]: proxy aodh has no server available!
<27>Sep 23 07:20:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:03 node-1 multipathd: uevent trigger error
<129>Sep 23 07:20:05 node-1 haproxy[30065]: 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>Sep 23 07:20:05 node-1 haproxy[30065]: Server keystone-1/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>Sep 23 07:20:05 node-1 haproxy[30065]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:05 node-1 haproxy[30065]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:05 node-1 haproxy[30065]: 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>Sep 23 07:20:05 node-1 haproxy[30065]: Server keystone-2/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>Sep 23 07:20:05 node-1 haproxy[30065]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:05 node-1 haproxy[30065]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:05 node-1 haproxy[30065]: 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>Sep 23 07:20:06 node-1 haproxy[30069]: 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>Sep 23 07:20:06 node-1 haproxy[30069]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:06 node-1 haproxy[30069]: proxy neutron has no server available!
<129>Sep 23 07:20:06 node-1 haproxy[30069]: 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>Sep 23 07:20:06 node-1 haproxy[30069]: 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>Sep 23 07:20:06 node-1 haproxy[30069]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:06 node-1 haproxy[30069]: proxy mysqld has no server available!
<129>Sep 23 07:20:06 node-1 haproxy[30069]: 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>Sep 23 07:20:06 node-1 haproxy[30069]: 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>Sep 23 07:20:06 node-1 haproxy[30069]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:06 node-1 haproxy[30069]: proxy object-storage has no server available!
<129>Sep 23 07:20:06 node-1 haproxy[30069]: 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>Sep 23 07:20:06 node-1 haproxy[30069]: 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>Sep 23 07:20:07 node-1 haproxy[30069]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:07 node-1 haproxy[30069]: proxy aodh has no server available!
<129>Sep 23 07:20:07 node-1 haproxy[30069]: 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>Sep 23 07:20:07 node-1 haproxy[30069]: 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>Sep 23 07:20:07 node-1 haproxy[30069]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:07 node-1 haproxy[30069]: proxy ceilometer has no server available!
<27>Sep 23 07:20:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:08 node-1 multipathd: uevent trigger error
<129>Sep 23 07:20:10 node-1 haproxy[31520]: 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>Sep 23 07:20:10 node-1 haproxy[31520]: Server keystone-1/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>Sep 23 07:20:11 node-1 haproxy[31524]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:11 node-1 haproxy[31524]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:11 node-1 haproxy[31524]: 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>Sep 23 07:20:11 node-1 haproxy[31524]: Server keystone-2/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>Sep 23 07:20:11 node-1 haproxy[31524]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:11 node-1 haproxy[31524]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:11 node-1 haproxy[31524]: 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>Sep 23 07:20:11 node-1 haproxy[31524]: 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>Sep 23 07:20:11 node-1 haproxy[31524]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:11 node-1 haproxy[31524]: proxy neutron has no server available!
<129>Sep 23 07:20:11 node-1 haproxy[31524]: 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>Sep 23 07:20:11 node-1 haproxy[31524]: 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>Sep 23 07:20:11 node-1 haproxy[31524]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:11 node-1 haproxy[31524]: proxy mysqld has no server available!
<129>Sep 23 07:20:12 node-1 haproxy[31524]: 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>Sep 23 07:20:12 node-1 haproxy[31524]: 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>Sep 23 07:20:12 node-1 haproxy[31524]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:12 node-1 haproxy[31524]: proxy object-storage has no server available!
<129>Sep 23 07:20:12 node-1 haproxy[31524]: 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>Sep 23 07:20:12 node-1 haproxy[31524]: 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>Sep 23 07:20:12 node-1 haproxy[31524]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:12 node-1 haproxy[31524]: proxy aodh has no server available!
<129>Sep 23 07:20:12 node-1 haproxy[31524]: 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>Sep 23 07:20:12 node-1 haproxy[31524]: 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>Sep 23 07:20:12 node-1 haproxy[31524]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:12 node-1 haproxy[31524]: proxy ceilometer has no server available!
<27>Sep 23 07:20:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:13 node-1 multipathd: uevent trigger error
<129>Sep 23 07:20:15 node-1 haproxy[391]: 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>Sep 23 07:20:16 node-1 haproxy[395]: Server horizon/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>Sep 23 07:20:16 node-1 haproxy[395]: 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>Sep 23 07:20:16 node-1 haproxy[395]: Server keystone-1/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>Sep 23 07:20:16 node-1 haproxy[395]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:16 node-1 haproxy[395]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:16 node-1 haproxy[395]: 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>Sep 23 07:20:16 node-1 haproxy[395]: Server keystone-2/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>Sep 23 07:20:16 node-1 haproxy[395]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:16 node-1 haproxy[395]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:16 node-1 haproxy[395]: 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>Sep 23 07:20:16 node-1 haproxy[395]: 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>Sep 23 07:20:16 node-1 haproxy[395]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:16 node-1 haproxy[395]: proxy neutron has no server available!
<129>Sep 23 07:20:16 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:17 node-1 haproxy[395]: proxy mysqld has no server available!
<129>Sep 23 07:20:17 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:17 node-1 haproxy[395]: proxy object-storage has no server available!
<129>Sep 23 07:20:17 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:17 node-1 haproxy[395]: proxy aodh has no server available!
<129>Sep 23 07:20:17 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: 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>Sep 23 07:20:17 node-1 haproxy[395]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:17 node-1 haproxy[395]: proxy ceilometer has no server available!
<27>Sep 23 07:20:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:19 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:19 node-1 multipathd: uevent trigger error
<129>Sep 23 07:20:21 node-1 haproxy[1861]: 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>Sep 23 07:20:21 node-1 haproxy[1861]: Server horizon/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>Sep 23 07:20:21 node-1 haproxy[1861]: 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>Sep 23 07:20:21 node-1 haproxy[1861]: Server keystone-1/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>Sep 23 07:20:22 node-1 haproxy[1881]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:22 node-1 haproxy[1881]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: Server keystone-2/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>Sep 23 07:20:22 node-1 haproxy[1881]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:22 node-1 haproxy[1881]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:22 node-1 haproxy[1881]: proxy glance-api has no server available!
<129>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:22 node-1 haproxy[1881]: proxy glance-glare has no server available!
<129>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:22 node-1 haproxy[1881]: proxy neutron has no server available!
<129>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: 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>Sep 23 07:20:22 node-1 haproxy[1881]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:22 node-1 haproxy[1881]: proxy glance-registry has no server available!
<129>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:23 node-1 haproxy[1881]: proxy mysqld has no server available!
<129>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:23 node-1 haproxy[1881]: proxy object-storage has no server available!
<129>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:23 node-1 haproxy[1881]: proxy aodh has no server available!
<129>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: 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>Sep 23 07:20:23 node-1 haproxy[1881]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:23 node-1 haproxy[1881]: proxy ceilometer has no server available!
<27>Sep 23 07:20:24 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:24 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:24 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:24 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:24 node-1 multipathd: uevent trigger error
<129>Sep 23 07:20:27 node-1 haproxy[3396]: 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>Sep 23 07:20:27 node-1 haproxy[3396]: Server horizon/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>Sep 23 07:20:27 node-1 haproxy[3396]: 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>Sep 23 07:20:27 node-1 haproxy[3396]: Server keystone-1/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>Sep 23 07:20:27 node-1 haproxy[3396]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:27 node-1 haproxy[3396]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:27 node-1 haproxy[3396]: 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>Sep 23 07:20:27 node-1 haproxy[3396]: Server keystone-2/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>Sep 23 07:20:27 node-1 haproxy[3396]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:27 node-1 haproxy[3396]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:28 node-1 haproxy[3407]: proxy nova-api has no server available!
<129>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:28 node-1 haproxy[3407]: proxy nova-metadata-api has no server available!
<129>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:28 node-1 haproxy[3407]: proxy glance-api has no server available!
<129>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:28 node-1 haproxy[3407]: proxy glance-glare has no server available!
<129>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:28 node-1 haproxy[3407]: proxy neutron has no server available!
<129>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:28 node-1 haproxy[3407]: proxy glance-registry has no server available!
<129>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: 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>Sep 23 07:20:28 node-1 haproxy[3407]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:28 node-1 haproxy[3407]: proxy mysqld has no server available!
<129>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:29 node-1 haproxy[3407]: proxy object-storage has no server available!
<129>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:29 node-1 haproxy[3407]: proxy aodh has no server available!
<129>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:29 node-1 haproxy[3407]: proxy ceilometer has no server available!
<129>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: 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>Sep 23 07:20:29 node-1 haproxy[3407]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:29 node-1 haproxy[3407]: proxy nova-novncproxy has no server available!
<27>Sep 23 07:20:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:30 node-1 multipathd: uevent trigger error
<129>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: Server horizon/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>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: Server keystone-1/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>Sep 23 07:20:33 node-1 haproxy[4733]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:33 node-1 haproxy[4733]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: Server keystone-2/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>Sep 23 07:20:33 node-1 haproxy[4733]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:33 node-1 haproxy[4733]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:33 node-1 haproxy[4733]: proxy nova-api has no server available!
<129>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:33 node-1 haproxy[4733]: proxy nova-metadata-api has no server available!
<129>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:33 node-1 haproxy[4733]: proxy cinder-api has no server available!
<129>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:33 node-1 haproxy[4733]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:33 node-1 haproxy[4733]: proxy glance-api has no server available!
<129>Sep 23 07:20:33 node-1 haproxy[4733]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy glance-glare has no server available!
<129>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy neutron has no server available!
<129>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy glance-registry has no server available!
<129>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy mysqld has no server available!
<129>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy object-storage has no server available!
<129>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy aodh has no server available!
<129>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy ceilometer has no server available!
<129>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: 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>Sep 23 07:20:34 node-1 haproxy[4737]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:34 node-1 haproxy[4737]: proxy nova-novncproxy has no server available!
<27>Sep 23 07:20:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:36 node-1 multipathd: uevent trigger error
<129>Sep 23 07:20:38 node-1 haproxy[6119]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server horizon/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>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server keystone-1/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>Sep 23 07:20:39 node-1 haproxy[6125]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy keystone-1 has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server keystone-2/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>Sep 23 07:20:39 node-1 haproxy[6125]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy keystone-2 has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy nova-api has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy nova-metadata-api has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy cinder-api has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy glance-api has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy glance-glare has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:39 node-1 haproxy[6125]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:39 node-1 haproxy[6125]: proxy neutron has no server available!
<129>Sep 23 07:20:39 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy glance-registry has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy mysqld has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy object-storage has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy aodh has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy ceilometer has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy heat-api has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy heat-api-cfn has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy heat-api-cloudwatch has no server available!
<129>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: 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>Sep 23 07:20:40 node-1 haproxy[6125]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 23 07:20:40 node-1 haproxy[6125]: proxy nova-novncproxy has no server available!
<27>Sep 23 07:20:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:20:53 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 23 07:21:17 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>Sep 23 07:21:19 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 23 07:21:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:21:45 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 23 07:22:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:22:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:22:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:22:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:22:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:38 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:38 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:38 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:38 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 23 07:24:54 node-1 apache2_error [Fri Sep 23 07:24:49.871596 2016] [mpm_event:notice] [pid 14126:tid 140184204736384] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 23 07:24:54 node-1 apache2_error [Fri Sep 23 07:24:49.871667 2016] [core:notice] [pid 14126:tid 140184204736384] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 23 07:24:54 node-1 apache2_error [Fri Sep 23 07:24:52.865978 2016] [mpm_event:notice] [pid 14126:tid 140184204736384] AH00491: caught SIGTERM, shutting down
<43>Sep 23 07:24:54 node-1 apache2_error [Fri Sep 23 07:24:53.956221 2016] [mpm_worker:notice] [pid 15567:tid 140294105409408] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 23 07:24:54 node-1 apache2_error [Fri Sep 23 07:24:53.956292 2016] [core:notice] [pid 15567:tid 140294105409408] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 23 07:24:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:24:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:03 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:06 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:06 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:06 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:06 node-1 multipathd: uevent trigger error
<27>Sep 23 07:25:06 node-1 multipathd: uevent trigger error
<43>Sep 23 07:26:15 node-1 apache2_error [Fri Sep 23 07:26:08.068452 2016] [mpm_worker:notice] [pid 15567:tid 140294105409408] AH00295: caught SIGTERM, shutting down
<43>Sep 23 07:26:15 node-1 apache2_error [Fri Sep 23 07:26:08.815893 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 23 07:26:15 node-1 apache2_error [Fri Sep 23 07:26:08.815943 2016] [core:notice] [pid 28675:tid 139906862442368] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 23 07:26:55 node-1 apache2_error [Fri Sep 23 07:26:52.320206 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 23 07:26:55 node-1 apache2_error [Fri Sep 23 07:26:52.515981 2016] [mpm_worker:warn] [pid 28675:tid 139906862442368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 23 07:26:55 node-1 apache2_error [Fri Sep 23 07:26:52.519817 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 23 07:26:55 node-1 apache2_error [Fri Sep 23 07:26:52.519832 2016] [core:notice] [pid 28675:tid 139906862442368] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 23 07:27:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:36 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:27:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:27:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:23 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:23 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:23 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:23 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:23 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:27 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:28:45 node-1 multipathd: uevent trigger error
<27>Sep 23 07:29:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:29:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:29:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:29:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:29:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:30:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:30:48 node-1 multipathd: uevent trigger error
<27>Sep 23 07:30:48 node-1 multipathd: uevent trigger error
<27>Sep 23 07:30:48 node-1 multipathd: uevent trigger error
<27>Sep 23 07:30:48 node-1 multipathd: uevent trigger error
<27>Sep 23 07:30:48 node-1 multipathd: uevent trigger error
<27>Sep 23 07:30:48 node-1 multipathd: uevent trigger error
<27>Sep 23 07:30:48 node-1 multipathd: uevent trigger error
<27>Sep 23 07:31:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:31:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:31:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:31:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:31:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:32:10 node-1 multipathd: uevent trigger error
<27>Sep 23 07:33:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:34:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:34:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:01 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:47 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:47 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:47 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:47 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:47 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:47 node-1 multipathd: uevent trigger error
<27>Sep 23 07:35:47 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:50 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:36:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:36:58 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Sep 23 07:36:58 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Sep 23 07:36:59 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Sep 23 07:37:00 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Sep 23 07:37:00 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Sep 23 07:37:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:28 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:28 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:28 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:28 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:28 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:37:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:39:51 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:40:04 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:04 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:04 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:04 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:04 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:42 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:40:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:25 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:25 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:25 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:25 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:25 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:30 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:34 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:34 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:34 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:34 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:52 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:53 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:53 node-1 multipathd: uevent trigger error
<27>Sep 23 07:41:53 node-1 multipathd: uevent trigger error
<27>Sep 23 07:42:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:42:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:42:39 node-1 multipathd: uevent trigger error
<27>Sep 23 07:42:40 node-1 multipathd: uevent trigger error
<27>Sep 23 07:42:53 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:43:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:43:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:43:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:43:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:00 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:00 node-1 multipathd: uevent trigger error
<11>Sep 23 07:44:12 node-1 liberasurecode[16891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:12 node-1 liberasurecode[16891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:12 node-1 liberasurecode[16891]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:12 node-1 liberasurecode[16891]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:12 node-1 liberasurecode[16915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:12 node-1 liberasurecode[16915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:12 node-1 liberasurecode[16915]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:12 node-1 liberasurecode[16915]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:14 node-1 liberasurecode[17367]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:14 node-1 liberasurecode[17367]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:14 node-1 liberasurecode[17367]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:14 node-1 liberasurecode[17367]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18603]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18603]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18687]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18687]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18687]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:18 node-1 liberasurecode[18687]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[18856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[18856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[18856]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[18856]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19064]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19064]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19064]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19064]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19098]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19098]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19098]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19098]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19147]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19147]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19147]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19147]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19161]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19161]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19161]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:19 node-1 liberasurecode[19161]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:36 node-1 liberasurecode[20706]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:36 node-1 liberasurecode[20706]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:36 node-1 liberasurecode[20706]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:44:36 node-1 liberasurecode[20706]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 23 07:44:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:44 node-1 multipathd: uevent trigger error
<27>Sep 23 07:44:44 node-1 multipathd: uevent trigger error
<11>Sep 23 07:45:01 node-1 liberasurecode[25192]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:45:01 node-1 liberasurecode[25192]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:45:01 node-1 liberasurecode[25192]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:45:01 node-1 liberasurecode[25192]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Sep 23 07:45:36 node-1 apache2_error [Fri Sep 23 07:45:31.634822 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 23 07:45:36 node-1 apache2_error [Fri Sep 23 07:45:32.015704 2016] [mpm_worker:warn] [pid 28675:tid 139906862442368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 23 07:45:36 node-1 apache2_error [Fri Sep 23 07:45:32.019795 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 23 07:45:36 node-1 apache2_error [Fri Sep 23 07:45:32.019835 2016] [core:notice] [pid 28675:tid 139906862442368] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 23 07:45:53 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 23 07:46:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:12 node-1 multipathd: uevent trigger error
<43>Sep 23 07:46:16 node-1 apache2_error [Fri Sep 23 07:46:08.537160 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 23 07:46:16 node-1 apache2_error [Fri Sep 23 07:46:08.733192 2016] [mpm_worker:warn] [pid 28675:tid 139906862442368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 23 07:46:16 node-1 apache2_error [Fri Sep 23 07:46:08.746125 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 23 07:46:16 node-1 apache2_error [Fri Sep 23 07:46:08.746158 2016] [core:notice] [pid 28675:tid 139906862442368] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 23 07:46:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:20 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:20 node-1 multipathd: uevent trigger error
<43>Sep 23 07:46:56 node-1 apache2_error [Fri Sep 23 07:46:54.597117 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 23 07:46:56 node-1 apache2_error [Fri Sep 23 07:46:54.793489 2016] [mpm_worker:warn] [pid 28675:tid 139906862442368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 23 07:46:56 node-1 apache2_error [Fri Sep 23 07:46:54.803559 2016] [mpm_worker:notice] [pid 28675:tid 139906862442368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 23 07:46:56 node-1 apache2_error [Fri Sep 23 07:46:54.803590 2016] [core:notice] [pid 28675:tid 139906862442368] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 23 07:46:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:46:58 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:05 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:11 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:11 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:11 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:11 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:29 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:29 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:29 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:29 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:56 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:56 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:56 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:56 node-1 multipathd: uevent trigger error
<27>Sep 23 07:47:56 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:03 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 23 07:48:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:12 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:48:17 node-1 multipathd: uevent trigger error
<27>Sep 23 07:49:04 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<11>Sep 23 07:50:02 node-1 liberasurecode[19563]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:50:02 node-1 liberasurecode[19563]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:50:02 node-1 liberasurecode[19563]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:50:02 node-1 liberasurecode[19563]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 23 07:51:07 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:07 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:07 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:07 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:13 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:21 node-1 multipathd: uevent trigger error
<129>Sep 23 07:51:32 node-1 haproxy[3095]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 23 07:51:32 node-1 haproxy[3095]: 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.
<27>Sep 23 07:51:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:33 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:49 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:54 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:54 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:54 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:54 node-1 multipathd: uevent trigger error
<27>Sep 23 07:51:55 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:08 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:15 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:21 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:43 node-1 multipathd: uevent trigger error
<27>Sep 23 07:52:43 node-1 multipathd: uevent trigger error
<129>Sep 23 07:52:52 node-1 haproxy[3095]: 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>Sep 23 07:53:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:32 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:37 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:41 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:46 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:50 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:50 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:50 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:50 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:50 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:55 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:55 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:55 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:55 node-1 multipathd: uevent trigger error
<27>Sep 23 07:53:55 node-1 multipathd: uevent trigger error
<11>Sep 23 07:55:01 node-1 liberasurecode[26215]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:55:01 node-1 liberasurecode[26215]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:55:01 node-1 liberasurecode[26215]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 23 07:55:01 node-1 liberasurecode[26215]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
